design-with-claude

dwic — a product designer inside your terminal

dwic (design with claude) puts a product designer inside Claude Code. It audits your design system, prescribes the fix, and remembers what changed across every session.

The one-line audit

npx dwic-audit

No token, no install, no Claude Code required; your code never leaves your machine. dwic scans your project, prints a dashboard of design-system gaps across 8 categories (color, typography, spacing, accessibility, forms, navigation, motion, copy), and writes a shareable markdown report to .dwic/audit-<date>.md. The check is deterministic (WCAG contrast math, token parsing, markup heuristics), so it's reproducible and CI-friendly via its exit code. Run against a deliberately-broken fixture:

dwic audit pings an anonymous counter on each run so we can see the CLI → MCP funnel. Pass --no-telemetry or set DWIC_TELEMETRY=off to disable; the payload is category-level counts only (no file contents, no paths).

Inside Claude Code

Install the MCP server and the product designer works interactively. Ask the specialists (color-specialist, accessibility-specialist, typography-specialist, and the rest) to audit or fix, and dwic remembers your project's decisions across sessions instead of re-asking every time.

npx dwic-audit setup --token=imr_xxx

Get a token at designwithclaude.com/get-started. For full usage docs, start there.

The free library — dwic's open knowledge base

This repo also ships 49 design skills across 8 categories (39 design specialists and 8 technical guides for designers) as plain Claude Code slash commands. No runtime, no dependencies, no API keys. Browse them at designwithclaude.com/library.

These aren't a separate product. They're the same knowledge base dwic runs on. Each specialist's expertise lives in a markdown role prompt under commands/, and dwic's MCP specialists load those exact files. When you ask dwic's color-specialist inside Claude Code, its expertise comes from the same commands/color-specialist.md that the free /color-specialist slash command loads.

The difference is the runtime around them. dwic wires 12 of these specialists as MCP tools and adds what plain prompts can't: a deterministic audit engine, project memory, and the one-line CLI. The rest of the library is free to drop into Claude Code as slash commands today.

Each command is a specialist file containing structured domain knowledge: WCAG specifics, token architecture patterns, motion timing curves, healthcare UX compliance rules, checkout conversion best practices. The technical guides help designers get unstuck with common walls — environment setup, database connections, auth, deployment, and error debugging. This isn't generic prompting — it's deep, opinionated expertise.

Install the library

With the skills CLI

Works in Claude Code, Cursor, Cline, Gemini CLI, Antigravity and others — no Claude Code required:

npx skills add imsaif/design-with-claude

As a Plugin (recommended)

# Add the marketplace
/plugin marketplace add imsaif/design-with-claude

# Install the plugin
/plugin install design-with-claude@design-with-claude

# Switch it on (without this, the commands don't appear)
/reload-plugins

Commands are namespaced: /design-with-claude:design-brief, /design-with-claude:accessibility-specialist, etc.

As Standalone Commands

If you prefer shorter command names (no namespace prefix):

# Clone the repo
git clone https://github.com/imsaif/design-with-claude.git ~/.design-with-claude

# Copy commands to your user-level commands directory
cp -r ~/.design-with-claude/commands/ ~/.claude/commands/

This gives you /design-brief, /accessibility-specialist, etc. directly.

Quick Start

/design-brief Build a SaaS analytics dashboard with dark mode and accessibility focus

The master command analyzes your brief, identifies the relevant design domains (out of 48), and returns structured guidance — token recommendations, component specs, layout decisions, and implementation notes.

When invoked inside a code project, commands are context-aware: they detect your stack, read your existing files, and generate output that matches your conventions.

Example Output

## Brief Analysis
"SaaS analytics dashboard with dark mode and accessibility focus"
Product type: B2B SaaS dashboard
Key requirements: data visualization, dark theme, WCAG AA compliance

