Automatic design checks | Impeccable

Catch design problems while your agent works.
Design hooks run the detector during your agent’s work on UI files. Findings give the agent a chance to correct a problem while the change is still in context.
Turning checks on in Impeccable is one step. Review the setup for your tool so the hook can run.
In your AI coding tool, check the current setup:
Enable or disable checks for this project:
In an interactive session, accept workspace trust. Open /hooks to inspect Impeccable’s PostToolUse and Stop hooks. Project installs normally use .claude/settings.local.json; plugin installs can supply their own hooks.
Claude Code’s hook and trust guidance
Open Settings → Hooks in the app, or /hooks in the CLI. Review and trust Impeccable’s PostToolUse and Stop hook definitions. New or changed definitions need review again.
Codex’s hook and trust guidance
Trust the workspace, then check Customize → Hooks for the project’s .cursor/hooks.json. Cursor reloads this file when it changes. If it still does not appear, restart Cursor and check the Hooks output channel.
Cursor’s hook guidance
Commit .github/hooks/impeccable.json and merge it into the repository’s default branch. This is a shared project hook used by Copilot CLI and the cloud agent. In the CLI, also accept the folder’s trust prompt.
Copilot’s hook setup guidance
Run /hooks-trust to review and trust the project hooks in .grok/hooks/. Use /hooks to inspect the loaded hooks.
Grok Build’s hook guidance
The hook checks supported edits to components and styles.
It identifies the problem and provides a correction direction.
It can fix the issue, or explain an intentional choice.
For Claude Code and Codex, the per-edit pass focuses on immediate problems: broken images, overflow, poor legibility, gradient text, glow, and design-system drift. Broader checks run on the session’s touched UI files at the Stop event, when the agent finishes responding. Previously reported findings are filtered out.
This gives unfinished work room to develop without repeating every observation after every edit. A later stop stays quiet if there is nothing new to report.
Set hook.perEditRules to "all" for the full rule set after each edit. Cursor and Copilot already use the full set because Impeccable does not defer their findings to a Stop pass. Grok delivers feedback through Stop even when it scans during edits.
Hooks check web code. They skip projects whose PRODUCT.md declares ios, android, or adaptive. Use audit for native interface reviews.
After installing or moving a project, run doctor:
It can find a hook whose script path no longer exists, or a mismatch between its installed configuration and enabled state. No messages can mean a clean edit, quiet mode, or an inactive hook; silence alone does not tell you which.
For a confirmed exception, record the specific value and why it belongs:
The exception is shared with manual detector scans. Configuration & ignores explains narrower file scopes, private exceptions, and broader rule or file exclusions.
Built-in file types are .tsx, .jsx, .html, .vue, .svelte, .astro, .css, .scss, .sass, .less, .ts, and .js. Plain JS and TS stay quiet unless a design issue is found.
Add server-side template types through detector.extensions.
To skip hook setup for one install or update:
Runtime options live under hook in .impeccable/config.json. Local overrides, including installation consent, live in the gitignored .impeccable/config.local.json.
hook.quiet: true silences clean and pending acknowledgements while keeping new findings. It does not turn checks off.
For debugging, set hook.auditLog to a path such as .impeccable/hook.ndjson. Each invocation writes one JSON line. Leave logging off during normal work.
IMPECCABLE_HOOK_DISABLED, IMPECCABLE_HOOK_QUIET, and IMPECCABLE_HOOK_LOG override the corresponding config settings for processes that receive those environment variables. Status reports relevant overrides.
Install and update stop rather than overwrite a malformed manifest. Inspect the file first. If you choose to replace it, rerun with --force; Impeccable backs up the malformed file with a .bak extension before replacing it.