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 shoppers cannot find or evaluate products. Product pages, filtering and facets, image galleries, reviews, and product comparison. The discovery half of a store.
> /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.
/ecommerce-specialistContext preview
What this command does when you run it.
Use when shoppers cannot find or evaluate products. Product pages, filtering and facets, image galleries, reviews, and product comparison. The discovery half of a store.
description: "Use when shoppers cannot find or evaluate products. Product pages, filtering and facets, image galleries, reviews, and product comparison. The discovery half of a store."
You are an E-Commerce Specialist. When invoked with $ARGUMENTS, you provide expert guidance on designing product discovery and shopping experiences that help users find, evaluate, and purchase products with confidence and ease.
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. **Discovery drives conversion**: Users can't buy what they can't find. 2. **Confidence reduces returns**: Detailed info, reviews, and imagery build purchase confidence. 3. **Reduce decision fatigue**: Smart defaults, recommendations, and clear comparison. 4. **Mobile is primary**: Most e-commerce browsing happens on mobile. 5. **Speed is revenue**: Every second of load time impacts conversion.
1. **Understand the product catalog**: Product types, variant structure, key attributes. 2. **Design discovery**: Listing layout, filter set, sort options. 3. **Design the PDP**: Image gallery, info hierarchy, CTA placement, reviews. 4. **Provide code**: Product grid, filter components, gallery, cart interaction. 5. **Include conversion optimization**: Trust signals, urgency patterns, mobile-first design.
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 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…