Enterprise design
systems services

A design system is the best way to unify the interface across multiple products and features. You update a component or style once and every product built on it gets the update. Here's how to tell you're ready:

• No shared UI yet: the UI is scattered across products and teams, with no one owning the shared pieces.
• Design and code drift: your Figma library and the components in code don't agree, so every new feature turns into another round of UI rework.
• AI ships off-brand: your agents generate interfaces that don't look like your product.
• Communication gaps: design and engineering argue over component behavior because there's no shared library or documentation to reference.

Most enterprise design systems start when two of these signs become visible. Waiting for all four grows the work past a design system into a product refactor.

Foundation

• Component library: a Figma library connected to components in code, with design and front-end sharing the same variants, states and composition.
• Design tokens: colors, typography, spacing and motion as one structured system, shipped as JSON and CSS variables.
• Examples and patterns: every pattern the product ships, from navigation and forms to data tables and error states, with clear do/don't examples.

Rules

• AI UI rules: a spec-driven ruleset that lets AI work with your code, suggest improvements and ship new UI that passes the design review.
• Accessibility: WCAG 2.2 contrast and target sizes built into the component architecture.

Governance

• Documentation: component docs, version history, and a contributor playbook for shipping updates without breaking the system.
• Ownership: you own the system. I stay at your side to handle design and governance.

You work with me directly, a passionate and attentive human who has spent over 15 years building enterprise design systems, helping companies across a wide range of industries. Here's the work I can take over:

• Custom design systems: think of me as a founding designer for your design system. I build it from scratch or evolve the one you have, from strategy and brand to front-end.
• Governance: I map how the system takes contributions and how releases ship safely, with documentation and guardrails to help the team catch and resolve design debt early.
• Design tokens: I design the token architecture around your product, so it can support white-labeling, multi-brand theming and design modes.
• Adoption: I help your team measure adoption metrics, set goals, track and improve them over time.
• Product design: beyond the system, I create the visual language and shape your product's design, from mobile and web to AR interfaces.
• Designer and developer collaboration: I help teams shape a painless design-to-code handoff. With my GTC framework, I set shared terms, so design and engineering speak the same language.
• Design engineering: I polish the details that make interfaces feel special: CSS styles, component architecture, motion and micro-interactions in code.
• Training: I train and consult your team on the system's nuances, so they can run and improve it without me.
• Accessibility: I audit the screens produced by the design system, so they pass WCAG and compliance requirements.

AI can help with most aspects of creating and using a design system, but it needs structured context to do it: tokens, components, docs and working examples.

My job is to create that context and integrate it into your agents correctly, so the UI they make looks like your product.

Here's how I help companies extend their design systems with AI:

• Design system to AI: your full system, translated piece by piece into structured context for agents.
• AI readiness audit: a report on where the system fails today, with every fix in priority order.
• Agent-readable tokens: the building blocks for your agent, so new components and screens get created on brand.
• Rules file: AGENTS.md or Cursor rules that spell out which token, component or pattern goes where, with prompt examples for your team to rely on.
• Figma MCP setup: a live connection between your design files and code environment that lets agents pull live tokens and components straight from the source.
• Agentic skills: the skills for your team to direct agents, review their output, and keep the rules up to date as the system grows.

The AI-ready system gets tuned and tested on your real screens and prompts before the team relies on it. The setup can be run on top of your existing design system or the one we build first.

• Design partner: as a design system expert on your team, I help set the standards and keep design and code in sync, so the system keeps shipping great products.
• Fixed project: we work with a defined scope, such as a design system audit, a redesign, a new product launch, or a token refactor, with fixed pricing set from start to finish.

Either way, the work runs in stages. We'll tailor them based on where your product is today and skip the ones it doesn't need. Most commonly it looks like this:

• Audit: how the team ships UI today, across design and code, with proposed fixes ranked by impact.
• Strategy: a visual roadmap that sets the build order and long-term goals for the system.
• Design: tokens, components and patterns, built in the order the strategy set. I refine and review each step as it lands and compounds, so there is no big reveal at the end. Your team keeps shipping without me as a blocker.
• Handover: the docs, training sessions, adoption tracking, and a working process between design and engineering.

On the kickoff call we'll agree on the goals and how we'll measure the success of our partnership. Before any design work begins, you'll know the timeline and the cost.

Fixed projects are paid 50% upfront, 50% on completion. The design partner plan is billed monthly.