Skip to main content
skill CX Codex

design · sethgammon — Claude Code skill: manifest and setup

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

MIT ★ 937 updated 2026-10-29

Install into Claude Code · Plugin marketplace All methods and platforms ↓
/plugin marketplace add SethGammon/Citadel
/plugin install citadel@citadel-local
Open on GitHub

What design 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.

What it helps with

  • 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 for the agent

  • 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.

How to install design

1Plugin marketplace

/plugin marketplace add SethGammon/Citadel
/plugin install citadel@citadel-local

This installs the whole citadel plugin with all its skills

2Skills CLI (Vercel)

npx skills add SethGammon/Citadel --skill design -a claude-code

3Manually: put the files in place

~/.claude/skills/design/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/design/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about design

How do I install design in Claude Code?

Add the marketplace with /plugin marketplace add SethGammon/Citadel, then install the skill with /plugin install citadel@citadel-local.

What does the design skill do?

It creates .planning/design-manifest.md from existing styles or preferences for a new project. A post-edit hook checks changed files against the manifest and reports deviations.

Does the hook block edits when it finds a mismatch?

No. It emits warnings, one per category per edit, and scans only the file that changed.

Source text

SKILL.md · MIT
---
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}
- text-muted: {hex}

### Semantic
- success: {hex}
- warning: {hex}
- error: {hex}
- info: {hex}

## Typography

- font-family: {value}
- heading-font: {value, or "same as body"}
- Type scale: {xs, sm, base, lg, xl, 2xl, 3xl — with px/rem values}
- Line heights: {tight, normal, relaxed — with values}
- Font weights used: {list}

## Spacing

- Base unit: {4px / 0.25rem}
- Scale: {1, 2, 3, 4, 6, 8, 12, 16, 24 — in base units}
- Component padding: {standard value}
- Section gap: {standard value}
- Page margin: {standard value}

## Shape

- Border radius: {none, sm, md, lg, full — with values}
- Default radius: {which one is used most}
- Shadow scale: {sm, md, lg — with values}

## Layout

- Max content width: {value}
- Breakpoints: {sm, md, lg, xl — with values}
- Grid/flex preference: {which is used more}
- Spacing rhythm: {consistent gaps between sections}

## Component Patterns

{Only populated in extract mode or after the project has components}
- Button: {padding, radius, font-weight, transition}
- Card: {padding, radius, shadow, border}
- Input: {padding, radius, border-color, focus-ring}

## Anti-Patterns (things to flag)

