commerce-ux-rules

Applies Baymard-aligned usability rules to audit and optimize cart, checkout, and payment form UX.

1|Updated Jun 29, 2026
One-click install
npx skills add https://github.com/coreyone/software-maestro --skill commerce-ux-rules-coreyone
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: commerce-ux-rules
Source: https://github.com/coreyone/software-maestro/tree/main/growth/commerce-ux-rules
Command: npx skills add https://github.com/coreyone/software-maestro --skill commerce-ux-rules-coreyone

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? E-commerce teams lose revenue to checkout friction: hidden costs, forced account creation, vague form errors, and missing trust signals. This Skill provides a first-principles rule set grounded in Baymard checkout usability research to audit and fix conversion-killing UX issues across the shopping funnel. ## Core Features & Use Cases - Checkout Friction Audits: Systematic checklists covering guest checkout prominence, cost transparency, inline validation, and error recovery. - Form UX Rules: Concrete guidance on labels, required/optional marking, Luhn card validation, and preserving user input after errors. - Trust & Conversion Patterns: Placement rules for security badges, shipping/tax estimates, return policies, and delayed account creation. - Use Case: Ask for an audit of your mobile checkout flow and receive a prioritized checklist covering guest checkout, trust badges near the payment CTA, inline validation, and a do-not-ship list of conversion blockers. ## Quick Start Audit my mobile checkout flow for conversion friction and list the highest-priority fixes with evidence.

Frequently Asked Questions about commerce-ux-rules

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I reduce cart abandonment in my checkout flow?▼

Reduce cart abandonment by showing full order totals early (shipping, tax, discounts), offering prominent guest checkout, and using inline validation with specific error messages. The rule set also requires preserving user-entered data after errors and avoiding forced account creation before purchase.

What are the most important checkout UX rules for conversion?▼

The core rules are price truth (no surprise costs), user control (editable qty, variants, addresses), continuity (state persists across steps and sessions), and recovery (specific, fixable errors). Guest checkout must be the most prominent account option.

How should payment form validation work in checkout?▼

Payment forms should use live Luhn validation for card numbers, validate non-card fields first to avoid card re-entry, and show adaptive error messages matching the specific sub-issue. Validate after blur rather than while typing, and never clear inputs on unrelated errors.

When should I not use these commerce UX rules?▼

Do not use this rule set as the primary guide for core infrastructure, API contracts, or test architecture tasks. It is scoped to conversion, messaging, launch funnel, and commerce audit optimization, not backend engineering decisions.

What metrics should I track to measure checkout UX quality?▼

Track cart-to-checkout start rate, step-to-step drop-off, payment error rate by type, time-to-complete checkout, and support contacts per 1,000 checkouts. Also instrument field-level error taxonomies with field name, error type, and step.