Design Systems & Figma scales.
Component-driven design systems and Figma libraries that survive contact with engineering. Tokens, variants, documentation, and a migration plan from your existing UI. I handle the design + the maintainer training.
The kinds of problems I'm good at.
- Token system (color, type, spacing, elevation, motion)
- Component library with variants, props, and edge-case states
- Documentation site (Storybook or a Notion-style doc hub)
- Migration plan from current UI + maintainer training
From kickoff to handoff.
- 01Week 1
Audit existing UI
Inventory every component, screen, and pattern in the current product. Identify duplicates + drift.
- 02Week 2
Token architecture
Design tokens (color, type, spacing, elevation, motion) with semantic + primitive layers.
- 03Weeks 3–5
Component library
Build core components with all variants + states. Documented as I go.
- 04Week 6
Migration plan
Mapping from old components → new. Sequenced rollout that doesn't block product work.
- 05Week 6–7
Maintainer training
Two sessions teaching your team how to extend the library. Recorded for future onboards.
What you'll actually get.
Figma library
Published library, ready for the team to consume from any file.
Documentation
When-to-use guidance for every component, with examples and don'ts.
When we're done, you have:
- A design system your engineers actually use (not one that drifts after month 3)
- Tokens that map cleanly to your code
- Documentation that's short enough to read in one sitting
- A trained maintainer on your team who can extend it
What's included.
- Token system (color, type, spacing, elevation)
- Component library (variants + props)
- Documentation site
- Migration plan from existing UI
- Maintainer handoff
Common questions.
I design the Figma library and provide token JSON. Building the React/Vue component library is a separate engagement (or a partner engineer's scope).
Yes — I can audit, extend, or migrate from existing systems (Material, shadcn/ui, Radix, custom). I won't throw away what works.
Sub-10 screens probably doesn't need one yet. 30+ screens, multiple designers, or a planned redesign? Yes.
Optional retainer for design-system governance reviews, new component requests, and breaking-change planning.
