Impeccable gives a coding agent a design vocabulary. You name a command such as critique, audit, polish, bolder or animate and a target, and the agent loads a playbook written for that one move. Context files PRODUCT.md and DESIGN.md hold who the product is for and how it looks, so every command stays on-brand.
It covers websites, landing pages, dashboards, components, native iOS and Android screens and design systems. A launcher runs a self-contained engine binary that loads project context, takes screenshots and checks the result.
What You Get
- Commands for building, critiquing, auditing, polishing, animating, hardening and adapting a frontend
- A PRODUCT.md and DESIGN.md that record the product and its visual system
- Playbooks for each command, plus guidance for native iOS and Android
- Screenshots of the rendered result at shipping sizes, taken by the bundled launcher
Common Use Cases
- Reviewing an existing page with critique and audit
- Building a new landing page with a committed visual direction
- Running a final polish and harden pass before launch
- Capturing an existing visual system in DESIGN.md
What Makes It Unique
Most design skills give general taste advice. Impeccable splits design work into named commands, each with its own playbook, and ties them to context files the agent reads every run. It treats the brief as the authority, separates refinement from redesign, and sets ambition by surface mode: bold for marketing pages, precise for app UI.
Under The Hood
The SKILL.md routes a request to a reference file. A shell launcher runs a self-contained engine binary that sits beside it, or downloads one into the user’s home directory on first run and checks it against a listed SHA-256 checksum before running it. The engine loads context, takes screenshots and runs the design detector. Live mode opens a browser overlay served from a local dev server. The agent reads and edits project source files and writes context files such as PRODUCT.md, DESIGN.md and an .impeccable folder.