Impeccable GitHub: Design Skill, Setup and Review Workflow
Find pbakaus/impeccable and choose a focused design review without treating automated findings as a complete UX audit.
Impeccable is the design vocabulary and review toolkit at pbakaus/impeccable, with documentation at impeccable.style. Its commands help a coding agent make and review interface changes.
Start with the supported setup
The README provides an installer, manual-copy and plugin paths for supported tools. It distinguishes project and global installation, asks users to reload their coding tool and documents additional hook approval for some harnesses. Follow the path for your actual tool; copying skill files and installing a hook are different actions. Sources checked October 31, 2026.
The project describes critique for design review, audit for technical findings, and focused refinements such as polish. Its deterministic detector is separate from the agent's broader judgment. Do not assume every integration installs the same hooks or permissions.
Impeccable as an agent skill
The Impeccable skill provides design guidance to an agent; it is not a replacement for the product's design system or a finished interface. Pick the setup documented for your coding environment and state what the existing project must preserve. Review the proposed changes in the actual rendered page. The project README was rechecked November 4, 2026.
Give it a concrete target
Choose one existing surface, a user task and a constraint: for example, making a pricing comparison easier to scan on a phone while keeping the current brand typography. Capture the current state, ask for ranked findings, then apply one main change and inspect it at the relevant screen sizes.
| Output | What still needs your review |
|---|---|
| Automated detector finding | Whether the rule applies to this interface |
| Design suggestion | Whether it improves the intended user task |
| Edited source file | Whether the rendered result and behavior work |
A clean scan does not prove usability or accessibility. Installation may add hooks and download an engine; read the current documentation before approving those changes.
Varwo reviewed the project without installing it or running a design experiment. Compare the separate Taste Skill guide when choosing design instructions for an agent.