Command reference
Say what you want. Or name the exact move.
You don't need a special command: describe the outcome and a bare /pristine picks the right one. When you know what kind of change you want, use a command, or name a Lens after polish.
Start here
Build something new
A page, a component, or a redesign in a new direction.
/pristine design a signup page for our monthly book clubImprove what you have
Keep the look; fix what's holding it back.
/pristine polish the pricing page, keep the current layoutJust want a score
Honest review, out of 10, without touching code.
/pristine critique localhost:3000/checkoutCommands 4
initTeach Pristine your product, your users and your design system.edits codecritiqueScore a page out of 10, through your users' eyes, with the fixes to reach 10.read-onlydesignBuild something new, or redesign what you have in a new direction.edits codepolishFinish what you have. Same look, every detail raised.edits code
Lenses 16
Polish picks Lenses for you. Name them to force exactly those: /pristine polish bolder animate the hero. Design uses them as build rules.
Make it stronger The page is flat, timid or anonymous.
Make it calmer The page is loud, busy or crowded.
Fix the structure The eye goes to the wrong place, or the page breaks on one screen.
Make it feel alive Nothing answers, or one moment deserves more.
Make it hold up Real data, slow networks, keyboards, and the last 5%.
What a bare /pristine runs
| You say | It runs |
|---|---|
| “Build a pricing page” | design |
| “Redesign the dashboard, it looks dated” | design |
| “Clean up the settings page” | polish |
| “Is this signup any good?” | critique |
If it can't tell a redesign from a polish, it asks once. Otherwise it names the route in one line and starts.