new-section

To scaffold a new deco.cx section, provide the desired section name and file path to generate a TSX file with TypeScript props, Preact server-side rendering, and Tailwind conventions. This ensures consistent boilerplate across your storefront.

The best way to add client-side behavior to a deco.cx section is by using islands within your server-rendered Preact components. The scaffolding process supports optional islands to handle interactive features without breaking the SSR structure.

You can add loaders for data fetching by including optional loaders during the scaffolding process. This generates the required boilerplate to fetch data server-side and pass it to your Preact section components.

Yes, deco.cx scaffolding enforces server-side rendering with Preact and Tailwind. It generates a compliant section file that uses proper Tailwind utility classes and follows strict SSR conventions to prevent boilerplate drift.

Yes, you can use this scaffolding to maintain consistent boilerplate across your team. It ensures all new storefront sections follow the exact same structure, typed props, and conventions, preventing structural drift during rapid development.

A limitation is that the scaffolding requires a valid root SKILL.md with a name and description to proceed. It also strictly enforces Preact and Tailwind, meaning it is not suitable for teams using alternative frontend frameworks.