Design systems at scale
What changes when 44 teams depend on a library instead of three. Adoption, governance, documentation, naming that survives a redesign.
Vladislav Iushev
forDesigners


What changes when 44 teams depend on a library instead of three. Adoption, governance, documentation, naming that survives a redesign.
OKLCH, component tokens, semantic naming without rigid hierarchies, spacing that matches Figma.
Flows where mistakes cost money: states, edge cases, multi-conditional logic, mobile trading.
Prompt input, waiting states, failure modes, and designing for output nobody can predict.
Figma MCP, Cursor, design and code in parallel. What actually speeds up and what doesn't.
An outside view from someone who's looked at a lot of them from inside product teams.
What these teams value, how they hire, what to prepare for.
For one question you keep circling
$200
Upgrade to a package anytime
For working through a real problem
$600
4 hours in total
For a full review and a plan to execute
$1,000
7 hours in total
Nothing. Send a link or a question beforehand if you want, or just show up.
English or Russian.
Bank transfer in USD, EUR or AED, or USDT if you prefer crypto. More options coming soon. I send the details once we've agreed on a time.
Yes. Most people use them across several sessions rather than one long one.
As part of a session, yes. I'll tell you how it reads and what I'd change, but I won't rebuild it for you.
No. Nobody can promise that. What I can do is tell you honestly what's in the way.