Ours used to say 'the spec doesn't match the component.' Took me a while to figure out why.
Curious to learn about your approach.
The biggest recurring complaint I see is not the delivery format—it’s missing state and exception context. A file can expose exact padding and token values, but engineering still has to guess loading, empty, error, responsive, and interaction states.
A preflight that reduces rework is:
1. Every screen points to the component and variant it uses.
2. Tokens are named, not only shown as hex/px values.
3. A state/responsive matrix says explicitly what exists and what is missing.
4. Exceptions and intentional overrides are called out.
5. Unresolved decisions have an owner instead of being silently inferred.
JSON or a Tailwind file helps with mechanical values, but it doesn’t replace that decision log. In your case, was “the spec doesn’t match the component” caused by stale published components, local overrides, or a state that wasn’t documented?
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
