Ship the launch plan by Friday.
Owners, dependencies, and decisions in one view.
Start with what feels wrong.
Open a page you want to improve and describe the problem in your own words. Name what must stay: the brand, layout, content, or a behavior people already rely on.
/impeccable this dashboard feels crowded and the important numbers are hard to find. Improve the hierarchy while keeping our colors and existing features.
You do not need to know which command fits. Impeccable can inspect the page and choose an approach from your request.
If you are unsure what needs work, ask for a critique:
/impeccable critique the dashboard
Read the findings, then ask your agent to address the ones you want to change. A critique reviews the design; it does not automatically apply every proposed fix. Try a critique with the visual overlay for a worked example.
Describe the outcome, or use a command when you know the kind of change you want:
/impeccable polish the pricing page. Keep our colors, plan names, and monthly/yearly switch.
Ship the launch plan by Friday.
Owners, dependencies, and decisions in one view.
Ship the launch plan by Friday.
Owners, dependencies, and decisions in one view.
| What needs work | Try |
|---|---|
| Unfinished details, alignment, or inconsistent spacing | polish |
| A confusing page structure or weak hierarchy | layout |
| Hard-to-read text or inconsistent type | typeset |
| Too much competing content | distill |
| Vague labels or unclear instructions | clarify |
| A design that feels too timid or too loud | bolder or quieter |
For visual alternatives in the running page, name the element and direction with generate:
/impeccable generate 3 bold variants of the pricing cards
Compare the alternatives in your browser and accept the one you want in your source code. To select and annotate elements yourself, iterate with Live Mode.
A focused improvement keeps the current visual identity. If you want to replace it, say so:
/impeccable redesign the marketing site. Keep the product facts and signup flow, but replace the current visual style.
A redesign goes through Build something new, including choosing a direction and deciding whether to review mockups first. A routine polish pass does not need that process. To make ongoing work follow an established identity, record your design system.
Try the page’s main task, inspect it at a narrow width, and review the code changes. Tell the agent what works and what still needs adjustment. Specific feedback helps:
The plan comparison is easier to read. Keep that, but move the monthly/yearly switch above it again.
Before shipping, use audit for accessibility, performance, and responsive issues. Enable automatic design checks if you want detector feedback during future UI edits.