--- name: impeccable-studio description: "Use Impeccable for interface critique, audit, polish, typesetting, layout, onboarding, copy clarity, motion and responsive hardening. Route to the complete pinned playbook and distinguish its optional engine and hooks from bundled instructions." --- # Impeccable studio Read `../../vendor/impeccable/SKILL.md`; use `/vendor/impeccable` as its skill base directory. Select the exact command reference from its table. For example, load `reference/critique.md` for UX judgment, `reference/audit.md` for technical findings, `reference/polish.md` for finish, `reference/harden.md` for error states and `reference/typeset.md` for type. Load the craft floor before editing an interface. Choose Persuade, Operate, Read or Experience from the surface's job. Preserve the owning brand pack, approved copy and behavior. Rank findings by effect on the actual user journey, then fix the important ones within scope. The bundled launcher can download a checksum-verified native engine on first run. Inspect it and available network/runtime capability before executing; do not install hooks, alter host settings, enable telemetry, or install a provider integration as an incidental effect. When the launcher cannot run, read existing PRODUCT.md, DESIGN.md and applicable references directly and report that engine detection did not run. Continue authorized work. Keep live mode limited to a local checkout. Never inject it into a deployed site or relax production CSP. Catalog fetches and engine download are separate network effects; telemetry-disabled does not mean offline. Read engine findings as diagnostics, not release approval. Verify fixes in a real browser with `../browser-verify/SKILL.md`, including keyboard, mobile, empty/loading/error states and reduced motion. Preserve the Apache license and NOTICE.md; upstream platform material has its own retained attribution.