Polyms — one system, a growing ecosystem

Build the
whole deck.

Polyms is a family of products that keeps growing — ui-kit and ai-kit are just the first two out the door. Same brand, same vocabulary, everything after builds on the same deck.

live · ui-kit
TL
Tifa Lockhart
tifa.lockhart@polyms.dev
one systemno shadcn, no fluentbrand orangereal engineeringship the deckMIT licensedone systemno shadcn, no fluentbrand orangereal engineeringship the deckMIT licensed
01 — principles

Built once, run everywhere.

01

One system, every product

ui-kit, ai-kit, and everything Polyms ships after share the same vocabulary — no parallel library per team.

02

Semantic before brand

success/warning/danger/info stay untouched across the whole ecosystem. Brand orange lives only in --color-primary.

03

Skills over prompts

Agents like ai-kit are forked, adapted, owned — not black-box context you can't edit.

04

Built to compound

Every new product inherits the system instead of starting from zero — the ecosystem gets faster to ship, not slower.

02 — the ecosystem

Two shipped. Many more building.

ui-kit and ai-kit are the first two out the door — every product after inherits the same system.

SHIPPED

ui-kit

React 19 + Tailwind CSS 4 component library. Compound components, semantic theming, programmatic overlays.

NEXT UP

More on the way

The ecosystem keeps growing — same brand, same system, every time.

03 — meet ui-kit

Not a mockup. Real components.

BUTTON
SWITCH
AVATARTL
ALERT
04 — meet ai-kit

Agent skills for real engineering.

ai-kit is Polyms' shared brain for agentic fullstack dev — short-named skills you invoke with a slash command, from product requirements to shipped, reviewed code. Fork them, adapt them, commit back — they're yours, not black-box prompts.

KEY SKILLS
/pm
Requirements, PRD, user stories, prioritization.
/design
UI spec from PRD — flows, screens, ui-kit map.
/dev
Fullstack implementation, TDD, debugging.
/code-review
Two-axis review — Standards + Spec.
ONE PIPELINE, START TO SHIP
Idea/align/pm/to-issues/design/dev/code-reviewShip
MIT licensed — building at Polyms?

Plug into the system, not a starting point.

ui-kit and ai-kit are open source. Clone either repo and you inherit the tokens, the components, and the pipeline — no request queue, no gatekeeping.

terminal
$ ui-kit • tokens, components, theming — init your stack
$ ai-kit • skills, pipeline, slash commands — your daily driver
# MIT licensed. Fork it, ship it.