Multi-category storefront
Let shoppers browse, refine a catalog, and keep a usable cart.
Customize the recipe
Prompt preview
# Multi-category storefront Let shoppers browse, refine a catalog, and keep a usable cart. ## Deliverable A multi-category shop with persistent cart behavior and sample products. ## Stack and visual direction - Recommended starting stack: Next.js and TypeScript. Use server-side validation and sandbox integrations for payment or booking when needed. - Minimalism: Use deliberate spacing, a compact palette and a clear typographic hierarchy. Retain the labels, feedback and affordances people need to act. Apply this direction to the website. - Inspect the workspace first. Adapt to its stack when it contains a project, or use the recommended starting stack in a new workspace. ## Tools and setup · Universal Use the receiving agent’s documented skill and tool mechanisms. Match setup to the agent and workspace you actually have. Check available tools first. Propose documented project-level setup only when it materially helps and follow the host's permission prompts. If a tool or integration is unavailable, continue with the workflow below using existing tools, local fixtures or a manual check. Keep secrets in the intended configuration environment. - [Frontend Design](https://github.com/anthropics/skills/tree/main/skills/frontend-design) (Skill) — Plan distinct typography, composition and interaction details before building UI. Fallback: Write a short plan for hierarchy, palette, spacing and interaction states, then review the actual screens against it. - [Next.js](https://github.com/vercel/next.js) (Repository) — Use App Router conventions, server rendering, metadata and accessible route structure. [Official setup](https://nextjs.org/docs/app/getting-started/installation). - [Stripe Payment Samples](https://github.com/stripe-samples/accept-a-payment) (Repository) — Reference sandbox checkout and confirmation flows with provider-hosted payment collection. Use test-mode credentials and test payment fixtures. ## Workflow 1. Build category pages, product details, filters, sorting and a cart over a shared product model. Validate availability and price on the server before creating a sandbox checkout. 2. Use the simplest implementation that delivers the stated outcome. Follow the user's project constraints and treat the starting stack as a default. Reuse existing work and ask for essential input only when it would change the result. Use realistic labeled sample data when real inputs are unavailable. 3. Run the applicable checks and report what actually passed along with any checks you could not run. ## Acceptance checks - [ ] Filter and sort state produce the same results after navigating back from a product. - [ ] Changing an unavailable quantity shows an explanation and a valid alternative. - [ ] Walk the primary journey with keyboard only. Check visible focus, logical order, accessible names, readable contrast, zoom and reduced motion. Use axe where available and manually check behavior that automation cannot assess. - [ ] Check mobile navigation and every key page at narrow and desktop widths. Remove horizontal document overflow and optimize images with stable dimensions and appropriate alternatives. - [ ] Check working buttons, links and footer destinations, clickable logo and contact paths where applicable, page titles, descriptions, favicon, a useful 404 and the current copyright year. Remove placeholder text and unused navigation. - [ ] Verify forms with both valid and invalid submissions and useful success and error feedback.
Recipe resources
Source, setup, and compatibility details.
Frontend Design
Plan distinct typography, composition and interaction details before building UI.
Upstream documents Claude Code.
License · See upstream skill license
Next.js
Use App Router conventions, server rendering, metadata and accessible route structure.
License · MIT
Setup guide for Next.jsStripe Payment Samples
Reference sandbox checkout and confirmation flows with provider-hosted payment collection.
Use test-mode credentials and test payment fixtures.
License · MIT
21st MCP
Find and compare component examples that fit the chosen visual direction.
An MCP-compatible agent and a 21st API key. Check source terms before reusing a component.
Setup guide for 21st MCPPlaywright CLI
Walk real browser interactions and collect screenshots or evidence for regressions.
Node.js and supported browser binaries. Use a local build or authorized test environment.
License · Apache-2.0
Setup guide for Playwright CLIOpenSEO
Run an appropriate site audit, keyword or local visibility workflow when data access is available.
Live data may require OpenSEO access or a configured MCP connection. Some lookups can incur charges.
Upstream documents Codex, Claude Code.
Setup guide for OpenSEO