How to Install and Use Impeccable Design Skills

Mar 20, 2026

I spent an hour trying to figure out why my /audit command wasn’t working in Claude Code. Turns out I had installed the Impeccable skills to the wrong directory. Here’s how to get design skills working across different AI development environments.

The Problem

I wanted to use Impeccable’s design audit and polish commands in my AI workflow. The documentation said “install the bundle,” but each AI provider has a different installation path and requirements. After several failed attempts, I finally got it working.

Understanding Impeccable Skills

Impeccable provides a set of design-focused AI skills that help you:

Audit your design for issues
Normalize inconsistencies
Polish the final result
Distill complexity

These skills work across multiple AI development environments, but each has its own installation quirks.

Claude Code Installation

Claude Code offers two installation options: project-specific or global.

Project-specific installation keeps skills local to one project:

# Download the bundle first
curl -L -o impeccable-bundle.zip https://impeccable.style/download

# Extract and copy to your project
unzip impeccable-bundle.zip
cp -r dist/claude-code/.claude your-project/

Global installation makes skills available across all projects:

# Install globally
cp -r dist/claude-code/.claude/* ~/.claude/

After installation, restart Claude Code and test:

> /audit

If the command works, you’ll see a design analysis of your current context.

Cursor Installation (Requires Nightly)

Here’s where I got stuck. Cursor requires switching to the Nightly channel first.

Step 1: Enable Nightly Channel

Open Cursor settings:

Navigate to Settings → Beta
Enable “Nightly Channel”
Restart Cursor

Step 2: Enable Agent Skills

After restart:

Go to Settings → Rules
Enable “Agent Skills”

Step 3: Install the Skills

cp -r dist/cursor/.cursor your-project/

Without the Nightly channel, the .cursor directory structure won’t be recognized. I learned this the hard way.

Gemini CLI Installation

Gemini CLI requires the preview version for skills support.

# Install preview version
npm i -g @google/gemini-cli@preview

# Install skills
cp -r dist/gemini/.gemini your-project/

Enable skills through the interface:

> /settings
# Navigate to Skills section
# Enable skills

Codex CLI Installation

Codex CLI uses a slightly different command syntax:

# Install to global config
cp -r dist/codex/.codex/* ~/.codex/

The key difference is command syntax:

# Codex uses /prompts: prefix
/prompts:audit
/prompts:normalize
/prompts:polish
/prompts:distill

Available Commands

Once installed, these commands work across all providers (with syntax variations for Codex):

Command	Purpose
`/audit`	Find design issues
`/normalize`	Fix inconsistencies
`/polish`	Final cleanup
`/distill`	Remove complexity

Common Mistakes I Made

Mistake 1: Wrong Directory

I installed to ~/.claude/skills/ instead of ~/.claude/. The skills need to go directly in the config directory, not a subdirectory.

Mistake 2: Forgot to Enable Skills

In Cursor and Gemini CLI, skills must be explicitly enabled in settings. Installation alone isn’t enough.

Mistake 3: Wrong Provider Bundle

Each provider has its own bundle structure. Make sure you’re copying from dist/claude-code/ for Claude Code, dist/cursor/ for Cursor, etc.

Mistake 4: Codex Command Syntax

I kept typing /audit in Codex CLI when it should be /prompts:audit. Check your provider’s syntax.

Verification Checklist

After installation, verify everything works:

Restart your AI tool completely
Run /audit (or /prompts:audit for Codex)
Check that you get a design analysis response
If nothing happens, check the installation path matches your provider

Why This Matters

Design skills in AI tools help catch issues that code review might miss:

Inconsistent spacing and sizing
Color accessibility problems
Layout inconsistencies
Overly complex structures

Having these skills available in your AI assistant means you can get instant design feedback without context-switching to a separate tool.

Final Words + More Resources

My intention with this article was to help others share my knowledge and experience. If you want to contact me, you can contact by email: Email me

Here are also the most important links from this article along with some further resources that will help you in this scope:

Oh, and if you found these resources useful, don’t forget to support me by starring the repo on GitHub!