content / skill

Impeccable

Add one skill with 24 design commands and a rule-based detector for AI-generated frontend design to your coding agent.

Repository owner pbakaus

Not rated yet
0 comments

Like 0 Save

Published 11 Oct 2026Listing updated 12 Oct 2026

At a glance

Purpose: Add one skill with 24 design commands and a rule-based detector for AI-generated frontend design to your coding agent.
Runs in: Local agent with shell, Web service
Operating systems: Not stated
Needs: Runtime: Not stated; Needs internet: Not stated; Needs accounts or API keys beyond your agent: No
Files and data: Reads files: Yes; Writes files: Yes; Sends data to other services: Not stated
Tool type: Skill
Delivery: From GitHub
Version: Latest on the main branch
Access: Code on GitHub
Compatibility: According to the README, it supports Cursor, Claude Code, GitHub Copilot, DeepSeek Harness, Gemini CLI, Codex CLI, Grok Build, Hermes Agent, OpenCode, Pi, Kiro, Trae, Rovo Dev, Qoder, Mistral Vibe, Veto and Google Antigravity. It installs a provider-native hook for Claude Code, GitHub Copilot, Codex, Cursor and Grok Build. The README says Veto does not run the edit hooks and Hermes has no hook surface.
External costs: The repository is Apache-2.0-licensed and states no pricing. The README says the CLI and browser extension run the deterministic rules with no LLM and no API key. Your coding agent or model provider may charge for usage.
Permissions: The skill acts through your coding agent with the access you give it. According to the README, the installer writes skill folders and hook files into your project or home folder, such as .claude/settings.local.json, .cursor/hooks.json and .codex/hooks.json, and the hook runs a launcher when UI files are edited. The README says Claude Code hooks run independently of model tool approval, so the first edit or Stop event can download and cache the engine. In live mode, applying copy edits can run an optional package.json script named impeccable:manual-edit-validate in a shell with your user permissions. Working files are written under .impeccable/ in your project.
Usage terms: Apache License 2.0, as stated in the repository. See its LICENSE file for the exact terms.

Code on GitHub

pbakaus/impeccable

Apache-2.0

JavaScript80,326 stars4,784 forksLast pushed 12 Oct 2026 UTC

The design language that makes your AI harness better at design.

Public GitHub data fetched 13 Oct 2026 UTC · 0 days old

View on GitHub ↗

What it does

Impeccable is design guidance for AI coding agents. According to the README, it ships one skill, invoked as /impeccable, with 24 commands, live browser iteration and 59 deterministic detector rules for AI-generated frontend design.

The README lists commands including shape, craft, critique, audit, polish, distill, bolder, quieter, typeset, layout, colorize, animate, clarify, adapt, optimize, harden, init, document and extract. The init command writes durable product context to a PRODUCT.md file, and the document command generates a DESIGN.md from existing code. You can pin a command as a standalone shortcut.

The README also describes a standalone command-line detector that checks files, directories or a URL without an AI harness, a browser extension, and design hooks for some agents that run the detector when you edit UI files.

Who it is for

Developers who build frontends with AI coding agents and want a shared set of design commands and checks.

Example tasks

Run /impeccable init to record product context in PRODUCT.md.
Audit a page, for example /impeccable audit blog.
Get a UX design review with /impeccable critique landing.
Do a final pass before shipping, for example /impeccable polish settings.
Detect design anti-patterns in a directory with npx impeccable detect src/.

Getting started

According to the README, run npx impeccable install from your project root, then run /impeccable init inside your AI coding tool. npx impeccable update refreshes an existing install. The README also describes a Git submodule route, a Claude Code plugin route with /plugin marketplace add pbakaus/impeccable, a Grok Build plugin route, a VS Code extension, a download from the project website and manual copy steps for each tool. The README has the exact commands.

Limitations

According to the README, the skill needs no runtime of its own. A small launcher runs the Impeccable engine, a self-contained binary that sits next to the launcher or is downloaded once on first run into ~/.impeccable/bin/. Node is needed only for the npx installer and CLI. The README says Codex users should open /hooks after install or update and approve the project hook when prompted, Grok Build users need folder trust, and Hermes gates project-local skills behind a per-repo trust decision. Cursor and Gemini CLI skills need beta or preview settings, and the VS Code extension needs VS Code 1.109.3 or later, Copilot Chat access and a trusted local workspace. Live mode works on a local checkout and is not supported on deployed production sites. Scanning a URL with the detector uses an installed Chrome, Chromium or Edge. The README says a clean detector run is evidence, not proof of visual or accessibility quality. The repository can change at any time; check its README before you install.

Data practices

According to the README, the CLI and browser extension run the deterministic rules with no LLM and no API key, and the launcher downloads the engine once on first run if it is not already next to the launcher. Working files such as screenshots, caches and session state are written under .impeccable/ in your project. The README does not mention telemetry or describe what your agent and model provider receive. That depends on your coding agent and model provider.