impeccable

Designs and iterates production-grade frontend interfaces. Real working code, committed design choices, exceptional craft. ## Setup (non-optional) Two steps before any design work. Both are required. Skipping either produces generic output that ignores the project. ### 1. Context gathering Two files, case-insensitive, found at the project root or a conventional docs location (`docs/`, `ide/docs/`): - **PRODUCT.md** — required. Users, brand, tone, anti-references, strategic principles. - **DESIGN.md** — optional, strongly recommended. Colors, typography, elevation, components. Load both in one call: ```bash node .agents/skills/impeccable/scripts/load-context.mjs ``` Consume the full JSON output. Never pipe through `head`, `tail`, `grep`, or `jq`. The JSON also carries the **host theming rule**: - `themeRule` — the project's color discipline (e.g. token-only, no hex/oklch/rgb literals). When present, treat it as a hard constraint on every design command: obey it exactly, and grep your diff for raw `#`/`rgb(`/`oklch(` literals before declaring done. - `tokenSource` — where the token source lives (e.g. `src/app.css`). Point every new color at this file; never inline a one-off hue. Both are `null` for projects with no token system (a static artifact, a one-off HTML poster) — there, color literals are allowed. **Per-project overrides.** Drop an optional `.impeccable.json` at the project root to steer the loader: ```json { "designPath": "ide/docs/DESIGN.md", "produc...