All commands and Lenses
Command read-only
/pristine critique
Score a page out of 10, through your users' eyes, with the fixes to reach 10.
Critique is honest review without edits. It screenshots the target in light and dark, on desktop and mobile, walks it as each Persona, and scores 11 Dimensions. Every finding names the element, the value and the fix. It never touches a file.
Try it
/pristine critique localhost:3000/pricingA URL is the most accurate target: it captures the real rendered page.
/pristine critique src/app/onboarding/page.tsxA file path works too. It finds the route that renders it and captures that.
/pristine critique [pasted screenshot]Paste a screenshot of anything, including a competitor. It finds the matching code if it's yours.
/pristine is the checkout flow any good?Plain questions about quality route to critique automatically.
How it works
Loads context
Reads DESIGN.md for Personas and tokens. Without one, it uses the code as the system and sensible fallback Personas.
Captures before judging
Desktop 1440 and mobile 390, light and dark, full page. Waits for fonts, hydration and hover delays so it doesn't call a loading state a bug.
Walks it as each Persona
Can Maya on a laptop do her job? Can Arjun on a phone? Where do they hesitate, and where do they leave?
Places it on a Level, then scores
Level 2 template, 6 clean, 8 considered, 10 memorable. Then 11 Dimensions, each with evidence and the fix to reach 10.
Runs the detector
A static scan for things like tiny text, missing labels and ignored reduced motion. Findings are checked by eye, not trusted blindly.
What you get
- Overall score, Level and a two-line verdict
- A Dimension table: score, evidence, and what 10 needs
- Priority fixes P0 to P2, each with its Lens
- What already works, so polish doesn't break it
Check the result
- Look at the Captured line. If a cell is missing (say, no dark mode), the score for it is a guess.
- Push back on any finding you disagree with. It will either show evidence or withdraw it.
- A 9 is rare and a 10 is rarer. A 6 is normal for working software.
Then follow up in plain words
/pristine polish the P0 and P1 fixes from that critiquePolish picks up the saved findings instead of diagnosing again.