Design System Cosplay
Design system cosplay is what happens when teams build the surface level artifacts of a mature system without the conditions that justify one. They publish a big Figma library, add 12 themes, write a Notion page, then wonder why engineers ignore it. The term captures the LARPing of maturity by teams that have not crossed the real thresholds of scale or complexity.
It is not an honest design system with dedicated owners and a paid maintenance bill. Those exist at Stripe, Shopify, and GitHub because the math works. Cosplay happens when an eight person startup spends a quarter on 180 components no one asked for. Six months later the system is a graveyard.
The 95 percent versus 5 percent rule comes from this exact pattern. Five percent of teams run multiple products at massive scale in regulated domains. They need the system. The other 95 percent are building infrastructure for an org size they do not yet have. They copy the artifacts from Linear or Vercel without copying the taste or the restraint.
Watch for the signals. More components than features. No dedicated owner. Tokens that drift within one quarter. Engineers who treat the system as optional. These are cosplay indicators. The anti dashboard piece covers the same mistake in metrics. Teams build the dashboard before they have the product that justifies the data.
Stop the cosplay by auditing against the five conditions. Multiple products sharing identity. Headcount in the hundreds. Staffed design ops. External consumers. Regulated domain. Check fewer than three and default to the minimum viable visual system instead. Your team will ship faster and look better.
The irony is painful. Teams build these systems to look more professional. The result is slower velocity, heavier files, and visual debt that accumulates faster than they can pay it down. The teams that skip the cosplay and ship tokens plus primitives plus taste win the coherence race.
AI made cosplay even more obvious. Any junior with Cursor and Shadcn can generate brand consistent UI in minutes. The 400 component Figma library with its own release cadence suddenly looks like expensive make believe.
Design system cosplay feels like progress until you measure the output. Then it just feels like theater.
Build only what your current size earns. Everything else is costume.
Read the full guide
Related terms
Keep exploring
Design System
A design system is the living product of tokens, components, patterns, guidelines, and governance that stops teams from reinventing UI every sprint.
Anti-Dashboard
A focused interface that answers one specific question, surfaces one priority list, and ties every visible number to a clear next action while hiding everything else.
Minimum Viable Visual System
The three layer stack of design tokens, UI primitives, and taste that delivers consistent interfaces for the 95 percent of teams who should never build a full design system.
Visual Debt
Visual debt is the growing pile of design inconsistencies, awkward lockups, mismatched systems, and permanent workarounds that accumulate when brand architecture fails to match the reality of your expanding portfolio.