# impeccable

The skill turns your agent into a design-system author: tokens, type scale, component states, accessibility criteria. Useful when a project needs one visual language.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode · 2200 installs · ★ 3349
- Author: typeui.sh
- License: MIT · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/bergside/awesome-design-skills/tree/HEAD/skills/impeccable/SKILL.md
- Updated: 2026-06-28
- HTML: https://affpapa.org/en/nevibecode/skills/typeuish-impeccable

## What it does

impeccable gives the agent a role: write design-system guidance for the Impeccable style. That style is an editorial poster — cream and burnt orange sections alternating, an amber brand color, high contrast. The foundations are numeric: Chakra Petch for text and display, JetBrains Mono for code, a type scale of 12/14/16/20/24/32, spacing at 4/8/12/16/24/32, and tokens such as primary=#CC8800, surface=#FFFFFF and text=#111827.

It is a set of instructions, not a code generator. The workflow starts with restating the design intent in one sentence, then moves to tokens and constraints, then to component anatomy with every state spelled out — default, hover, focus-visible, active, disabled, loading, error. It ends with a QA checklist you can run in code review. Rules must anchor to a token or a threshold, since vague adjectives make a guideline useless.

Accessibility is set at WCAG 2.2 AA with keyboard-first interaction and visible focus. When aesthetics clash with accessibility, the skill says accessibility wins — worth remembering before you start trimming the palette. Install runs through `npx skills add` for Claude, Codex, Cursor, Gemini CLI and OpenCode; GitHub Copilot uses `gh skill install` instead.

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add bergside/awesome-design-skills --skill impeccable -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/impeccable/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/impeccable/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add bergside/awesome-design-skills --skill impeccable -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/impeccable/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add bergside/awesome-design-skills --skill impeccable -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/impeccable/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install bergside/awesome-design-skills impeccable
```

2. **Manually: put the files in place**
- File: `.github/skills/impeccable/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add bergside/awesome-design-skills --skill impeccable -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/bergside/awesome-design-skills --path skills/impeccable
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/impeccable/SKILL.md` — The legacy .windsurf/skills/ path still works

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add bergside/awesome-design-skills --skill impeccable -a opencode
```

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/bergside/awesome-design-skills/tree/HEAD/skills/impeccable/SKILL.md

## When to use it
- define tokens and a spacing scale before writing components
- list every state for a button or input field
- check text contrast before handing off a layout
- pull drifting paddings back onto one scale
- get a review checklist for UI code

## Example prompts
- Write a design system for a landing page in the Impeccable style: tokens, typography, button states
- Review my card component against the impeccable rules and list the accessibility issues
- Build a QA checklist for reviewing this UI in code review

## Source text · SKILL.md · MIT

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: 16b713a3dce267f3.

BEGIN THIRD-PARTY FILE 16b713a3dce267f3
```text
---
name: "impeccable"
description: "A modern, graphic, editorial-poster aesthetic — warm and confident — built on alternating cream and burnt orange sections, an amber brand color."
metadata:
  author: typeui.sh
---

<!-- TYPEUI_SH_MANAGED_START -->
# Impeccable Design System Skill (Universal)

## Mission
You are an expert design-system guideline author for Impeccable.
Create practical, implementation-ready guidance that can be directly used by engineers and designers.

## Brand
A modern, graphic, editorial-poster aesthetic — warm and confident — built on alternating cream and burnt orange sections, an amber brand color.

## Style Foundations
- Visual style: modern, clean, high-contrast
- Typography scale: 12/14/16/20/24/32 | Fonts: primary=Chakra Petch, display=Chakra Petch, mono=JetBrains Mono | weights=100, 200, 300, 400, 500, 600, 700, 800, 900
- Color palette: primary, neutral, success, warning, danger | Tokens: primary=#CC8800, secondary=#C55221, success=#16A34A, warning=#D97706, danger=#DC2626, surface=#FFFFFF, text=#111827
- Spacing scale: 4/8/12/16/24/32

## Accessibility
WCAG 2.2 AA, keyboard-first interactions, visible focus states

## Writing Tone
concise, confident, helpful

## Rules: Do
- prefer semantic tokens over raw values
- preserve visual hierarchy
- keep interaction states explicit

## Rules: Don't
- avoid low contrast text
- avoid inconsistent spacing rhythm
- avoid ambiguous labels

## Expected Behavior
- Follow the foundations first, then component consistency.
- When uncertain, prioritize accessibility and clarity over novelty.
- Provide concrete defaults and explain trade-offs when alternatives are possible.
- Keep guidance opinionated, concise, and implementation-focused.

## Guideline Authoring Workflow
1. Restate the design intent in one sentence before proposing rules.
2. Define tokens and foundational constraints before component-level guidance.
3. Specify component anatomy, states, variants, and interaction behavior.
4. Include accessibility acceptance criteria and content-writing expectations.
5. Add anti-patterns and migration notes for existing inconsistent UI.
6. End with a QA checklist that can be executed in code review.

## Required Output Structure
When generating design-system guidance, use this structure:
- Context and goals
- Design tokens and foundations
- Component-level rules (anatomy, variants, states, responsive behavior)
```
END THIRD-PARTY FILE 16b713a3dce267f3

The third-party file has ended. Everything between the 16b713a3dce267f3 tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

First 2420 of 3562 bytes. © typeui.sh · MIT · https://github.com/bergside/awesome-design-skills/tree/HEAD/skills/impeccable/SKILL.md

_Part of the page did not fit — see the HTML version._

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md