All commands and Lenses
Command edits code
/pristine polish
Finish what you have. Same look, every detail raised.
Polish is what a bare /pristine runs on existing UI. It captures the page, finds what's holding the score down, and applies only the Lenses that raise it, keeping the look, content and behavior. Then it captures again and reports every change with real values.
Try it
/pristine polish src/app/settings/page.tsxThe default. It picks the Lenses from what it finds.
/pristine the signup form feels off on mobileDescribe the symptom. A bare invocation on existing UI routes to polish.
/pristine polish bolder typeset the landing heroName Lenses to force them. It runs exactly those, in that order.
/pristine polish harden the invoices table, real customers have 40-character company namesGive the edge case you care about and it tests that first.
How it works
Captures and diagnoses
A baseline Capture of all four cells and a quick score, so every change has a before.
Plans the Lenses
Picks the few that raise the lowest Dimensions. Never two that fight, like bolder and quieter.
Applies them in order
Structure before detail: distill and layout, then typeset and color, then motion, then harden and the last details.
Verifies by looking
Captures again, checks nothing regressed, and reruns the detector on every edited file.
What you get
- A Before / After / Why table with real values ("13px #999 → 15px --ink-2, 4.9:1")
- Dimension scores before and after
- Detector findings it accepted, with the reason
- What's still short of 10, honestly
Check the result
- Do the main task on a narrow screen, then try the empty, loading and error states.
- Tab through it. Every focusable thing should show where focus is.
- If polish says the page is below Level 6, it will recommend design instead of quietly redesigning.
Then follow up in plain words
The error message is clearer now, but the form jumps when it appears. Keep the button still.Point at what's still wrong; it fixes that and captures again.