checkout-architecture

Document reusable checkout UI components for sign-in, address, and payment steps.

1.5k|875|Updated Aug 20, 2021
One-click install
npx skills add https://github.com/saleor/storefront --skill checkout-architecture
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: checkout-architecture
Source: https://github.com/saleor/storefront/tree/main/.claude/skills/checkout-architecture
Command: npx skills add https://github.com/saleor/storefront --skill checkout-architecture

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reference for reusable checkout UI components. Use when working with SignInForm, AddressSelector, PaymentMethodSelector, or composing checkout step views.

Core Features & Use Cases

  • Component locations and examples for contact, shipping-address, payment, and AddressForm components to promote consistency across steps.
  • Guidance on how to import and compose components to build a cohesive checkout flow.
  • Usage patterns and design considerations to accelerate frontend development and enable reuse across pages and channels.

Quick Start

Import the reusable checkout components from src/checkout/components and compose steps as shown in the usage pattern.

Frequently Asked Questions about checkout-architecture

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

FAQPage Schema
How do I build a React checkout flow with reusable UI components?

Build a React checkout flow by importing reusable UI components from src/checkout/components and composing them into step views. This approach covers contact, shipping address, and payment steps to ensure consistent UX across channels.

What are the best practices for organizing frontend architecture in a checkout UI?

Organizing frontend architecture for a checkout UI involves structuring components by step, applying usage patterns, and extracting new components only when reuse is needed. This maintains a cohesive flow across sign-in, address, and payment views.

When should I extract a new component from my React checkout steps?

Extract a new checkout component when a specific UI pattern, such as an address selector or payment method selector, is repeated across steps. This promotes frontend architecture consistency and accelerates development across pages.

Can I use the same checkout UI components across different pages and channels?

Yes, checkout UI components are designed for reuse across different pages and channels. Importing and composing them according to documented usage patterns ensures a cohesive checkout flow and consistent UX.

Does this reference include examples for composing sign-in and payment steps in TypeScript?

Yes, the reference includes component locations and examples for composing sign-in and payment steps in TypeScript. It covers importing and composing components like SignInForm and PaymentMethodSelector to accelerate frontend development.

How do I ensure consistent UX across multiple checkout steps in a React application?

Ensure consistent UX across checkout steps by applying reusable UI components and documented usage patterns. This reference provides design considerations and organization guidance to maintain consistency across contact, address, and payment flows.