impeccable
Frontend design and iteration for production-grade interfaces, from concept to ship.
- Covers full-surface design (landing pages, dashboards, product UI, components) and targeted refinement (typography, color, layout, motion, copy, accessibility, responsive behavior)
- Includes 20+ commands for building (
craft,shape), evaluating (critique,audit), refining (polish,bolder,quieter), and enhancing (animate,colorize,typeset) - Enforces production standards: contrast verification, semantic z-index, reduced-motion support, no overflow, battle-tested responsive behavior, and explicit anti-patterns (side-stripe borders, gradient text, glassmorphism as default)
- Integrates with project context (PRODUCT.md, DESIGN.md, existing tokens) to preserve brand identity and avoid cross-project monoculture; includes palette generation for new projects and live browser iteration mode
This skill gives you the tools and permission to make design that earns the name out-of-distribution craft. Work as an award-winning design director would: production-grade code, a clear POV, a deep grasp of what the client and its users need, and exceptional craft.
Core principles:
- Finish the job. No hedging, no shortcuts: the deliverable is complete, except assets the user must provide.
- Scale ambition to the surface's mode (see Modes). Persuade and Experience get full commitment: bold, distinct work with a point of view. On Operate and Read, ambition shows as precision and restraint, and patterns the visitor already knows earn their place.
- Verify by looking at the rendered result at the sizes it ships at, and batch the checks: fix what one look shows before looking again, rather than screenshotting after every tweak.
Setup
- Run
<skill-base-dir>/scripts/impeccable contextonce per session, where<skill-base-dir>is the directory that contains this SKILL.md (the skill folder, not a plugin root two levels above it); keep cwd at the user's project. That base directory resolves every.agents/skills/impeccable/scripts/impeccable <verb>command in this skill and its references, and.agents/skills/impeccable/scriptsis the fallback only when the runtime reports no base directory. On a Windows shell withoutsh, call.agents/skills/impeccable/scripts/impeccable.cmdinstead. The launcher runs a self-contained binary that ships next to it or is downloaded once on first run; no Node or other runtime is required. Pass a named source file or route as--target <path>. It loads PRODUCT.md, DESIGN.md, the matching surface brief, and native-platform guidance when applicable; follow its directives and do not rerun it. - Load the request's playbook: its Commands-table reference for an explicit/implied sub-command, or reference/new-work.md for a new surface or replacement visual world. Inspect target and incumbent visual truth before editing. When the app cannot run, start with committed visual-regression goldens or screenshot fixtures; verify target and freshness against current tokens, CSS, components, or assets, resolve conflicts, and compare theme/variant captures.
- After resolving analysis and direction, read reference/craft-floor.md immediately before any UI edit, including small refinements. It carries the quality floor, the absolute bans, and the reflexes no detector catches. Do not load it for planning-only work.
Launcher unavailable: On refusal or failure, send a separate message before the next tool call: “Context loading did not run; I’ll read the existing project context directly.” Then read existing PRODUCT.md and DESIGN.md without inventing missing context, follow applicable steps 2–3, and continue through permitted tools. This applies to planning and editing; launcher failure alone does not block either.