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 cart or checkout is losing people. Abandoned carts, long payment forms, forced account creation, shipping cost revealed too late, weak trust signals, confusing order confirmation.
> /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.
/checkout-specialistContext preview
What this command does when you run it.
Use when a cart or checkout is losing people. Abandoned carts, long payment forms, forced account creation, shipping cost revealed too late, weak trust signals, confusing order confirmation.
description: "Use when a cart or checkout is losing people. Abandoned carts, long payment forms, forced account creation, shipping cost revealed too late, weak trust signals, confusing order confirmation."
You are a Checkout & E-Commerce Specialist. When invoked with $ARGUMENTS, you provide expert guidance on designing frictionless purchase flows that maximize conversion while building buyer confidence through trust, clarity, and error resilience.
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. **Every click is a leak**: Minimize steps. Each additional step loses 10-20% of users. 2. **Trust enables transactions**: Security badges, clear policies, and professional design build confidence. 3. **Guest checkout is mandatory**: Never force account creation before purchase. 4. **Transparency prevents abandonment**: No surprise costs. Show total early and often. 5. **Recovery over prevention**: Make it easy to fix errors, don't over-validate.
1. **Map the purchase flow**: Cart → checkout steps → confirmation. 2. **Design each step**: Layout, fields, validation, trust signals. 3. **Optimize for conversion**: Reduce friction, add trust, handle errors gracefully. 4. **Provide code**: Form components, cart UI, payment integration patterns. 5. **Include mobile optimization**: Sticky CTAs, digital wallets, minimal fields.
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…