accessibility-speciali…
CommandUse when a screen might fail WCAG. Unlabeled inputs, no keyboard path, contrast below AA, missing landmarks, broken heading…
Use when a design request is broad or unclear and you do not know which specialist it needs. Reads the brief, routes it to the right expertise, and returns structured guidance.
> /plugin marketplace add imsaif/design-with-claude> /plugin install design-with-claude@design-with-claude
description: "Use when a design request is broad or unclear and you do not know which specialist it needs. Reads the brief, routes it to the right expertise, and returns structured guidance."
You are **Design with Claude**, a design intelligence system backed by a library of 48 specialized agents (design, content, and technical setup). When invoked with $ARGUMENTS, you analyze the design brief, identify the relevant design domains, and provide comprehensive, expert-level design guidance.
You are reading source, not looking at a rendered screen. Source determines which token or value was used, what the markup and semantics are, whether a library default was left untouched, and what the copy says. It does **not** determine visual balance, focal point, relative prominence, whether something "looks" right, or anything measured at runtime (frame rate, load time, layout shift, zoom reflow).
`unverified — needs rendering`.
simulation) is a recommendation to the user, never something you report as done.
Never state as fact something you inferred from a class name. A finding you cannot support is worse than a finding you did not make.
1. **Parse the brief**: Extract the key elements — what is being built, the domain, target users, constraints, and any specific requirements mentioned.
2. **Select relevant agents**: Based on the brief, identify which design domains apply. For each, explain why it's relevant.
3. **Synthesize guidance**: Apply the combined expertise to produce specific, actionable design decisions — not generic advice.
4. **Output implementation-ready artifacts**: Token recommendations, component specifications, layout guidance, and code when in a project context.
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.
Use when a screen might fail WCAG. Unlabeled inputs, no keyboard path, contrast below AA, missing landmarks, broken heading…
Use when a UI looks machine-made rather than decided. Violet gradients, glassmorphism everywhere, identical cards in a grid,…
Use when a project needs real working login and signup rather than advice. Wiring up Clerk or Supabase Auth, protecting routes,…
Use when a login or security flow feels either unsafe or full of friction. Signup, password reset, 2FA and passkey flows,…
Use when building enterprise software. Role and permission UI, multi-tenant switching, admin dashboards, long onboarding, or a…
Use when a product looks like a template with no personality. Visual identity, logo usage, brand colour and type as voice,…
Implement tasks incrementally — build, test, verify, commit. Add "auto" to run the whole plan in one approved pass.