impeccable
Impeccable is a design skill system for coding agents, with a separate deterministic detector for interface patterns. It is most useful to evaluate on an existing component with a specific usability problem, such as unclear hierarchy or confusing error recovery. The skill guides model-driven changes; the detector reports patterns it recognizes. Those two capabilities need different acceptance criteria and should not be treated as a single design-quality score.
On November 4, 2026, we ran the published [email protected] detector on two controlled local HTML fixtures. The first produced four findings and exit code 2; after manual changes, the second produced an empty findings array and exit code 0. This verifies the fixture workflow only. It does not measure generated design quality, accessibility completeness, conversion, performance or any comparison between models.
For adoption, save product goals and existing visual rules before requesting changes. PRODUCT.md and DESIGN.md provide the project context described by the official documentation. Start with a narrow target, inspect the diff and rerun the normal build and interaction checks. Hooks require their own host configuration and trust. Live Mode can accept variants into source, but we did not exercise it in this review.
Read the full review, verification scope and sources →Features
Why choose it
Trade-offs
Maintenance check
- Last commit
- 2026-11-10
- Commits, last 90 days
- 100+
- Releases, last 90 days
- 30
- Latest release
- skill-v4.8.2 (2026-11-09)
- Open issues
- 62
- Recent issues with at least one comment
- 6/8
Oldest week on the left; the latest four weeks are orange. Source: GitHub commit activity.
Status rule: archived on GitHub = Archived; last commit within 90 days = Active; 91 to 365 days = Slowing; older = Stale. All figures come from the GitHub API on the date shown.
Most discussed open issues
- #386 Vue preview mode: needs Svelte-parity accept path before it can ship9 comments · 2026-07-18
- #846 [Bug] Unchanged DESIGN.md sidecar reported stale after checkout/worktree creation (mtime-only comparison)6 comments · 2026-09-22
- #1264 critique: score never improves (28/40 three rounds running) even when every priority issue is fixed3 comments · 2026-10-31
- #1022 [Feature] Configurable PRODUCT.md and DESIGN.md paths across Context, Live Mode, and design tooling3 comments · 2026-10-12
- #950 [Bug] detect: elements inside an `inert` subtree under a page overlay count as occluded/nested content3 comments · 2026-10-05
Issue titles are quoted from GitHub. Open the link to check whether a problem still applies to the version you use.
Who it fits
- You have an existing interface and a concrete component-level problem.
- You can review generated changes and preserve documented brand decisions.
- You only need code formatting or a complete accessibility certification.
- You expect zero findings to prove that a design performs better.
Quick start
Use cases
Alternatives
Comments
No comments yet. Be the first!