---
import Base from '../layouts/Base.astro';
import '../styles/sub-pages.css';
import '../styles/changelog-faq-kinpaku.css';
---
Support
Installation, updates, troubleshooting, and the questions newcomers ask first. Each answer is deep-linkable.
The easiest way is npx impeccable install, which shows the harness folders it detected, lets you keep or customize the provider list, and asks whether to install in the current project or globally. Use --scope=project or --scope=global for non-interactive installs.
If you downloaded the universal ZIP, extract it to your project root (same level as your package.json or src/ folder). It creates hidden folders for each supported tool: .cursor/, .claude/, .gemini/, .codex/, .agents/, and .github/.
Project-level installation takes precedence and lets you version control your skills.
Run npx impeccable update from your project root. It downloads the latest skills and cleans up deprecated files. Not sure you're behind? npx impeccable check compares what you have installed against the latest release first.
npx impeccable install --force installs fresh./plugin in Claude Code.npx skills add pbakaus/impeccable also works, but installs one shared build for all harnesses rather than the one compiled for yours.Your PRODUCT.md and DESIGN.md context files are never overwritten.
/critique directly. How do I get that back?Pinning is built in. Run /impeccable pin critique and /critique becomes a standalone shortcut again, without reversing the consolidation.
Under the hood it writes a lightweight redirect skill that delegates to /impeccable critique, so updates to the parent skill flow through automatically. It works for every command.
Examples:
/impeccable pin polish → /polish works again/impeccable pin audit → /audit works again/impeccable pin live → /live works againTo remove: /impeccable unpin critique. To see your current pins, check your harness skills directory (.claude/skills/, .cursor/skills/, etc.) for directories named after the command you pinned, like .claude/skills/critique/.
For commands: Type /impeccable in your AI harness and look for commands like /impeccable audit, /impeccable polish, etc. If they don't appear, double-check the files are in the correct location.
For skills: Skills are applied automatically when relevant. To verify, explicitly mention "use the impeccable skill" in your prompt. This forces the AI to acknowledge and apply it.
Tool-specific setup:
@google/gemini-cli@preview + Skills enabled via /settings/ command picker. Open /skills or type $. Repo installs live in .agents/skills/, user installs live in ~/.agents/skills/. Restart Codex if a new skill does not show up.Skills and commands are intermediate features. If you're just getting started, learn the basics first:
Once you're comfortable with basic prompting and code generation, come back and give Impeccable a try.
Yes. Everything is Apache 2.0: skills, commands, CLI, and the detection engine. Fully open source, free for everyone.