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
sh <skill-base-dir>/scripts/impeccable context (Windows PowerShell or cmd: <skill-base-dir>\scripts\impeccable.cmd context) once per session, with cwd at the user's project and a 60-second limit. Read reference/launcher.md first for base-directory resolution, timeout, Windows and Permission denied handling, and pin/unpin; it applies to every verb. The launcher 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.
- 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 (including loaded symbols), and the reflexes no detector catches. Do not load it for planning-only work.
Launcher unavailable: only after a real launcher attempt returned an error (a hang or timeout is not an error: retry once first), 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, including reading reference/craft-floor.md immediately before any UI edit, and continue through permitted tools. When both files are absent, proceed on the incumbent implementation and offer init afterward. Launcher failure alone does not block planning or editing.
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.
- 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.
- Named structure is delivered. When the user names a structural outcome (merge, consolidate, one page), deliver that structure; do not substitute links or banners.
- 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. Choose it from the requested surface, not the product, and persist it only in that surface brief (a tool's landing page is Persuade; a fashion house's docs are Read).
- Persuade (landing, marketing, pricing) and Experience (portfolios, galleries): mode-persuade.md. Full commitment, bold point of view.
- Operate (app UI, dashboards, editors, settings): mode-operate.md; deeper guidance in operate.md. Precision and restraint.
- Read (docs, articles, help, changelogs): mode-read.md. Structure for comprehension.
See new-work.md for new surfaces.
Commands
Each command's playbook is reference/<command>.md (audit and adapt also have a .native.md variant); descriptions in reference/commands.md.
- Build:
shape, init, document, extract, craft (deprecated alias)
- Evaluate:
critique, audit
- Refine:
polish, bolder, quieter, distill, harden, onboard
- Enhance:
animate, colorize, typeset, layout, delight, overdrive
- Fix:
clarify, adapt, optimize
- Iterate:
live, generate [n] [action] [element]
Routing:
- No argument: read routing.md and present its context-aware menu; never auto-run a command.
- Explicit or clearly implied request to run a command: load its reference (native variant on native platforms) and follow it. Ask once if two commands fit.
- Workflow or command-selection question: read Workflow questions.
- 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
impeccable context 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 impeccable context; init loads the native platform reference itself when the platform it recorded is ios, android, or adaptive.
Hooks / Doctor: /impeccable hooks <args> (the design detector hook): load reference/hooks.md on any argument. /impeccable doctor, or a question about what is out of date or stale: load reference/doctor.md.
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.
1---2name: impeccable3description: "Use when designing, critiquing, or improving a frontend or native UI: pages, dashboards, components, forms, layout, typography, color, motion, UX copy, design systems. Not for backend-only or non-UI tasks."4version: 4.8.05license: Apache 2.06metadata:7 source: https://skillmd.com/skills/calvin-llc/impeccable8---910This 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.1112Core principles:13- Finish the job. No hedging, no shortcuts: the deliverable is complete, except assets the user must provide.14- 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.15- 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.1617## Setup18191. Run `sh <skill-base-dir>/scripts/impeccable context` (Windows PowerShell or cmd: `<skill-base-dir>\scripts\impeccable.cmd context`) once per session, with cwd at the user's project and a 60-second limit. Read [reference/launcher.md](reference/launcher.md) first for base-directory resolution, timeout, Windows and `Permission denied` handling, and `pin`/`unpin`; it applies to every verb. The launcher loads PRODUCT.md, DESIGN.md, the matching surface brief, and native-platform guidance when applicable; follow its directives and do not rerun it.202. Load the request's playbook: its Commands-table reference for an explicit/implied sub-command, or [reference/new-work.md](reference/new-work.md) for a new surface or replacement visual world. Inspect target and incumbent visual truth before editing.213. After resolving analysis and direction, read [reference/craft-floor.md](reference/craft-floor.md) immediately before any UI edit, including small refinements. It carries the quality floor, the absolute bans (including loaded symbols), and the reflexes no detector catches. Do not load it for planning-only work.2223**Launcher unavailable:** only after a real launcher attempt returned an error (a hang or timeout is not an error: retry once first), 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, including reading [reference/craft-floor.md](reference/craft-floor.md) immediately before any UI edit, and continue through permitted tools. When both files are absent, proceed on the incumbent implementation and offer init afterward. Launcher failure alone does not block planning or editing.2425## How to design2627- **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.28- **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.29- **Named structure is delivered.** When the user names a structural outcome (merge, consolidate, one page), deliver that structure; do not substitute links or banners.30- **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.3132## Modes3334The mode names what the visitor's success looks like on this surface. Choose it from the requested surface, not the product, and persist it only in that surface brief (a tool's landing page is Persuade; a fashion house's docs are Read).3536- **Persuade** (landing, marketing, pricing) and **Experience** (portfolios, galleries): [mode-persuade.md](reference/mode-persuade.md). Full commitment, bold point of view.37- **Operate** (app UI, dashboards, editors, settings): [mode-operate.md](reference/mode-operate.md); deeper guidance in [operate.md](reference/operate.md). Precision and restraint.38- **Read** (docs, articles, help, changelogs): [mode-read.md](reference/mode-read.md). Structure for comprehension.3940See [new-work.md](reference/new-work.md) for new surfaces.4142## Commands4344Each command's playbook is `reference/<command>.md` (`audit` and `adapt` also have a `.native.md` variant); descriptions in [reference/commands.md](reference/commands.md).4546- **Build:** `shape`, `init`, `document`, `extract`, `craft` (deprecated alias)47- **Evaluate:** `critique`, `audit`48- **Refine:** `polish`, `bolder`, `quieter`, `distill`, `harden`, `onboard`49- **Enhance:** `animate`, `colorize`, `typeset`, `layout`, `delight`, `overdrive`50- **Fix:** `clarify`, `adapt`, `optimize`51- **Iterate:** `live`, `generate [n] [action] [element]`5253Routing:5455- **No argument:** read [routing.md](reference/routing.md) and present its context-aware menu; never auto-run a command.56- **Explicit or clearly implied request to run a command:** load its reference (native variant on native platforms) and follow it. Ask once if two commands fit.57- **Workflow or command-selection question:** read [Workflow questions](reference/routing.md#workflow-questions).58- **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 `impeccable context` directs, offering init afterward rather than blocking on it.59- `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.6061After init writes PRODUCT.md, resume without rerunning `impeccable context`; init loads the native platform reference itself when the platform it recorded is `ios`, `android`, or `adaptive`.6263**Hooks / Doctor:** `/impeccable hooks <args>` (the design detector hook): load [reference/hooks.md](reference/hooks.md) on any argument. `/impeccable doctor`, or a question about what is out of date or stale: load [reference/doctor.md](reference/doctor.md).6465**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.