A TinyCTO.tv Hype Stack technical parable about design system, visual reference, implementation ambiguity. A design system must encode reusable behavior, constraints, accessibility, and governance—not only appearance.
# Episode 133 — The Design System Was a Screenshot — Script
## Concept design system;visual reference;implementation ambiguity
## Hype promise A prompt can turn an idea into a production-ready product before the meeting ends.
## System reality The design system is a screenshot with no components, states, tokens, accessibility rules, or ownership.
Risk approval is not risk ownership unless the decision is tied to people who can act when the risk becomes real.