impeccable
Run impeccable design quality commands on frontend code — audit, critique, polish, animate, normalize, and more. Built on top of the frontend-design skill with 20 steering commands and 10 domain-specific reference files. Use when doing a design QA pass, reviewing UI quality, or refining a frontend component before shipping.
Best use case
impeccable is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Run impeccable design quality commands on frontend code — audit, critique, polish, animate, normalize, and more. Built on top of the frontend-design skill with 20 steering commands and 10 domain-specific reference files. Use when doing a design QA pass, reviewing UI quality, or refining a frontend component before shipping.
Teams using impeccable should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/impeccable/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How impeccable Compares
| Feature / Agent | impeccable | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Run impeccable design quality commands on frontend code — audit, critique, polish, animate, normalize, and more. Built on top of the frontend-design skill with 20 steering commands and 10 domain-specific reference files. Use when doing a design QA pass, reviewing UI quality, or refining a frontend component before shipping.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
SKILL.md Source
> **Source:** External skill (frontend-design ecosystem) — local copy, do not modify without checking upstream. # Impeccable Design quality layer for Claude Code. 20 commands that audit, review, polish, and refine frontend interfaces. Complements the `frontend-design` skill (vision/direction) with systematic QA passes. **Source:** https://github.com/pbakaus/impeccable **Installed at:** `~/clawd/skills/` (frontend-design + 20 individual command skills) ## When to Use - After building a component or page with `frontend-design` — run a quality pass - Pre-ship review: `/audit` → `/critique` → `/polish` - Targeted fixes: `/colorize`, `/animate`, `/bolder`, `/quieter` - Design system alignment: `/normalize`, `/extract` ## 20 Commands | Command | What it does | |---|---| | `/teach-impeccable` | One-time setup: gather design context, save to project config | | `/audit` | Technical quality checks (a11y, performance, responsive) — scores 5 dimensions with P0-P3 severity | | `/critique` | UX design review — scores against Nielsen's 10 heuristics, persona archetypes, cognitive load | | `/normalize` | Align with design system standards | | `/polish` | Final pass before shipping | | `/distill` | Strip to essence — remove unnecessary complexity | | `/clarify` | Improve unclear UX copy and labels | | `/optimize` | Performance improvements | | `/harden` | Error handling, i18n, edge cases | | `/animate` | Add purposeful motion | | `/colorize` | Introduce strategic color | | `/bolder` | Amplify boring designs | | `/quieter` | Tone down overly bold designs | | `/delight` | Add moments of joy | | `/extract` | Pull into reusable components | | `/adapt` | Adapt for different devices | | `/onboard` | Design onboarding flows | | `/typeset` | Fix typography: font choices, hierarchy, sizing, weight, readability | | `/arrange` | Fix layout, spacing, visual rhythm, monotonous grids | | `/overdrive` | Technically extraordinary effects: shaders, spring physics, scroll-driven reveals (beta) | ## 10 Reference Files | Reference | Covers | |---|---| | `typography.md` | Type systems, font pairing, modular scales, OpenType | | `color-and-contrast.md` | OKLCH, tinted neutrals, dark mode, accessibility | | `spatial-design.md` | Spacing systems, grids, visual hierarchy | | `motion-design.md` | Easing curves, staggering, reduced motion | | `interaction-design.md` | Forms, focus states, loading patterns | | `responsive-design.md` | Mobile-first, fluid design, container queries | | `ux-writing.md` | Button labels, error messages, empty states | | `cognitive-load.md` | Cognitive load theory, chunking, progressive disclosure | | `heuristics-scoring.md` | Nielsen's heuristics scoring rubric and evaluation | | `personas.md` | User persona archetypes for design critique | ## How to Use from OpenClaw Delegate to Claude Code via acpx. Pass the target file/component and the command: ```bash # Pre-ship QA pass (recommended sequence) acpx --approve-all claude --cwd ~/bloom/frontend \ 'Run impeccable quality pass on [component/file]: 1. /audit — check a11y, performance, responsive 2. /critique — UX design review 3. /polish — final pass Report issues found and fixes applied.' # Targeted single command acpx --approve-all claude --cwd ~/bloom/frontend \ '/animate the [component] — add purposeful motion using the impeccable animate skill' # Design system alignment acpx --approve-all claude --cwd ~/bloom/frontend \ '/normalize [component] to align with our design system tokens' ``` ## Recommended Workflow ``` 1. Build → frontend-design skill (vision + direction) 2. QA → /audit + /critique 3. Refine → /polish + targeted commands as needed 4. Ship ``` ## Anti-Patterns (Built-in to the Skill) Impeccable explicitly tells the agent what NOT to do: - Overused fonts (Arial, Inter, system defaults) - Gray text on colored backgrounds - Pure black/gray (always tint neutrals) - Cards nested in cards - Bounce/elastic easing (feels dated)
Related Skills
teach-impeccable
One-time setup that gathers design context for your project and saves it to your AI config file. Run once to establish persistent design guidelines.
writer
Write content in Eric's voice — articles, blog posts, tweets, social media posts, marketing copy, newsletter drafts. Loads WRITING-STYLE.md and enforces kill phrases.
positioning-angles
Use when defining product positioning, choosing strategic angles, crafting value propositions, competitive positioning, product messaging, differentiation strategy, or go-to-market angles. Also use for 'how should I position my app', 'what angle should I use', 'painkiller vs vitamin', or 'market positioning'.
outline-generator
Use when generating outlines, article structures, content outlines, blog outlines, planning article sections, structuring posts, breaking down topics into sections, or organizing ideas for long-form content. Also use for 'outline this', 'structure this article', or 'plan the sections'.
last30days-open
Use only when the user explicitly asks for the open variant of last30days, including watchlists, briefings, and history queries. Sources: Reddit, X, YouTube, web.
last30days
Use when researching what happened in the last 30 days on a topic. Also triggered by 'last30'. Sources: Reddit, X, YouTube, web. Produces expert-level summary with copy-paste-ready prompts.
hooks
Use when generating hooks, headlines, titles, and scroll-stopping openers for content. Also use when analyzing viral posts, Reels, TikToks, YouTube Shorts, or successful social examples to extract reusable hook patterns and improve hook guidance.
evaluate-content
Use when judging content quality OR editing/improving existing copy: shareability, readability, voice, cuttability, angle, copy sweeps.
editor-in-chief
Use when a first draft is complete and all Phase 1 gates are done: topic selected (seo-research), title approved (hooks), outline approved (outline-generator), draft written (writer). Runs autonomous diagnosis-prescribe-rewrite loop before Substack.
copywriting
Write or improve marketing copy for any surface: pages, ads, app stores, landing pages, TikTok/Meta scripts, push notifications, UGC. Combines page copy frameworks with direct response principles.
content-strategy
Use when building content strategy: hooks, angles, and ideas from what's trending now. Covers organic and paid creative across TikTok, X, YouTube, Meta, LinkedIn.
content-pipeline
Orchestrator for the 3-article content pipeline — runs research phase, spawns parallel article sub-agents, creates Typefully drafts. Use when running the full content pipeline (usually via cron at 3am).