# design

This skill builds a design manifest from a project’s styles or your preferences. A post-edit hook flags mismatches in edited files.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf (Devin Desktop), Claude.ai · ★ 937 repo stars
- Author: SethGammon
- License: MIT · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/SethGammon/Citadel/tree/HEAD/skills/design/SKILL.md
- Updated: 2026-10-29
- Security check: automated, 2026-11-16 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/skills/sethgammon-design

## What it does

In an existing project, the skill reads `tailwind.config.*`, global CSS, and component files, then asks you to review the patterns it found before writing. For a new project, it asks about visual feel, color mode, brand colors, and layout density. The manifest goes to `.planning/design-manifest.md`.

The `post-edit.js` hook checks edited CSS, TSX, JSX, and Tailwind files against that manifest. It warns about colors, font sizes, spacing, and radii outside the recorded values; it does not block edits. No manifest means no scan, and Tailwind utility classes mapped to the config are skipped. If `.planning/` cannot be created, the skill prints the manifest for you to save yourself.

## Install

### Claude Code (native platform)

1. **Plugin marketplace**
In the agent chat (not a shell):
```text
/plugin marketplace add SethGammon/Citadel
```
In the agent chat (not a shell):
```text
/plugin install citadel@citadel-local
```
This installs the whole citadel plugin with all its skills

2. **Skills CLI (Vercel)**
```bash
npx skills add SethGammon/Citadel --skill design -a claude-code
```

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

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add SethGammon/Citadel --skill design -a codex
```

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

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add SethGammon/Citadel --skill design -a cursor
```

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

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install SethGammon/Citadel skills/design
```

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

### Gemini CLI

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

2. **Platform CLI**
```bash
gemini skills install https://github.com/SethGammon/Citadel --path skills/design
```

### Windsurf (Devin Desktop)

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

### 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/SethGammon/Citadel/tree/HEAD/skills/design/SKILL.md

## When to use it
- extract a project’s styling rules into a manifest
- draft a starting manifest for a new interface
- spot colors or spacing outside the documented system
- refresh the manifest after styling changes

## Example prompts
- Build a design manifest from this project’s styles and show me the findings before saving.
- Create a starter manifest with a dark theme, dense layout, and these brand colors.
- Update the current manifest and show only what changed.

## 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: 9ca2b320761052f9.

BEGIN THIRD-PARTY FILE 9ca2b320761052f9
````text
---
name: design
license: MIT
description: >-
  Generates and maintains a design manifest for visual consistency. In existing
  projects, reads current styles and documents the design language. In new
  projects, asks a few questions and generates a starter manifest. The post-edit
  hook reads the manifest and flags deviations.
user-invocable: true
auto-trigger: false
trigger_keywords:
  - design
  - style guide
  - design manifest
  - visual consistency
effort: medium
---

# /design — Design Manifest Generator

## When to Use

- At the start of a new project (generate starter manifest from preferences)
- On an existing project that has no manifest (extract patterns from existing code)
- When visual inconsistency is noticed ("why do we have 4 different button styles?")
- When /do routes "design", "style guide", "visual consistency", "design manifest"

## Protocol

### Step 1: DETECT MODE

Check for existing styles: look for `tailwind.config.*`, global CSS files, or component files with style patterns. If any exist, use Extract Mode. If none exist or the user says "new project", use Generate Mode.

### Step 2: GATHER INPUT

**Extract Mode**: Read style sources (tailwind config, global CSS, component files). Present findings to user and confirm before writing.

**Generate Mode**: Ask up to 4 questions about feel, color mode, brand colors, and layout density. Use sensible defaults for anything not specified.

### Step 3: WRITE MANIFEST

Write to `.planning/design-manifest.md` using the template defined below. Every section must have real values — no placeholders.

### Step 4: CONFIRM

Present a summary of the manifest to the user: "Here's your design manifest. It will be used by the post-edit hook to flag deviations. Anything to change?"

## Modes

### Extract Mode (existing project has styles)

1. Read `tailwind.config.*` — extract colors, spacing, fonts, breakpoints
2. Read global CSS files — extract CSS variables, base styles
3. Scan 5-10 component files — values used 3+ times become the palette, scale, type scale, shape language, and elevation scale; note component patterns (card, button, input)
4. Present findings: "Here's what I found. Does this look right?"
5. Write manifest after user confirms

### Generate Mode (new project or no existing styles)

Ask up to 4 questions: feel (minimal/playful/corporate/bold), color mode (dark/light/both), brand colors (hex or "pick for me"), layout density. Use sensible defaults for anything not specified.

## The Manifest

Write to `.planning/design-manifest.md`:

```markdown
# Design Manifest

> Generated: {date}
> Mode: {extracted | generated}
> Source: {tailwind.config.ts, globals.css, etc. | user preferences}

## Colors

### Primary Palette
- primary: {hex} — {usage: buttons, links, accents}
- primary-hover: {hex}
- primary-muted: {hex}

### Neutral Palette
- background: {hex}
- surface: {hex} — {cards, modals, elevated elements}
- border: {hex}
- text-primary: {hex}
- text-secondary: {hex}
````
END THIRD-PARTY FILE 9ca2b320761052f9

The third-party file has ended. Everything between the 9ca2b320761052f9 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 3001 of 6441 bytes. © SethGammon · MIT · https://github.com/SethGammon/Citadel/tree/HEAD/skills/design/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
