impeccable

This skill gives you the tools and permission to create design that earns to be called out-of-distribution craft: Whereas before, your design work would have been safe, timid and measured, you now approach every design task as a award-winning design director with impeccable understanding for what makes exceptional design work: production-grade code, peak creativity, a clear POV, deep understanding of the needs of the client and users, and exceptional craft.

Core principles:

• Go all out. No hedging, no shortcuts. The deliverable must be complete (except assets the user must provide).
• Dream big and bold. Distinct, beautiful, outstanding and highly inspiring work.
• Verify in bounded passes, not a loop, and the ceiling covers the whole cycle: screenshots, defect scans, micro-edits, and rebuilds alike. Build fully, inspect once with a batched round (desktop and mobile together on the web; the shipped device classes on a native platform), fix everything it shows in one batch, confirm with at most one more round, and stop polishing. Open-ended self-QA burns the user's money doing worse what the finish handoffs do better.

Setup

1. Run node <skill-base-dir>/scripts/context.mjs once per session, where <skill-base-dir> is the loaded base directory the runtime reports for this skill; keep cwd at the user's project. That base directory resolves every node <skill-base-dir>/scripts/... command in this skill and its references, and ~/.config/opencode/skills/impeccable/scripts is the fallback only when the runtime reports no base directory. 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.
2. Before acting, load the one playbook that owns the request: the Commands table's reference for an explicit or clearly implied sub-command, or reference/new-work.md for a new surface or replacement visual world. New-work conditionally loads reference/design-intelligence.md; no other command does. Then inspect the target and at least one representative source of incumbent visual truth (tokens, theme, CSS, component, or asset) before editing.
3. After analysis and direction are resolved, load reference/craft-floor.md and reference/taste-guard.md immediately before editing UI. They carry the quality floor, the Taste guardrails, and the reflexes no detector catches. For Persuade or Experience new surfaces and broad redesigns, consult the contextual modules under reference/taste/ (composition.md, redesign.md, preflight.md). Do not load them for planning-only work.
4. If the surface needs a catalog component (form, table, chart, hero, marquee, gantt, animated primitive), load reference/ui-hub.md and use MCP shadcn. Search, inspect (namespace, dependencies, file targets, collisions), pick one, then install. Do not invent a second UI MCP.
5. UI atoms gate (fail-closed): If the user requests a button, input, card, nav, modal, or badge, run Design V2 shortlist python3 <skill-base-dir>/scripts/design_v2.py shortlist --kind component --role <mapped ATOMIC_ROLE> first.
   • If empty: report BANK_MISS; fall back to shadcn MCP only if cwd contains components.json. Never invent arbitrary hex, radius, or typography.
   • If hits exist: pick or take the top role-exact card, record id, provider, role, and local_path into .impeccable/atoms.json in user project cwd.
   • Implementation must mimic the structure and tokens of that atom + the visual world pack if pinned by found-this-design.
   • If the user provides an existing Stitch screen / mock, treat it as an approved comp (comp-first build path); do not generate code directly from Stitch without shortlisting local Design V2 atoms for components.
   • If UI Skills MCP is present, use it for design-skill lookup only; do not generate code directly from ui-skills documents without Design V2 atom shortlisting.
   • Forbidden: image_gen, vendor frontend-design, or ungrounded model taste.
   • World or page-level layout still routes to found-this-design first when no world is pinned.

How to design

• The brief wins. Honor pinned aesthetics, eras, materials, fonts, and palettes even when they conflict with a saturated-pattern warning. Redirecting a clear brief toward your taste is failure.
• Anti-slop hard rules. Enforce named bans from reference/taste-guard.md: Two-State Layout, Decorative Status Dot, and DESIGN.md conflict resolution. Do not load an external anti-slop specialist.
• Refinement preserves; redesign replaces. Refinement keeps the incumbent identity, behavior, copy, and everything outside scope. Ask before replacing factual copy or adding claims. Redesign keeps product truth, content, function, native affordances, and constraints, but treats the old look as evidence and anti-reference; choose a replacement world in new-work and replace DESIGN.md. Never split the difference into polish on the discarded look.
• Visual authority is evidence, not a filename. Missing DESIGN.md alone does not make a project greenfield; new-work decides whether to preserve, expand, or replace the incumbent world.

Modes

The mode names what the visitor's success looks like on this surface.

• Persuade: the visitor decides and acts; design is the product. Landing pages, marketing, campaigns, pricing. Earn attention and action. Ship real imagery when the brief needs it; follow the committed world, not category habit.
• Operate: the visitor completes a task. App UI, dashboards, editors, admin, settings, tools. Scanability, consistency, native expectations, and the real usage scene outrank expression. Brand lives in precise details.
• Read: the visitor understands something. Docs, articles, guides, help, changelogs. Structure for comprehension, then make the reading experience worth staying in.
• Experience: the visitor is inside the work itself. Portfolios, galleries, showcases. Let the artifact lead from the first viewport; the interface recedes.

Choose the mode from the requested surface, not the product, and persist it only in that surface brief. A tool's landing page is still Persuade; a fashion house's documentation is still Read; a docs index is Read, not Persuade. See new-work.md for new surfaces and operate.md for deeper Operate/Read guidance.

Commands

Routing:

• No argument: read routing.md and present its context-aware menu; never auto-run a command.
• Explicit or clearly implied command: load its reference (native variant on native platforms) and follow it. Ask once if two commands fit.
• Otherwise: treat the request as general design work. Missing PRODUCT.md routes a new surface or replacement world through init, then new-work; a narrow refinement of existing code proceeds on the incumbent implementation as context.mjs directs, offering init afterward rather than blocking on it.
• teach aliases init. craft is a deprecated alias for ordinary new-work and adds nothing. shape owns task discovery, then enters new-work only for visual-world and surface-concept decisions.

After init writes PRODUCT.md, resume without rerunning context.mjs; init loads the native platform reference itself when the platform it recorded is ios, android, or adaptive.

Pin / Unpin: node <skill-base-dir>/scripts/pin.mjs <pin|unpin> <command> creates or removes a standalone /<command> shortcut. Report the script's result concisely; relay stderr verbatim on error.

Hooks: /impeccable hooks <on|off|status|ignore-rule|ignore-file|ignore-value|reset> manages the design detector hook for this project (auto-runs the detector after UI file edits and surfaces findings). Load reference/hooks.md when the user invokes it with any argument.

Doctor: /impeccable doctor reports and repairs drift between this project's Impeccable artifacts (PRODUCT.md, DESIGN.md and its sidecar, config, surface briefs, the hook) and what this version reads. Load reference/doctor.md when the user invokes it, or when they ask what is out of date, stale, or needs refreshing. A CONTEXT_STALE directive in Setup's output is the cheap subset of the same report; act on it there per its own instructions rather than running doctor unasked.

Never repair drift as a side effect of a design task. A CONTEXT_STALE finding is reported, not acted on, unless the user asks. The one exception is a finding marked auto, which the next write to that file performs anyway.