Design systems,explained forpeople who ship
no theory, just receipts
Choose from 120 design systems, compare the tradeoffs, and leave with an evidence-linked decision brief. Build on it with free token tools and editable references.
The systems closest to agent-ready today.
One practitioner, Kiryl Zhukouski, and the receipts.
Fourteen years building design systems for enterprise healthcare, industrial IoT and SaaS. The site is what I wish I'd had at year three: opinionated, practitioner-voiced, ad-free.
Four paths in. pick the one that matches your question.
Build a design system, day 1 to day 90.
Eight chapters mapped to a 90-day path. Foundations first, tokens before themes, governance before headcount. Practitioner voice, no theory.
Which design system to choose in 2026.
Five team shapes, five concrete recommendations, the anti-patterns to avoid, and the shifts since 2023 that changed the answer.
Why your design system isn't being used.
The hard part isn't building it — it's getting other teams to ship on it. The distribution mechanics, the funnel from discovery to maintenance.
Tokens, MCP servers, and agents that ship code.
The 2026 wedge: how to expose your tokens, components, and patterns to Cursor, Claude Code, and v0 without drift. Three pillars, a readiness checklist, and a 1-week migration plan.
The whole site, in five sections.
Playbook
Build a design system in eight chapters — foundations first, governance before headcount.
Foundations
Color, typography, spacing, and accessibility — the primitives everything else assumes.
Design systems
120 real-world systems compared side by side, each with tokens and a breakdown.
Frameworks
Implementation guides and adaptation patterns across React, Vue, and the rest.
Tools
Generators, calculators, and public-site scanners for your design system.
Design system tools
A workbench for the day-to-day: generate tokens, model the business case, check contrast, and lay out grids — no signup, nothing leaves your browser.