Skip to main content
What it contains
Frontend design/quality Agent Skill plus commands, detector rules, PRODUCT.md/DESIGN.md artifacts, and live browser iteration.
Typical uses
Plan, create, critique, audit, polish, harden, adapt, animate, and optimize frontend interfaces with bounded visual QA.
Why people choose it
Inference: combines aesthetic craft with production frontend checks and explicit routing boundaries.
LicenseApache License 2.0
Last meaningful updateUnknown
Production readinessproduction
Classification
Subject domains
frontend designUXUI quality
Task categories
frontend designUXUI quality
Project phases
designimplementationreview
Secondary types
CLIfrontend quality toolkit
Select when
- User wants to design/redesign/audit/polish/harden/optimize a frontend
Do not select when
- Backend-only or non-UI task
Implementation complexitymedium
Routing heuristic 88.0%
Security boundary clarity
3/5 First-party routing documentation
5/5 Strengths
None documented.
Poor-fit scenarios
- Backend-only or non-UI task
Limitations
None documented.
.claude/skills/impeccable/SKILL.md
Route frontend requests/playbooks.
routingbounded QA
.claude/skills/impeccable/reference/
Shape/init/document/extract.
planningdesign context
.claude/skills/impeccable/reference/
Critique/audit.
UXa11yperformance
.claude/skills/impeccable/reference/
Polish/harden/animate/layout/adapt/optimize and more.
refinement
.claude/skills/impeccable/reference/live.md
Browser visual variants.
live iteration
.claude/skills/impeccable/scripts/
Deterministic design checks.
linting
LanguagesMarkdown, JavaScript
FrameworksNone documented
Operating systemsNone documented
Installation methodsnpx impeccable install, Claude plugin
Interfacesskill, CLI, hooks
Required credentialsNone documented
External servicesNone documented
Major dependenciesNone documented
Compatibility notes
None documented.
One-sentence semantic summary
Frontend design/quality Agent Skill plus commands, detector rules, PRODUCT.md/DESIGN.md artifacts, and live browser iteration.
Capability keywords
designcritiqueauditpolishhardeningresponsiveperformancelive variants
User intent phrases
- User wants to design/redesign/audit/polish/harden/optimize a frontend
Negative match phrases
- Backend-only or non-UI task
Differentiators
None documented.
Security considerations
None documented.
Privacy considerations
None documented.
Uncertainty
Unresolved items
None documented.
Inference notes
None documented.
Evidence
- repository_metadata · Repository metadata/identity checked through GitHub.
- readme · Primary first-party README inspected.
- documentation · Exact master-skill trigger boundary and command routing inspected.
Repository usage guidance
installation summarynpx impeccable install; Claude plugin
basic usage summaryPlan, create, critique, audit, polish, harden, adapt, animate, and optimize frontend interfaces with bounded visual QA.
documented entry points/impeccable
key configuration filesNone documented
important directories.claude/skills/impeccable/
documentation pathsREADME.md, .claude/skills/impeccable/SKILL.md
example pathsNone documented
Relationships
overlapping
medium
Both improve frontend design; Impeccable includes routed audit/hardening.
overlapping
medium
Both provide UI/UX guidance; UI-UX-Pro-Max emphasizes structured catalogs.
Recommended combinations
Frontend quality stack high
Each repository covers a distinct layer; avoid combining tools that duplicate lifecycle ownership.
Order of operations
- Extract incumbent design system
- Make extracted tokens/design docs authoritative
- Run Impeccable for scoped design/audit
- Use taste skill only where it does not conflict
Routing rules
rule_013: User wants to design/redesign/audit/polish/harden/optimize a frontend P987
Rationale
Frontend design/quality Agent Skill plus commands, detector rules, PRODUCT.md/DESIGN.md artifacts, and live browser iteration.
Required conditions
None documented.
Preferred
pbakaus/impeccable
Fallback
None