Skip to main content

Overview

Impeccable is distributed as provider-specific bundles optimized for each AI tool. This guide covers installation for all 4 supported providers.
Recommended: Download from impeccable.style for ready-to-use bundles with automatic updates.

Choose Your Provider

Cursor

AI-first code editor

Claude Code

Browser-based coding assistant

Gemini CLI

Google’s command-line tool

Codex CLI

OpenAI’s command-line tool

Cursor

Cursor supports the Agent Skills standard. Impeccable installs as skills in your project’s .cursor/ directory.

Requirements

Cursor skills require Nightly channel and Agent Skills to be enabled. Standard releases don’t support skills yet.
1

Switch to Nightly Channel

  1. Open Cursor Settings
  2. Go to Beta section
  3. Switch to Nightly channel
  4. Restart Cursor
2

Enable Agent Skills

  1. Open Cursor Settings
  2. Go to Rules section
  3. Enable Agent Skills

Installation

Usage

Once installed, use commands in Cursor’s chat:
/audit components/Button.jsx
/polish src/pages/Landing.tsx
/animate dashboard
Commands work project-wide. The skills are automatically loaded when you use them.

Troubleshooting

  1. Verify you’re on Nightly channel (Settings → Beta)
  2. Ensure Agent Skills is enabled (Settings → Rules)
  3. Restart Cursor completely
  4. Check .cursor/skills/ directory exists
Skills must follow the Agent Skills standard. Verify SKILL.md files have proper frontmatter:
---
name: audit
description: Perform comprehensive audit...
user-invokable: true
---

Claude Code

Claude Code has native support for skills in .claude/ directories. Works both project-specific and globally.

Requirements

No special setup required! Claude Code automatically detects skills.

Installation

Usage

Commands work in Claude Code’s chat:
/audit components/Dashboard.tsx
/polish checkout flow
/animate hero section
Claude Code shows available skills when you type /. Commands autocomplete automatically.

Troubleshooting

  1. Verify .claude/skills/ directory exists in your project or ~/.claude/skills/ globally
  2. Check SKILL.md files have proper YAML frontmatter
  3. Refresh Claude Code (reload the page)

Gemini CLI

Gemini CLI uses TOML format for commands and modular imports for skills.

Requirements

Gemini CLI skills require preview version and manual skill enablement.
1

Install Preview Version

npm i -g @google/gemini-cli@preview
2

Enable Skills

# Run Gemini CLI
gemini

# In the CLI:
/settings

# Enable "Skills" option
# Exit and restart

Installation

Usage

Commands in Gemini CLI use standard slash syntax:
/audit components/Header.tsx
/polish navigation
/animate page transitions
Gemini CLI uses modular imports. Main GEMINI.md file imports skill modules using @./GEMINI.*.md syntax.

Troubleshooting

  1. Verify you’re on preview version: gemini --version
  2. Check skills are enabled in /settings
  3. Run /skills list to see loaded skills
  4. Verify .gemini/commands/ contains .toml files
Gemini expects GEMINI.md and modular files in project root:
your-project/
├── GEMINI.md                    # Main import file
├── GEMINI.frontend-design.md   # Skill modules
└── .gemini/                     # Commands directory
    └── commands/

Codex CLI

Codex CLI uses a custom prompt format and invokes commands with /prompts: prefix.

Requirements

Codex CLI works with standard installation. No special setup required.

Installation

Usage

Codex CLI uses different syntax: /prompts:<name> instead of /<name>
Commands in Codex CLI:
/prompts:audit components/Layout.tsx
/prompts:polish dashboard
/prompts:animate transitions
The /prompts: prefix tells Codex to use your custom prompts from ~/.codex/prompts/.

Troubleshooting

  1. Verify files exist in ~/.codex/prompts/
  2. Check frontmatter format (uses description and argument-hint, not args array)
  3. Run /prompts:list to see available prompts
Remember: Codex uses /prompts:audit, not /auditThe : is required to invoke custom prompts.

Universal Bundle

Want to support multiple tools? Use the universal bundle.
1

Download Universal Bundle

Visit impeccable.style and click Download Universal.
2

Extract to Project

unzip impeccable-universal.zip -d your-project/
This creates all provider directories:
your-project/
├── .cursor/
├── .claude/
├── .gemini/
├── .codex/
└── README.txt
3

Commit to Version Control

git add .cursor/ .claude/ .gemini/ .codex/
git commit -m "Add Impeccable skills for all providers"
Now your team can use whichever tool they prefer!
The universal bundle includes all providers in a single ZIP. Perfect for teams using multiple tools.

Prefixed Installation

If you have existing commands with conflicting names, use the prefixed bundle:
1

Download Prefixed Bundle

Visit impeccable.style and click Download (Prefixed).
2

Extract and Use

Commands are prefixed with i-:
/i-audit
/i-polish
/i-animate
Prefixed bundles work identically, just with i- prefix to avoid naming conflicts.

Verification

After installation, verify everything works:
1

Check Directory Structure

ls -la .cursor/skills/
# Should show: frontend-design, audit, polish, etc.
2

Test a Command

Create a simple test file and run /audit:
test.jsx
export function Button() {
  return <button style={{ color: '#999' }}>Click</button>;
}
Then run:
/audit test.jsx
You should get a detailed audit report with anti-pattern warnings.
3

Verify Skill Loading

Ask your AI:
What design principles does the frontend-design skill include?
If the skill is loaded, you’ll get a detailed response about typography, color, spatial design, etc.

Updating

To update to the latest version:
1

Download Latest Bundle

Visit impeccable.style and download the latest version.
2

Backup Existing Installation

# Backup current installation
mv .claude/ .claude.backup/
# Or for Cursor:
mv .cursor/ .cursor.backup/
3

Extract New Version

unzip ~/Downloads/impeccable-[provider].zip -d .
4

Verify and Clean Up

# Test new installation
# If working, remove backup:
rm -rf .claude.backup/

Next Steps

Quick Start

Try your first command in under 5 minutes

Command Reference

Complete guide to all 17 commands

Design Principles

Deep dive into the skill’s design guidelines

Best Practices

Tips and workflows for effective usage

Build docs developers (and LLMs) love