Skip to content
cccskills
FreePublished on GitHub

cart-checkout

Design and audit cart and checkout flows — cart state, multi-step vs one-page checkout, guest checkout, address/shipping/tax/payment steps, and abandoned-cart recovery. Platform-agnostic conversion and correctness patterns. Triggers: designing a checkout, auditing drop-off, planning abandoned-cart flows.

The English summary is being prepared. Showing the original description.

SebastianLuser/claude-code-arcane3 stars(GitHub 3 + cccskills 0)

Run score Not tested

See how to install

Files included (2)

  • SKILL.md3.7 KB
  • references/checkout-flow-spec.md2.4 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Cart & Checkout

The highest-leverage surface in commerce: where intent becomes revenue. Design carts and checkouts that are correct under concurrency and optimized for completion — without prescribing a framework.

Before Starting

Gather: cart model (server-persisted vs client, guest vs account), checkout type (single vs multi-step), payment/shipping/tax requirements, and goal (design new flow, audit drop-off, or build abandoned-cart recovery).

How This Skill Works

ModeTriggerOutput
DesigndesignCart state model + checkout step flow + edge cases
AuditauditFriction/drop-off analysis with prioritized fixes
AbandonedabandonedRecovery sequence (triggers, timing, channels)

Phase 1 — Cart State

DecisionRecommendation
PersistenceServer-side cart keyed by session + user; merge on login
PricingRe-price at checkout — never trust cart-stored prices
InventorySoft-reserve at checkout start, not on add-to-cart
IdentityAllow guest carts; merge guest → account without losing items

Rule: The cart is a draft, not a contract. Totals, stock, and promotions are recomputed server-side before payment.


Phase 2 — Checkout Flow

Canonical steps: Cart → Identity → Shipping address → Shipping method → Payment → Review → Confirmation.

  • Guest checkout is non-negotiable for B2C — forced account creation is the #1 avoidable drop-off.
  • Collect email first (enables abandoned-cart + receipts).
  • One-page vs multi-step: multi-step for complex shipping/tax; one-page for low-SKU/digital. Either way, show progress and never lose entered data on validation error.
  • Recompute tax/shipping when the address changes; show the final total before the pay button.
  • Make payment idempotent — a double-click must not double-charge (hand off to payments-architecture).

For the full step-by-step field list, error handling, and address validation patterns, see references/checkout-flow-spec.md.


Phase 3 — Abandoned-Cart Recovery

TouchTimingAngle
1~1hReminder ("you left these")
2~24hHelp/objection handling + reviews
3~72hIncentive (discount) — only if margin allows

Capture email as early as possible; suppress recovery once the order completes; respect consent and frequency caps.


Output Artifacts

RequestOutput
Design flowCart model + annotated step diagram + edge-case list
AuditDrop-off table with severity and READY-to-ship fixes
AbandonedTrigger/timing/channel sequence + suppression rules

A checkout is READY when guest checkout works, prices/stock are re-validated server-side, payment is idempotent, and data survives validation errors.


Related Skills

  • payments-architecture: owns the payment step (intents, idempotency, webhooks).
  • shipping-tax: computes the shipping and tax shown at checkout.
  • promotions-discounts: applies coupons/discounts at the cart.
  • page-cro / form-cro: deeper conversion optimization of the checkout UI.
  • order-lifecycle: takes over once the order is placed.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Plan, design, and implement A/B tests and experiments with statistical rigor. Covers hypothesis frameworks, sample sizing, metrics, and result analysis.

The English summary is being prepared. Showing the original description.

SebastianLuser/claude-code-arcane3Updated Oct 27, 2026

Web/mobile accessibility decision guide: WCAG 2.2 AA, ARIA, keyboard nav, focus management, contrast, testing. Use for: a11y, accessibility, wcag, aria, screen reader, keyboard, contrast.

The English summary is being prepared. Showing the original description.

SebastianLuser/claude-code-arcane3Updated Oct 27, 2026

Generate, iterate, and scale ad creative for paid advertising across Google, Meta, LinkedIn, and X. Covers platform specs, creative frameworks, and quality validation.

The English summary is being prepared. Showing the original description.

SebastianLuser/claude-code-arcane3Updated Oct 27, 2026

Musica interactiva para juegos: layering vertical, re-secuenciacion horizontal, stingers, reglas de transicion con sync points, y mapeo de estados de gameplay a musica. Usar para: musica adaptativa, sistema de musica dinamica, transiciones musicales, combat music.

The English summary is being prepared. Showing the original description.

SebastianLuser/claude-code-arcane3Updated Oct 27, 2026

Design multi-agent systems, create agent architectures, define communication patterns, and build autonomous agent workflows with structured evaluation frameworks.

The English summary is being prepared. Showing the original description.

SebastianLuser/claude-code-arcane3Updated Oct 27, 2026

Inter-agent communication protocol for C-suite agent teams. Defines invocation syntax, loop prevention, isolation rules, response formats, and quality loops.

The English summary is being prepared. Showing the original description.

SebastianLuser/claude-code-arcane3Updated Oct 27, 2026

See all skills by SebastianLuser

Report a problem with this skill