checkout-optimization
/checkout-optimization
Use this skill when the user says 'checkout conversion', 'cart abandonment', 'express checkout', 'apple pay button', 'google pay', 'one-click checkout', 'guest checkout', 'checkout speed', 'checkout form UX'. It reduces checkout friction with express wallets, form autofill, performance and trust patterns, and defines how to measure the funnel. Do NOT use for: cart/order data model (use ecommerce-checkout-cart), payment gateway architecture or PCI (use ecommerce-payment-processing), Stripe subscription webhooks (use stripe-payments).
- Author
- j4flmao ↗
- Repository
- agent-skills ↗
- Licence
- MIT
- Last repository change
- 10.11.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 1
No signals detected. Repository changed on 10.11.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Use this skill when the user says 'checkout conversion', 'cart abandonment', 'express checkout', 'apple pay button', 'google pay', 'one-click checkout', 'guest checkout', 'checkout speed', 'checkout form UX'. It reduces checkout friction with express wallets, form autofill, performance and trust patterns, and defines how to measure the funnel. Do NOT use for: cart/order data model (use ecommerce-checkout-cart), payment gateway architecture or PCI (use ecommerce-payment-processing), Stripe subscription webhooks (use stripe-payments).
Triggers from the description
Original author description
Use this skill when the user says 'checkout conversion', 'cart abandonment', 'express checkout', 'apple pay button', 'google pay', 'one-click checkout', 'guest checkout', 'checkout speed', 'checkout form UX'. It reduces checkout friction with express wallets, form autofill, performance and trust patterns, and defines how to measure the funnel. Do NOT use for: cart/order data model (use ecommerce-checkout-cart), payment gateway architecture or PCI (use ecommerce-payment-processing), Stripe subscription webhooks (use stripe-payments).
How it works
- Purpose
- Agent Protocol
- Friction Sources → Fixes
- Express Checkout (Stripe Express Checkout Element)
- Autofill-Friendly Form
- Performance
- Recovery
- Measurement
- Anti-Patterns
- Checklist
SKILL.md preview
---
name: checkout-optimization
description: >
Use this skill when the user says 'checkout conversion', 'cart abandonment', 'express checkout', 'apple pay button', 'google pay', 'one-click checkout', 'guest checkout', 'checkout speed', 'checkout form UX'. It reduces checkout friction with express wallets, form autofill, performance and trust patterns, and defines how to measure the funnel. Do NOT use for: cart/order data model (use ecommerce-checkout-cart), payment gateway architecture or PCI (use ecommerce-payment-processing), Stripe subscription webhooks (use stripe-payments).
version: "2.0.0"
author: "j4flmao"
license: "MIT"
tags: [ecommerce, checkout, conversion, express-checkout, ux, performance]
---
# Checkout Optimization
## Purpose
Increase checkout completion by removing friction (fields, forced accounts, surprise costs), adding express wallets, and keeping the checkout fast and trustworthy. Every change is measured as a funnel step conversion, not guessed.
## Agent Protocol
### Trigger
"checkout conversion", "cart abandonment", "express checkout", "apple pay", "google pay", "one-click checkout", "guest checkout", "checkout performance", "checkout form".
### Input Context
- Current checkout steps and field count; PSP in use (Stripe, Adyen, Braintree, Shopify).
- Funnel data: cart → checkout start → shipping → payment → order.
- Device split (mobile share drives wallet priority).
### Output Artifact
Prioritized change list with expected funnel step and measurement plan.
### Response Format
```
Biggest drop-off: {step} ({rate})
Changes (ranked): {change} -> {step affected} -> {metric}
Experiment: {A/B design, primary metric, guardrail}
```
## Friction Sources → Fixes
| Friction | Fix |
|----------|-----|
| Unexpected costs at the end (shipping, tax, fees) | Show estimated shipping/tax in cart; free-shipping threshold progress |
| Forced account creation | Guest checkout default; offer account after purchase (password-only field on confirmation) |
| Long forms | Single shipping/billing toggle ("same as shipping"), address autocomplete, drop non-required fields |
| Card entry on mobile | Express wallets above the form (Apple Pay, Google Pay, PayPal, Shop Pay, Link) |
| Distrust | Recognizable payment marks, return policy and total near the pay button, no layout shift |
| Errors only on submit | Inline validation on blur, preserve input on error, specific messages |
| Slow page | Lazy-load third-party scripts except payment SDK; preconnect to PSP origin |
Baymard Institute's aggregate of published studies puts average cart abandonment around 70%; treat your own funnel data as the baseline, not industry averages.
## Express Checkout (Stripe Express Checkout Element)
Prefer the PSP's wallet component over raw Payment Request API: it handles Apple Pay domain verification, wallet eligibility and button rendering.
```javascript
import { loadStripe } from '@stripe/stripe-js';
const stripe = await loadStripe(STRIPE_PUBLISHABLE_KEY);
const elements = stripe.elements({ mode: 'payment', amount: 4999, currency: 'usd' });
const expressCheckout = elements.create('expressCheckout');
expressCheckout.mount('#express-checkout');
expressCheckout.on('confirm', async () => {
const { error: submitError } = await elements.submit();
if (submitError) return showError(submitError.message);
const res = await fetch('/api/checkout/intent', { method: 'POST', headers: { 'Idempotency-Key': cartId } });
if (!res.ok) return showError('Could not start payment, please retry');
const { clientSecret } = await res.json();
const { error } = await stripe.confirmPayment({
elements,
clientSecret,
confirmParams: { return_url: `${location.origin}/order/complete` },
});
if (error) showError(error.message); // otherwise the browser redirects
});
```
Server computes the amount from the cart — never trust an amount sent by the client.
## Autofill-Friendly Form
```html
<form autocomplete="on">
<input name="email" type="email" autocomplete="email" required>
<input name="name" autocomplete="shipping name" required>
<input name="address1" autocomplete="shipping address-line1" required>
<input name="postal" autocomplete="shipping postal-code" inputmode="numeric" required>
<input name="country" autocomplete="shipping country" required>
<input name="tel" type="tel" autocomplete="shipping tel">
</form>
```
Correct `autocomplete` tokens let browsers fill the whole form in one tap; wrong `name`/`id` heuristics are the common cause of failed autofill.
## Performance
- Keep checkout JS small; defer chat widgets, A/B tooling and analytics that are not needed to pay.
- `<link rel="preconnect" href="https://js.stripe.com">` (or your PSP) on cart page.
- Prefetch the checkout route from the cart (`<link rel="prefetch">` or framework router prefetch).
- Reserve space for wallet buttons and PSP iframes to avoid CLS.
- Target fast INP on the pay button: no heavy synchronous work in click handlers.
## Recovery
- Abandoned-cart email/SMS only with consent; first send within hours, include cart deep link that restores state.
- Persist cart server-side keyed by user/session so cross-device return works.
- Exit-intent modals: test carefully — they often hurt mobile UX and brand trust.
## Measurement
| Metric | Definition |
|--------|-----------|
| Checkout start rate | checkout_started / cart_viewed |
| Step conversion | step_n_completed / step_n_viewed |
| Payment success rate | payment_succeeded / payment_attempted (split by method, decline code) |
| Checkout completion | order_placed / checkout_started |
Run A/B tests with order completion as primary metric and AOV/refund rate as guardrails; size samples before launch (see product/ab-testing).
## Anti-Patterns
- Coupon field prominently at top (sends users off-site to hunt codes) — collapse behind a link.
- Re-asking for data already known (logged-in email, address).
- CAPTCHA on checkout for all users — use PSP risk scoring (e.g., Radar) instead.
- Full-page reload on validation errors.
## Checklist
- [ ] Guest checkout available
- [ ] Wallet buttons above the fold on mobile
- [ ] Total including shipping/tax visible before payment step
- [ ] All inputs have correct `autocomplete` tokens and input types
- [ ] Funnel events instrumented per step
- [ ] Idempotent order/payment creation
## References
- `skills/ecommerce/checkout-cart/references/checkout-optimization.md`
- `skills/ecommerce/checkout-cart/references/checkout-ux.md`
- `skills/ecommerce/payment-processing/references/checkout-optimization.md`
Versions
The database has no other skills named checkout-optimization.
Database snapshot: 13.11.2026 · package version ddd46a78d081 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 90ecommerce-checkout
When the user wants to optimize or optimise cart and checkout experience for eCommerce. Also use when the user mentions "cart page," "checkout," "cart abandonment," "guest checkout," "payment," "shipping," "checkout flow," or "conversion funnel. - 95stripe-payments
Use this skill when the user says 'stripe subscription', 'stripe webhook', 'subscription lifecycle', 'stripe billing', 'invoice.paid', 'past_due', 'dunning', 'stripe idempotency key', 'constructEvent'. It designs Stripe Billing subscription flows and production-grade webhook… - 100checkout-friction-finder-ecommerce
Audits e-commerce cart and checkout flows from screenshots, funnel exports, policies, and support notes to find likely friction points. Use when cart abandonment is high, checkout conversion is weak, customers complain about checkout, or the user wants a pre-scale checkout review. - 90ecommerce-checkout-cart
Use when the user asks about shopping cart, checkout flow, cart management, order management, discount/coupon system, tax calculation, shipping logic, or e-commerce backend patterns. Do NOT use for: payment processing (ecommerce-payment-processing), or general backend API design… - 91apple-hig-apple-pay
Use when designing or reviewing Apple Pay checkout, payment-sheet fields, generated buttons, express purchase, recurring payment disclosures, or processing recovery. - 100stripe-integration
Implement Stripe payment processing for robust, PCI-compliant payment flows including checkout, subscriptions, and webhooks. Use when integrating Stripe payments, building subscription systems, or implementing secure checkout flows.