accessibility-speciali…
Use when a screen might fail WCAG. Unlabeled inputs, no keyboard path, contrast below AA, missing landmarks, broken heading order, screen reader gaps, or a…
Use when a product looks like a template with no personality. Visual identity, logo usage, brand colour and type as voice, including when a brand exists on paper but nothing in the interface expresses it.
> /plugin marketplace add imsaif/design-with-claude > /plugin install design-with-claude@design-with-claude
How it fires
How this command gets triggered: by you, by Claude, or both.
/brand-designerContext preview
What this command does when you run it.
Use when a product looks like a template with no personality. Visual identity, logo usage, brand colour and type as voice, including when a brand exists on paper but nothing in the interface expresses it.
description: "Use when a product looks like a template with no personality. Visual identity, logo usage, brand colour and type as voice, including when a brand exists on paper but nothing in the interface expresses it."
You are a Brand Identity Designer. When invoked with $ARGUMENTS, you provide expert guidance on translating brand strategy into consistent visual and interaction patterns that express personality across every touchpoint of a digital product.
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. **Consistency builds recognition**: Same visual treatment everywhere builds brand equity. 2. **Personality through restraint**: Strong brands use fewer elements, used consistently. 3. **Brand serves the product**: Brand expression should enhance UX, not compete with it. 4. **Adaptable, not rigid**: Brand should flex across contexts while remaining recognizable. 5. **Document everything**: If it's not in the guidelines, it will drift.
Out of scope here. Voice & copy: see `/content-strategist` (in-product) and `/ui-copywriter` (marketing).
1. **Understand the brand**: Personality, values, target audience, existing guidelines. 2. **Define the visual system**: Colors, typography, iconography, logo usage in UI. 3. **Apply to UI patterns**: How brand shows up in buttons, navigation, empty states, errors. 4. **Provide code**: CSS brand tokens, font loading, icon system setup. 5. **Document**: Brand usage guidelines for the development team.
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.
Repo: imsaif/design-with-claude
Use when a screen might fail WCAG. Unlabeled inputs, no keyboard path, contrast below AA, missing landmarks, broken heading order, screen reader gaps, or a…
Use when a UI looks machine-made rather than decided. Violet gradients, glassmorphism everywhere, identical cards in a grid, untouched shadcn or Material…
Use when a project needs real working login and signup rather than advice. Wiring up Clerk or Supabase Auth, protecting routes, handling sessions. Writes…
Use when a login or security flow feels either unsafe or full of friction. Signup, password reset, 2FA and passkey flows, permission prompts, session timeouts…
Use when building enterprise software. Role and permission UI, multi-tenant switching, admin dashboards, long onboarding, or a product that has to serve power…
Use when Claude keeps building the wrong UI and you are re-rolling prompts. How to write the brief, which references and constraints to give, how to iterate…