## Relevant Domains (7 of 48)
1. Dashboard Designer — KPI cards, chart layout, data density
2. Dark Mode Specialist — surface hierarchy, elevation tokens, contrast
3. Accessibility Specialist — WCAG AA, focus management, screen readers
4. Data Visualization Specialist — chart selection, color-blind palettes
5. Design System Architect — dark/light token architecture
6. Color Specialist — semantic colors with dark mode variants
7. Typography Specialist — data-dense type scale, monospace for numbers

## Token Recommendations
--surface-primary: hsl(220 20% 10%)     /* main background */
--surface-secondary: hsl(220 18% 14%)   /* card surfaces */
--surface-elevated: hsl(220 16% 18%)    /* modals, dropdowns */
--text-primary: hsl(220 10% 93%)        /* high-emphasis text */
--accent-primary: hsl(210 100% 60%)     /* interactive elements */
--data-series-1: hsl(210 90% 60%)       /* chart color 1 */
...

## Component Recommendations
- KPI cards: icon + metric + trend + sparkline, 4-column grid
- Charts: use accessible palette with pattern fills for color-blind users
- Tables: sticky headers, alternating row contrast ≥ 3:1
- Navigation: sidebar with collapsible sections, active state at ≥ 4.5:1

## Implementation Notes
- Dark mode as default, light mode as toggle (not vice versa)
- All interactive elements need visible focus rings (2px solid, offset 2px)
- Chart tooltips must be keyboard-accessible (not hover-only)
- Minimum touch target: 44x44px for any clickable element

Commands

Start here

For someone who has an idea and nothing else. Everything below this assumes a project already exists; guide is what you run before there is one.

Master Command

Design Process

These act on the design process rather than a domain. Listed in the order you'd normally use them: pin the decisions, check the code obeys them, work the fix list.

Core Design

Visual Design

Interaction Design

Product Design

Content & IA

Industry

Specialized

Technical Setup

Examples

# Get a full design brief for a new product
/design-brief Healthcare patient portal with HIPAA compliance and mobile support

# Deep-dive into a specific domain
/accessibility-specialist Audit this login form for WCAG AA compliance
/design-system-architect Create a token architecture for our React component library
/motion-designer Define transition specs for our modal and dropdown components
/dashboard-designer Design a KPI overview page for a logistics platform

# Combine specialists for thorough coverage
/form-designer Multi-step onboarding form with file uploads
/color-specialist Define a semantic color system for light and dark themes
/checkout-specialist Guest checkout flow for a subscription product

# New design skills
/auth-security-ux-specialist Passkey login flow with 2FA fallback
/drag-drop-specialist Kanban board with drag between columns and keyboard support

# Design process — pin decisions, check compliance, work the fix list
/design-grill Pin down the decisions for our new settings screen before I build it
/design-enforce Check whether src/ actually uses the tokens in styles/tokens.css
/design-triage Work the findings from the latest audit in priority order

# Technical guides — get unstuck
/setup-guide I've never used a terminal before, help me set up Claude Code
/debug-helper Error: Cannot read properties of undefined (reading 'map')
/database-setup I need to store user submissions in a database
/deploy-to-vercel My build is failing with "Module not found"
/auth-implementation Add Google login to my Next.js app
/environment-setup What's a .env file and why do I need one?
/code-explainer What does this middleware.ts file do?

How It Works

Each command file is a markdown document containing a design specialist's complete knowledge. When you invoke a command, Claude loads that specialist as context — giving it deep, structured expertise in that domain.

There's no code running, no API calls, no build step. The commands/ directory IS the product. Claude's intelligence does the rest.

Alternative: Project-Local Commands

Copy commands into a single project:

cp -r ~/.design-with-claude/commands/ your-project/.claude/commands/

Contributing

Adding a new skill

1. Create commands/your-skill-name.md with YAML frontmatter (description field) and a role statement using $ARGUMENTS
2. Follow the structure of existing commands: Expertise, Design Principles, Guidelines, Checklist, Anti-patterns, How to respond, What to ask if unclear
3. Add to the command table in this README and to commands/design-brief.md

License

MIT — designwithclaude.com