impeccable
Designs, evaluates or refines an interface through a targeted procedure.
- Status
- Observed
- Last reviewed
- 2026-10-10
ID: impeccable.
What it does
Loads product context, visual direction and the surface brief, then selects the relevant procedure: design, critique, audit, polish, clarification, adaptation or other work. Distinguishes refinement that preserves identity from a redesign that replaces it. Follows command instructions and, before changing UI, the minimum quality bar. Limits visual verification and corrections to defined passes.
When to use it
Use it to create a surface, redesign it or address a UI problem with a specific outcome. shape helps define UX/UI before code; critique evaluates design; audit examines technical quality; polish completes an approved direction. It is not needed for backend-only work.
How to use it
Ask for it by name, or invoke it with /impeccable in Claude Code or $impeccable in Codex. Specify the surface, goal, constraints and reference material. Name the command if you know it, or describe the need. Request adherence to the brief and project components, with final visual verification and stated limitations.
What it delivers
- Outcome defined by the selected command
- Any changes to UI or design documents
- Visual evidence and relevant checks
Example
Use impeccable clarify on the invitation form: make labels and errors understandable while preserving layout, functionality and the product glossary.
Prerequisites
- The procedure uses the launcher included in the skill and the command references. If the launcher fails, context must be read from existing documents; the failure is declared.
Executable instructions
The skill is installed from the source maintained by pbakaus; its license applies.
In the workflow
Use the router to choose this capability based on the required outcome.