Figma library
Tokens as variables, light and dark, all components with variants and auto layout. Your designers pull from the library instead of eyeballing. One source of truth.
AI-Ready Design systems for teams that need ship fast, with less friction
We build design systems that your team and your tools can both run on: a Figma library for designers, an npm package for engineers, and a docs site your coding agents ingest as context. All within 2 weeks and for $20k fixed.
/problem
Half your UI is now built by AI. Your design system wasn't made for that.
The work is moving faster than the system. AI, contractors, and product teams are shipping in parallel — while your design system still expects a single human to sign off on every radius.
Every new feature ships its own button, its own spacing, its own shade of blue.
Designers eyeball colour and radius instead of pulling from one source of truth.
Coding agents invent components because there's nothing to reference.
Small inconsistencies compound into a product held together with tape.
This is for teams with no design-ops safety net, who need consistency to be the default instead of another quarterly project.
Your team uses agents for your ui, ux, and code.
Your team uses agents for your ui, ux, and code.Claude, Cursor, v0, Lovable — they all build faster than a human can review. Give them a documented system to pull from and their output stops drifting from what your designers intended.
You need foundations this month, not in six.
You need foundations this month, not in six.A fixed two-week sprint with a fixed price, not a quarterly design-ops initiative. You get the Figma library, the npm package and the docs site while the roadmap that needs them is still current.
/deliverables
Three artifacts. One source of truth.
A design system only works when design, code, and documentation stay in lockstep. These three deliverables share the same tokens, components, rules, and skills — so you never have to rebuild the same thing twice because of hallucinations.
npm package
Typed, production-grade components with your tokens as plain JSON. Accessible by default, dark mode included. Install it and ship.
Docs site
A custom documentation site with every token, rule, skill written in plain markdown. Readable by your team, ingestible by your agents.
/case-study
"The system finally matches what's in the file. Our agents stopped inventing buttons, and every screen we ship looks like it belongs to the same product."
Placeholder Client
design lead @company
10 days
from audit to handover
100
components created
1
source of truth
/process
Ten working days, four milestones.
A fixed scope and a senior team working on nothing else. Here is how the fortnight runs.
Audit
day 1–3We review your product and existing patterns, keep what works, and lock scope and direction with quick component spikes.
Audit1-2d→ audit.mdPlan1 d→ component-inventory.csv
Systemise
day 3–6Colour, type, spacing, radius and motion become named tokens with light and dark themes. Exported as Figma variables and JSON.
Build system1 d→ figma variables
Tokenize3d→ tokens.json
Build
day 6–9The 37 components that cover 95% of product UI, built in parallel in Figma and code so neither drifts. Daily async reviews.
Build library1 d→ ui-kit v0.1Build npm1 d→ @company/ui
Ship
day 10–14Docs site live, npm package published, Figma library shared. We hand over in a working session with your whole team.
Publish Docs1 d→ docs.company.devHandover workshop1 d→ handover session
/investment
The Design System Sprint
Figma library, npm package, and docs site — one system, one sprint. We only do two systems a month, by design. Sprints take 10-14 days, and are billed upfront.
$20,000
Audit of your product and existing patterns
Full token system (colour, type, spacing, radius, motion)
37 components matched in Figma and code
Typed npm package with tokens as plain JSON
Custom docs site your coding agents can read
Dark mode + accessibility pass
Daily async updates + weekly sync
/questions
Build for you to move fast.
How can two weeks be enough?
Because the scope is fixed and the team is senior. We're not inventing a brand — we systemise the one you already have, and 37 components cover about 95% of real product UI. The exceptions get documented patterns, so your team knows exactly how to extend the system.
We already have a design system — is this still useful?
Answer coming soon.
Which stacks do you support?
Answer coming soon.
What happens after handover?
Answer coming soon.
Fix it once, instead of patching it forever.