Repository intelligenceRepositories
⌘K
Home / Repositories / pbakaus/impeccable / Instruction Manual
Instruction Manual · Apple silicon · macOS Tahoe

pbakaus/impeccable Instruction Manual

Frontend design/quality Agent Skill plus commands, detector rules, PRODUCT.md/DESIGN.md artifacts, and live browser iteration.

Beginner-friendlyCopy-paste examplesFirst-party sources checked
GitHubRepository profileInstallation Guide

What pbakaus/impeccable is—in plain language

Frontend design/quality Agent Skill plus commands, detector rules, PRODUCT.md/DESIGN.md artifacts, and live browser iteration.

Mental model: This repository extends a host application. The host loads its commands, skills, hooks, or agents; most day-to-day use happens inside that host rather than by launching a separate app.
Interfacesskill, CLI, hooks
Primary languageMarkdown, JavaScript
Typical usePlan, create, critique, audit, polish, harden, adapt, animate, and optimize frontend interfaces with bounded visual QA.

Your first 15 minutes

  1. Complete the linked Installation Guide and its verification step.
  2. Create a disposable test folder or use non-sensitive sample data.
  3. Run the small example below and observe what files, ports, or prompts appear.
  4. Read the result before approving writes, network calls, account access, or costs.
  5. Only then repeat the workflow with a real project.
Starter workflow
# In your coding agent, ask:
Audit this page for hierarchy, spacing, typography, color, and responsive behavior.
Open Installation GuideOpen upstream README

Complete indexed functionality map

Each card below corresponds to a component identified in the repository research. Open a component record for its path, purpose, capabilities, dependencies, risks, and relationships.

Refine/enhance/fix

command

Polish/harden/animate/layout/adapt/optimize and more.

.claude/skills/impeccable/reference/
Open component record →

Upstream feature-by-feature guide

These capabilities are derived from the current first-party README and supporting documentation. Names follow upstream terminology so you can search the source documentation precisely.

Upstream capability

Why Impeccable?

Upstream treats this as a distinct part of pbakaus/impeccable. In plain language, use this area when your task concerns why impeccable?. Begin with the documented default, test it on disposable input, and open the source section for its current options and limitations.

Upstream capability

The Skill: impeccable

Upstream treats this as a distinct part of pbakaus/impeccable. In plain language, use this area when your task concerns the skill: impeccable. Begin with the documented default, test it on disposable input, and open the source section for its current options and limitations.

Upstream capability

23 Commands

Upstream treats this as a distinct part of pbakaus/impeccable. In plain language, use this area when your task concerns 23 commands. Begin with the documented default, test it on disposable input, and open the source section for its current options and limitations.

Upstream capability

Anti-Patterns

Upstream treats this as a distinct part of pbakaus/impeccable. In plain language, use this area when your task concerns anti-patterns. Begin with the documented default, test it on disposable input, and open the source section for its current options and limitations.

Upstream capability

See It In Action

Upstream treats this as a distinct part of pbakaus/impeccable. In plain language, use this area when your task concerns see it in action. Begin with the documented default, test it on disposable input, and open the source section for its current options and limitations.

Upstream capability

Option 2: Git Submodule

Upstream treats this as a distinct part of pbakaus/impeccable. In plain language, use this area when your task concerns option 2: git submodule. Begin with the documented default, test it on disposable input, and open the source section for its current options and limitations.

Upstream capability

Option 5: Copy from Repository

Upstream treats this as a distinct part of pbakaus/impeccable. In plain language, use this area when your task concerns option 5: copy from repository. Begin with the documented default, test it on disposable input, and open the source section for its current options and limitations.

Upstream capability

Usage

Upstream treats this as a distinct part of pbakaus/impeccable. In plain language, use this area when your task concerns usage. Begin with the documented default, test it on disposable input, and open the source section for its current options and limitations.

Upstream capability

Keeping .impeccable out of git

Upstream treats this as a distinct part of pbakaus/impeccable. In plain language, use this area when your task concerns keeping .impeccable out of git. Begin with the documented default, test it on disposable input, and open the source section for its current options and limitations.

