Name the actual design system inconsistencies in a UI before they multiply
Catch drift while it's three screens, not the whole product.
- Use it for
- Designers and engineers maintaining consistency across a growing product.
Design system drift happens one reasonable-seeming exception at a time — a slightly different button radius here, an ad-hoc spacing value there — and each individual instance is too small to notice while you're building it. By the time it's visible enough to bother someone, it's spread across dozens of screens and become expensive to fix. The window where it's cheap to catch is narrow and easy to miss without deliberately looking.
This prompt asks for the inconsistencies specifically, screen by screen, rather than general design feedback.
When not to use this
For an early-stage product with no design system yet, this is premature — you need one place before you can check for drift from it. This is for a product that has an established pattern and needs to check whether recent work is actually following it.
Did this work?
You get a specific list of inconsistencies (spacing, type scale, color usage, component variants) you hadn't consciously noticed, not a general "looks fine" or vague style commentary.
Tested on claude-opus-5. Evidence status is draft; it moves to battle-tested only on recorded runs, never by hand.