- Colors not in the palette above
- Font sizes not in the type scale
- Spacing values not in the spacing scale
- Border radius values not matching the shape section
- Hardcoded colors instead of CSS variables or Tailwind classes
```

## Hook Integration

post-edit.js checks for `.planning/design-manifest.md`. When a CSS/TSX/JSX/Tailwind file is edited, it scans for: hardcoded hex colors not in the palette, font sizes outside the type scale, spacing values outside the scale, and border radius values not in the shape section. Warnings only — not blocks. One warning per category per edit.

Hook rules: skip entirely if no manifest; scan only the edited file; cache the manifest once per session; do not flag Tailwind utility classes that map to config; only flag raw hex/px values.

## Contextual Gates

**Disclosure:** "Updating design manifest. Existing manifest will be modified."
**Reversibility:** amber — modifies `.planning/design-manifest.md`; undo with `git checkout .planning/design-manifest.md`.
**Trust gates:**
- Any: generate or update design manifest.
- Familiar (5+ sessions): full manifest rewrites that discard existing content.

## Quality Gates

- Every manifest section has real values (not placeholders)
- Extract mode cites which files the values came from
- Generate mode defaults are sensible (not random)
- Anti-patterns section is populated based on the manifest values

## Fringe Cases

**No styles and no preferences:** Default to Generate Mode; use sensible defaults (minimal, light mode, neutral palette); present before writing.

**Tailwind config but no custom theme:** Extract available values (font, breakpoints); note which sections use Tailwind defaults; generate the rest.

**`.planning/` missing:** Create it; if not possible, output manifest inline and instruct user to save it.

**"Update the manifest":** Re-run Extract Mode, diff against existing manifest, present only what changed.

## Exit Protocol

```
---HANDOFF---
- Design manifest: .planning/design-manifest.md
- Mode: {extracted | generated}
- Sources: {files read, or "user preferences"}
- Anti-patterns documented: {count}
- Next: Post-edit hook will flag deviations automatically
- Reversibility: amber — undo with `git checkout .planning/design-manifest.md`
---
```

© SethGammon · MIT · SethGammon/Citadel

Similar skills

All skills for Design →

design by other authors comes first.

design claudekit This Claude Code skill handles brand identity, interface styling, logos, banners, presentations, and social graphics. Ask for a design system, corporate identity mockups, or assets for a social platform. CX Codex +1 52,700installs design SubframeApp design — a skill that walks the agent through creating and editing pages, components, snippets, and themes in Subframe. It kicks in when the deliverable belongs in Subframe rather than a code branch. CX Codex +1 798installs design rshankras Design skills for Apple platform UI: Liquid Glass, animations, game feel, UX writing, SF Symbols and typography. Useful when a screen feels flat and you need a plan. CX Codex +1 738installs design cognitedata Provides Aura design system rules for Flows and Fusion applications. It guides agents to choose primitives, rely on semantic tokens, and maintain consistent UI states. CX Codex +1 1,900installs design kirkchen Creates a Beat change container and prepares specification artifacts such as a proposal, Gherkin scenarios, and design.md. It runs at the start of a change. CX Codex +1 523installs craft-design-engineering gustavo-fior craft-design-engineering — a skill that hands your agent design engineering rules: type, colour, spacing, motion and numbers. Useful when a UI needs to look finished. CX Codex +1 744installs frontend-design jdrhyne frontend-design — a skill that sets the order of UI work: wireframe, theme, animation, then code. Useful for landing pages, dashboards and single components. CX Codex +1 ★ 239repo stars color-palette-extractor OneWave-AI color-palette-extractor pulls dominant colors out of an image, screenshot or website and turns them into a palette with contrast checks. Handy when you need a theme built from a logo or someone else's mockup. CX Codex +1 660installs tailwind-ui-refactor pproenca tailwind-ui-refactor — a skill that refactors HTML with Tailwind utility classes: hierarchy, spacing, typography, color. Useful when you build UI without a designer on hand. CX Codex +1 474installs design-system claudekit The design-system skill builds design tokens, component specs, and presentation slides. Use it when an interface and its slides need to follow one visual system. CX Codex +1 54,500installs absolute-ui dhruvjainin absolute-ui — a Claude Code skill that applies concrete CSS and Tailwind values to interface design. It activates for requests about components, spacing, typography, dark mode, and responsive layouts. CX Codex +1 382installs

From the same set55

The whole set →
archon archon — a subagent that carries a big task through phases: splits a direction into steps, hands them to other agents and keeps campaign state between runs. CX Codex ★ 937repo stars loop loop — a skill for Claude Code and Codex that runs an action repeatedly and checks the result each time, stopping when verification passes or attempts run out. Useful for fixing lint errors or test failures in an active session. CX Codex +1 ★ 937repo stars marshal The marshal skill for Claude Code parses a task, gathers context from code and project memory, and chains skills. It runs in one session and asks only if it cannot continue. CX Codex +1 ★ 937repo stars test-gen test-gen is a Claude Code skill that generates and runs unit tests matching a project's existing framework, covering happy paths, edge cases, and failures. CX Codex +1 ★ 937repo stars live-preview live-preview takes screenshots of components during construction, not after completion. Catches layout regressions and invisible blocks before they propagate. CX Codex +1 ★ 937repo stars architect architect turns a PRD or task outline into an implementation plan with file trees, data models, and phased build steps. CX Codex +1 ★ 937repo stars cost See token usage and costs for sessions, campaigns, and time periods. Use it to check where spend is going and how quickly it is rising. CX Codex +1 ★ 937repo stars merge-review merge-review scans the fleet worktree merge queue, flags files touched by more than one branch, and suggests a merge order before anything lands in main. CX Codex +1 ★ 937repo stars

Project sponsors

Companies that keep this analytics open