Design System FoundationMichael Kulesza
Design system humans and AI can use
I build design system foundations grounded in proven open-source libraries, extended with design tokens, rules, and custom components shaped by your real user flows.
The system evolves with your product — I sync with your team's releases so nothing gets outdated mid-build. I deliver a system that cuts time-to-ship, reduces rework, and keeps your product consistent as the team scales.
Best for:
CTOs tired of rebuilding the same component, design leads who finally got DS budget, teams scaling past 15–20 devs where inconsistency is growing.
Not a fit if you need a full rebrand, a coded component library, or a one-week quick fix.
What you get:
DS audit — identifying inconsistencies, detached instances, and structural gaps that block frontend velocity
Token architecture — Primitive / Semantic / Component via Figma Variables (colors, typography, spacing, etc.)
Component refactoring and expansion
Custom components tailored to your product requirements
Atomic Design structure — organized DS file
Governance rules — naming conventions, contribution guidelines, versioning
Accessibility baseline — WCAG AA+ compliance
Dev-ready annotations linked to implementation tickets
What's not included:
Coded component library (I deliver specifications and Figma, not React code)
Full product redesign (a DS is about foundations, not a rebrand)
Ongoing maintenance (that's a Retainer engagement)
Icon library from scratch (I use existing or open-source sets)
What I need from you:
Access to Figma (even if files are messy, that's what the audit phase is for)
Access to your codebase or documentation of the tech stack (so the DS aligns with implementation)
A list of your most-used components and key user flows
Any existing brand guidelines, color palettes, or typography rules
Your team's pain points with the current design/component setup
Example work
21st.ai — design system governance
Ready?
→ Book a Clarity Call or email me at michael@kulesza.io
FAQs
I deliver the specification that makes coding fast and accurate:
- design tokens structured in Figma Variables,
- component specs with every state, variant, and interaction documented,
- dev-ready annotations linked to implementation tickets.
Your developers don't start from a blank canvas, they start from a precise blueprint. In one project, this cut local style overrides to near-zero and made the system reusable across multiple product lines from day one.
Yes. I either build from scratch on an open-source foundation or refine and extend what you already have. The approach depends on the state of your current files and your team's tech stack.
No. I start by auditing what you have, even if it's chaos. Detached instances, scattered styles, broken naming. I've seen it all.
What I need is access to your Figma and codebase so I can map the real state of things.
The delivery includes a governance workshop (60 min): how to add components, how naming works, how to version changes.
I design everything to work without me. If your team is small or new to design systems, consider the retainer option for the first 2–3 months after delivery.
Every DS Foundation I deliver is structured for AI coding tools by default: predictable naming conventions, clean token hierarchy, component architecture that Cursor and Copilot can parse reliably. This means when your developers (or AI tools) generate UI, it follows your design system rules, not random defaults.
The optional AI Prompt Library add-on takes it further — tested prompts for generating on-brand UI components.
It depends on your stack. For React: Shadcn, Radix, or Ant Design. For Vue: Vuetify or Naive UI. Your dev team's preference matters — the goal is to build on something they already know.
Example work
Michael's other services
Starting at$8,000
Duration3 weeks
Tags
Figma
Component libraries
Design System
Design Systems Specialist
Digital Accessibility
Product Designer
SaaS
UI Designer
UX Designer
Service provided by
Michael Kulesza Białystok, Poland
Design System FoundationMichael Kulesza
Starting at$8,000
Duration3 weeks
Tags
Figma
Component libraries
Design System
Design Systems Specialist
Digital Accessibility
Product Designer
SaaS
UI Designer
UX Designer
Design system humans and AI can use
I build design system foundations grounded in proven open-source libraries, extended with design tokens, rules, and custom components shaped by your real user flows.
The system evolves with your product — I sync with your team's releases so nothing gets outdated mid-build. I deliver a system that cuts time-to-ship, reduces rework, and keeps your product consistent as the team scales.
Best for:
CTOs tired of rebuilding the same component, design leads who finally got DS budget, teams scaling past 15–20 devs where inconsistency is growing.
Not a fit if you need a full rebrand, a coded component library, or a one-week quick fix.
What you get:
DS audit — identifying inconsistencies, detached instances, and structural gaps that block frontend velocity
Token architecture — Primitive / Semantic / Component via Figma Variables (colors, typography, spacing, etc.)
Component refactoring and expansion
Custom components tailored to your product requirements
Atomic Design structure — organized DS file
Governance rules — naming conventions, contribution guidelines, versioning
Accessibility baseline — WCAG AA+ compliance
Dev-ready annotations linked to implementation tickets
What's not included:
Coded component library (I deliver specifications and Figma, not React code)
Full product redesign (a DS is about foundations, not a rebrand)
Ongoing maintenance (that's a Retainer engagement)
Icon library from scratch (I use existing or open-source sets)
What I need from you:
Access to Figma (even if files are messy, that's what the audit phase is for)
Access to your codebase or documentation of the tech stack (so the DS aligns with implementation)
A list of your most-used components and key user flows
Any existing brand guidelines, color palettes, or typography rules
Your team's pain points with the current design/component setup
Example work
21st.ai — design system governance
Ready?
→ Book a Clarity Call or email me at michael@kulesza.io
FAQs
I deliver the specification that makes coding fast and accurate:
- design tokens structured in Figma Variables,
- component specs with every state, variant, and interaction documented,
- dev-ready annotations linked to implementation tickets.
Your developers don't start from a blank canvas, they start from a precise blueprint. In one project, this cut local style overrides to near-zero and made the system reusable across multiple product lines from day one.
Yes. I either build from scratch on an open-source foundation or refine and extend what you already have. The approach depends on the state of your current files and your team's tech stack.
No. I start by auditing what you have, even if it's chaos. Detached instances, scattered styles, broken naming. I've seen it all.
What I need is access to your Figma and codebase so I can map the real state of things.
The delivery includes a governance workshop (60 min): how to add components, how naming works, how to version changes.
I design everything to work without me. If your team is small or new to design systems, consider the retainer option for the first 2–3 months after delivery.
Every DS Foundation I deliver is structured for AI coding tools by default: predictable naming conventions, clean token hierarchy, component architecture that Cursor and Copilot can parse reliably. This means when your developers (or AI tools) generate UI, it follows your design system rules, not random defaults.
The optional AI Prompt Library add-on takes it further — tested prompts for generating on-brand UI components.
It depends on your stack. For React: Shadcn, Radix, or Ant Design. For Vue: Vuetify or Naive UI. Your dev team's preference matters — the goal is to build on something they already know.
Example work
Michael's other services
$8,000