Guide - When to Use Impeccable
Impeccable is most useful when the problem is not functionality, but quality of presentation.
What Impeccable is good at
Section titled “What Impeccable is good at”- improving visual hierarchy
- fixing bland layouts
- sharpening UX copy
- improving consistency and polish
- helping UI work feel more intentional
Use Impeccable when
Section titled “Use Impeccable when”- a screen technically works but looks generic
- you want critique before shipping a design
- you want a cleanup pass after the core feature is done
- you need help with copy, spacing, or interaction quality
Common commands and what they are for
Section titled “Common commands and what they are for”| Command | Best use |
|---|---|
/audit | Find quality issues in a screen or component |
/normalize | Make the UI more consistent |
/polish | Do a final refinement pass |
/distill | Remove unnecessary complexity |
/clarify | Improve vague or weak UX copy |
/animate | Add purposeful motion |
/colorize | Introduce stronger color decisions |
How it behaves
Section titled “How it behaves”- it critiques rather than just generating new code blindly
- it tends to improve aesthetics, clarity, and cohesion
- it works best after you already have a baseline UI to improve
When not to use it
Section titled “When not to use it”- backend-only work
- pure API or infrastructure tasks
- very early product logic where visuals are still irrelevant