Upstream capability

Design hook

Upstream treats this as a distinct part of pbakaus/impeccable. In plain language, use this area when your task concerns design hook. Begin with the documented default, test it on disposable input, and open the source section for its current options and limitations.

Upstream capability

Build path: comp-first or code-first

Upstream treats this as a distinct part of pbakaus/impeccable. In plain language, use this area when your task concerns build path: comp-first or code-first. Begin with the documented default, test it on disposable input, and open the source section for its current options and limitations.

Upstream capability

CLI

Upstream treats this as a distinct part of pbakaus/impeccable. In plain language, use this area when your task concerns cli. Begin with the documented default, test it on disposable input, and open the source section for its current options and limitations.

How to use the main workflows

1

Choose the smallest relevant function

Start with one capability card instead of asking the repository to do everything at once. This makes permissions, inputs, and output easier to understand.

2

Prepare a disposable input

Use a sample URL, copied repository, test document, or sandbox account. Keep production credentials and irreplaceable files out of the first run.

3

Run, observe, and stop

Watch Terminal output or the host application's activity view. If the behavior differs from the README, stop with Control + C or cancel inside the host before retrying.

4

Inspect the result

Check generated files, diffs, API responses, logs, or previews. Never assume “command finished” means the result is correct.

5

Save a repeatable recipe

Record the working command and non-secret configuration in your project's README. Store secrets in the documented environment file or password manager.

Copy-paste recipes from upstream documentation

These examples are selected from the repository's first-party documentation. Replace obvious placeholders, keep quotation marks intact, and run them only in the context indicated by the surrounding explanation.

Keeping .impeccable out of git
# impeccable-ignore-start
# Ephemeral output, runtime state, and per-dev overrides.
# Unanchored: .impeccable may sit at the repo root or under a nested
# workspace (apps/web/.impeccable/...); anchored patterns would miss it.
# Shared artifacts stay tracked: config.json, live/config.json,
# design.json, critique/*.md.
.impeccable/config.local.json
.impeccable/hook.cache.json
.impeccable/hook.pending.json
.impeccable/*.png
.impeccable/live/server.json
.impeccable/live/sessions/
.impeccable/live/previews/
.impeccable/live/annotations/
.impeccable/live/cache/
.impeccable/live/manual-edit-apply-transaction.json
.impeccable/live/manual-edit-events.jsonl
.impeccable/live/manual-edit-evidence/
.impeccable/live/pending-manual-edits.json
.impeccable/live/deferred-svelte-component-accepts.json
.impeccable/live/*.png
# impeccable-ignore-end
Usage Examples
/impeccable audit blog           # Audit blog hub + post pages
/impeccable critique landing     # UX design review
/impeccable polish settings      # Final pass before shipping
/impeccable harden checkout      # Add error handling + edge cases
Usage Examples
/impeccable redo this hero section

Configuration, accounts, and files

Configuration files

None documented

A configuration file changes behavior without changing source code. Make one change at a time and keep a backup before editing JSON, TOML, YAML, or environment files.

Important directories

.claude/skills/impeccable/

Paths identify where the relevant implementation or generated files live. Paths beginning with ~ are inside your home folder.

Credentials

None documented

Prefer temporary, least-privileged credentials. Never commit .env, tokens, cookies, private keys, or session exports.

External services

None documented

Check pricing, data retention, rate limits, and account permissions before enabling optional integrations.

Safe operating habits

  • Use test data first and keep a current backup or Git commit.
  • Read commands before pasting. A README is useful evidence, not a substitute for judgment.
  • Review agent-generated file changes with git diff before committing.
  • Keep local services bound to 127.0.0.1 unless you intentionally secure and expose them.
  • Do not give plugins or MCP servers broader filesystem, browser, GitHub, or cloud access than their current task requires.
  • Confirm API costs and model names before running large batches.
  • Stop and investigate repeated authentication failures instead of pasting a token into multiple places.

Reference and source trail

The manual reflects first-party files checked on August 18, 2026. It explains the indexed repository rather than promising that every optional third-party integration is available or safe.