Impeccable
External upstream integration. This repository did not create Impeccable. The original project is pbakaus/impeccable; retain its attribution and Apache-2.0 license when copying or adapting this skill.
Goal
Use the upstream Impeccable design language and command set for frontend design, critique, audit, refinement, accessibility, responsive behavior, typography, layout, motion, and production polish.
Input
- a frontend project or UI target;
- the requested Impeccable operation, such as
init, shape, critique, audit, polish, harden, adapt, or optimize;
- the current agent harness/provider when project-local installation is required.
Output
Return the requested design result or code change using the upstream Impeccable workflow. Report any project files created or changed by Impeccable setup separately from the UI work.
Workflow
- Read references/upstream.md for the pinned source, supported providers, install/update commands, and provenance.
- Prefer an existing project-local Impeccable installation when present. Do not replace or duplicate it with a hand-maintained client-specific copy.
- If the user asks to enable Impeccable for a project, detect the active supported provider and run the maintained upstream installer from the project root:
npx impeccable install --providers=<provider> --scope=project.
- Reload the harness when its discovery model requires it, then use the upstream
impeccable skill and its command routing as the authority for design work.
- Start new projects with
impeccable init so product and design context are durable. For existing projects, preserve the incumbent visual system unless the user explicitly requests a redesign.
- For updates, use
npx impeccable update rather than copying generated provider trees by hand.
Rules
- The upstream Impeccable package and CLI own Impeccable-specific behavior. Do not fork its generated
.agents, .claude, .codex, .cursor, .opencode, or other provider trees into this repository.
- Do not silently install or update Impeccable as a side effect of an unrelated task. Project-local installation is a repository mutation and requires user intent.
- Preserve user-specified brand, product, accessibility, framework, and platform constraints.
- Keep verification bounded: inspect, batch fixes, confirm once when practical, then stop rather than entering an open-ended polish loop.
- When refreshing this integration, update the upstream version/revision metadata and attribution together.
1---2name: impeccable3description: design, frontend, ui, ux, audit, polish, accessibility, impeccable4license: Apache-2.05---67# Impeccable89> External upstream integration. This repository did not create Impeccable. The original project is `pbakaus/impeccable`; retain its attribution and Apache-2.0 license when copying or adapting this skill.1011## Goal1213Use the upstream Impeccable design language and command set for frontend design, critique, audit, refinement, accessibility, responsive behavior, typography, layout, motion, and production polish.1415## Input1617- a frontend project or UI target;18- the requested Impeccable operation, such as `init`, `shape`, `critique`, `audit`, `polish`, `harden`, `adapt`, or `optimize`;19- the current agent harness/provider when project-local installation is required.2021## Output2223Return the requested design result or code change using the upstream Impeccable workflow. Report any project files created or changed by Impeccable setup separately from the UI work.2425## Workflow26271. Read [references/upstream.md](references/upstream.md) for the pinned source, supported providers, install/update commands, and provenance.282. Prefer an existing project-local Impeccable installation when present. Do not replace or duplicate it with a hand-maintained client-specific copy.293. If the user asks to enable Impeccable for a project, detect the active supported provider and run the maintained upstream installer from the project root: `npx impeccable install --providers=<provider> --scope=project`.304. Reload the harness when its discovery model requires it, then use the upstream `impeccable` skill and its command routing as the authority for design work.315. Start new projects with `impeccable init` so product and design context are durable. For existing projects, preserve the incumbent visual system unless the user explicitly requests a redesign.326. For updates, use `npx impeccable update` rather than copying generated provider trees by hand.3334## Rules3536- The upstream Impeccable package and CLI own Impeccable-specific behavior. Do not fork its generated `.agents`, `.claude`, `.codex`, `.cursor`, `.opencode`, or other provider trees into this repository.37- Do not silently install or update Impeccable as a side effect of an unrelated task. Project-local installation is a repository mutation and requires user intent.38- Preserve user-specified brand, product, accessibility, framework, and platform constraints.39- Keep verification bounded: inspect, batch fixes, confirm once when practical, then stop rather than entering an open-ended polish loop.40- When refreshing this integration, update the upstream version/revision metadata and attribution together.
lost-rob0t