impeccable-stinger

Operates the Impeccable design system to build and audit frontend UI through a four-phase loop.

84|37|Updated May 23, 2026
One-click install
npx skills add https://github.com/legioncodeinc/vibe-coding-tools --skill impeccable-stinger-legioncodeinc
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: impeccable-stinger
Source: https://github.com/legioncodeinc/vibe-coding-tools/tree/main/src/skills/impeccable-stinger
Command: npx skills add https://github.com/legioncodeinc/vibe-coding-tools --skill impeccable-stinger-legioncodeinc

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires impeccable, and includes scripts (resource) and references (resource) components.

What problem does it solve? AI-generated frontend design tends to repeat the same recognizable patterns and skip quality checks. This Skill runs the Impeccable design operating system (pbakaus/impeccable, Apache-2.0) as a disciplined workflow so UI work stays cohesive with the project's design system and passes a deterministic 59-rule anti-slop detector gate before shipping. ## Core Features & Use Cases - Four-phase design loop: Start (context contract via PRODUCT.md and DESIGN.md, job classification, direction contract), Iterate (23 named commands like polish, typeset, layout, colorize), Polish (audit, clarify, harden), and Maintain (extract, document, doctor). - Deterministic quality gate: Runs npx impeccable detect <target> against files, directories, or URLs; exit code 2 blocks close-out until findings are fixed or waived with a stated reason. - Hooks and live mode: Per-edit and end-of-session detector hooks for Claude Code, Cursor, Codex, and Copilot, plus opt-in browser-based live iteration with three variants per element. - Use Case: You ask for a new pricing page. The Skill ensures the context contract exists, classifies the job as a new surface, rolls a grounded design direction, builds it, runs audit and the detector gate, then hands off to security and quality review. ## Quick Start Ask the agent to design or refine a frontend page or component, for example: build a pricing page for my developer tool and run the impeccable detector gate before finishing.

Frequently Asked Questions about impeccable-stinger

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run the Impeccable anti-slop detector on my frontend code?▼

Run npx impeccable detect followed by a file, directory, or URL target. Exit code 0 means no findings, exit code 2 means findings that must be fixed or waived with a reason, and exit code 1 means the command failed. Use --json for CI pipelines.

What is the Impeccable four-phase design workflow?▼

The loop is Start, Iterate, Polish, Maintain. Start establishes PRODUCT.md and DESIGN.md context and a direction contract, Iterate applies named commands like polish or typeset in bounded rounds, Polish runs audit and the detector gate, and Maintain consolidates drift with extract and document.

Does the Impeccable detector work with React, Vue, and Svelte files?▼

Yes, the detector scans JSX, TSX, Vue, Svelte, Astro, HTML, and CSS files using static-html, browser, and regex engines. It is web-only; native iOS and Android projects route to the native audit pass instead.

How do I waive a detector finding for a brand font?▼

Use the narrowest ignore form with a stated reason, for example npx impeccable ignores add-value overused-font "Brand Sans" --reason "Brand font, committed in DESIGN.md". Waivers are recorded in .impeccable/config.json, and a waiver without a reason is treated as a failure.

When should I not use this design workflow?▼

Do not use it for backend-only or non-UI tasks, since every command and the detector target frontend surfaces. Product-specific design-token enforcement belongs to dedicated design-system skills rather than this general design operating loop.

Why does the Impeccable hook seem installed but report nothing?▼

A hook whose script path stops resolving still registers in the manifest but scans nothing, so silence reads as a clean codebase. Run /impeccable doctor to detect broken hook paths, stale config, and schema drift.