design-with-claude — Claude Code skill: audit and install
design-with-claude runs a deterministic design-system audit and sends findings to focused slash commands. Use it when an interface needs a structured review before changes.
MIT 206 installs ★ 35 updated 2026-10-21
npx skills add podo/design-agent-skills --skill design-with-claude -a claude-codeWhat design-with-claude does
The skill runs npx dwic-audit across areas such as color, type, spacing, accessibility, forms, navigation, motion, and copy. It combines WCAG contrast calculations, token parsing, and markup heuristics without using an LLM. The command prints a report, writes .dwic/audit-<date>.md, and returns a non-zero status when errors are found, which fits CI checks.
The second part is a set of Markdown slash commands with no runtime dependencies. Findings can be handed to a focused specialist, while /design-with-claude:design-triage reads the audit file and processes issues by rank. Use /design-with-claude:design-brief when a request crosses several design areas.
The audit does not need a token, but its CLI sends an anonymous run counter. Disable that with --no-telemetry or DWIC_TELEMETRY=off. An optional MCP server needs a token from designwithclaude.com; the plugin route requires Claude Code.
What it helps with
- check interface contrast against WCAG
- spot inconsistent tokens and spacing
- review form and navigation issues
- route audit findings to design specialists
- turn a cross-domain request into a design brief
Example prompts for the agent
- Run
npx dwic-auditon this project, then explain the findings and their priority. - Read
.dwic/audit-<date>.mdand work through the issues with/design-with-claude:design-triage. - Create a plan for an interface change that spans several areas with
/design-with-claude:design-brief.
How to install design-with-claude
1Skills CLI (Vercel)
npx skills add podo/design-agent-skills --skill design-with-claude -a claude-code2Manually: put the files in place
~/.claude/skills/design-with-claude/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/design-with-claude/
1Skills CLI (Vercel)
npx skills add podo/design-agent-skills --skill design-with-claude -a codex2Manually: put the files in place
.agents/skills/design-with-claude/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add podo/design-agent-skills --skill design-with-claude -a cursor2Manually: put the files in place
.cursor/skills/design-with-claude/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install podo/design-agent-skills skills/design-with-claude2Manually: put the files in place
.github/skills/design-with-claude/SKILL.md1Skills CLI (Vercel)
npx skills add podo/design-agent-skills --skill design-with-claude -a gemini-cli2Platform CLI
gemini skills install https://github.com/podo/design-agent-skills --path skills/design-with-claudeManually: put the files in place
.devin/skills/design-with-claude/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add podo/design-agent-skills --skill design-with-claude -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about design-with-claude
How do I install design-with-claude in Claude Code?
Run npx skills add podo/design-agent-skills --skill design-with-claude -a claude-code. The installed skill file will be available at ~/.claude/skills/design-with-claude/SKILL.md.
What does design-with-claude do?
It scans a project’s design system, writes an audit report, and connects findings with focused slash commands. The specialists cover areas including color, typography, forms, navigation, mobile interfaces, and more.
Does the skill require a token?
The audit command and slash commands work without a token. A token is needed only for the optional MCP server that adds interactive use and memory across sessions.
Source text
SKILL.md · MIT
---
name: design-with-claude
description: |
Deterministic design-system audit plus a full set of design specialists as slash commands. `npx dwic-audit` scans a project across categories such as color, typography, spacing, accessibility, forms, navigation, motion, and copy using WCAG contrast math and token parsing (no LLM involved), then routes each finding to the specialist that fixes it. Specialists cover visual hierarchy, interaction design, design system architecture, typography, color, spacing, motion, forms, navigation, dashboards, mobile, landing pages, auth UX, healthcare UX, B2B SaaS, e-commerce, dark mode, error handling, onboarding, and data viz. Installs as a Claude Code plugin; the commands are pure markdown with no runtime dependencies.
triggers:
- "design with claude"
- "imsaif design"
- "audit my design system"
- "WCAG contrast audit"
- "b2b SaaS design"
das:
type: package
category: design-review
upstream: "https://github.com/imsaif/design-with-claude"
version: latest
install: false
---
# design-with-claude
> Catalogue stub — full package: [imsaif/design-with-claude](https://github.com/imsaif/design-with-claude) (MIT)
<!-- das:install:start — generated from stub.yaml by `npm run generate`; edit stub.yaml, not this block -->
## Decision tree
1. **Is the full skill already installed?**
- `f=~/.claude/plugins/cache/design-with-claude/design-with-claude; [ -e "$f" ] && ! grep -qs "^das:" "$f" && echo "installed" || echo "pointer"`
- `installed` → invoke it and proceed
- `pointer` → go to step 2
2. **Install** (the skills CLI cannot install this one):
The skills CLI skips this repo because upstream's SKILL.md frontmatter does not parse as YAML, so the supported route is the Claude Code plugin. Run the two plugin commands in a terminal, or send the same two as slash commands inside Claude Code, then run /reload-plugins (without it the commands do not appear).
```bash
claude plugin marketplace add imsaif/design-with-claude
claude plugin install design-with-claude@design-with-claude
```
**Claude Code plugin route:**
```
/plugin marketplace add imsaif/design-with-claude
/plugin install design-with-claude@design-with-claude
```
**Heads-up**
- **Requires:** Claude Code (plugin route). Commands are namespaced, for example /design-with-claude:design-brief; Optional audit CLI `npx dwic-audit` (runs an npm package; it sends an anonymous run counter unless --no-telemetry or DWIC_TELEMETRY=off is set); Optional MCP server for interactive use needs a token from designwithclaude.com
- **License:** MIT
<!-- das:install:end -->
## Invoke after install
- Skill name: `design-with-claude`
- Trigger phrases: "design with claude", "audit my design system", "WCAG contrast audit", "dashboard design", "b2b SaaS design"
- Plugin commands are namespaced, for example `/design-with-claude:design-brief` and `/design-with-claude:accessibility-specialist`. Run `/reload-plugins` after installing or they do not appear.
## What it does
Two halves that work together.
**Measure.** `npx dwic-audit` runs a deterministic static scan across categories such as color, typography, spacing, accessibility, forms, navigation, motion, and copy. WCAG contrast math, token parsing, markup heuristics; no LLM runs. It prints a dashboard, writes a shareable `.dwic/audit-<date>.md`, and exits non-zero on errors so it works in CI. Your code stays on your machine; the CLI only sends an anonymous run counter with category-level counts (disable with `--no-telemetry` or `DWIC_TELEMETRY=off`). It needs no install and no token.
**Fix.** Design specialists as slash commands, each a domain expert in pure markdown with no runtime dependencies. The audit's categories map onto specialists (contrast failures → `/color-specialist`, unlabelled inputs → `/form-designer`, and so on), and `/design-triage` will read the audit report and work the findings in ranked order. `/design-brief` routes a plain-language brief when the problem spans several domains.
Use it when the request is vague ("improve our design", "is this any good?") — measure first, then invoke the specialist the findings point at, rather than guessing. An optional MCP server (set up with `npx dwic-audit setup`, needs a token from designwithclaude.com) adds project memory across sessions; it is not needed for the audit or the commands.
## When NOT to use
- Non-visual work with no design component
- A one-line CSS change you already know how to make
- When a single focused skill already installed suffices — avoid installing the full suite for one-off needs
- Non-Claude agents (Cursor, Cline, Gemini CLI, ...): the skills CLI currently cannot read upstream's SKILL.md (YAML error), so use the `npx dwic-audit` audit on its own or follow the [upstream README](https://github.com/imsaif/design-with-claude#readme)
© podo · MIT · podo/design-agent-skills