storefront-next

React Router 7 projects should enforce server components by default and restrict client loaders to maintain efficient data loading and streaming. Client boundaries should be minimized to ensure consistent patterns across the application.

Integrating SCAPI with React 19 frontend components requires using established adapter patterns to connect data loading and configuration. This approach standardizes SCAPI integration across routes, hooks, and providers within the frontend directory.

Storefront Next workflows support Tailwind CSS 4 design tokens and i18n integration using react-i18next. These patterns ensure consistent styling and internationalization across all React components and routes.

Writing Storybook 10 stories and Vitest unit tests for React components involves applying standardized testing workflows to maintain quality. These patterns ensure robust validation for components, hooks, and adapters in the frontend codebase.

This frontend assistant cannot be used for backend cartridge development. It is specifically applicable to frontend directory tasks including components, routes, hooks, providers, and adapters, but does not cover backend systems.

Generating Page Designer metadata and validating forms requires using React Hook Form combined with Zod for robust validation. The assistant documents specific patterns for metadata generation and environment-config system integration.