ecommerce-website-demo

Use when changing shared site layout behavior in the DatoCMS ecommerce website demo starter, even if the user does not say "layout": header, nav/navigation bar, dropdown menus, mobile menu, logo, accent color, notification strip, announcement/top banner, popup, cookie notice, footer, footer columns, social links, newsletter footer, search bar/placeholder, language selector, currency display, cart shell, and Layout or General Interface singleton fields that affect those shared surfaces. Trigger on prompts like "change the popup", "update the footer links", "add a banner at the top", "change the menu", "replace the logo", "hide the newsletter footer", "change the search placeholder", "update the cookie notice", or "change the site accent color". Do not use for homepage section blocks, product listing filters, product detail rendering, product card behavior, new record-backed page routes, draft preview links, SEO route mapping, generic content imports, or page content that does not affect shared site layout.

Use when changing product catalog behavior in the DatoCMS ecommerce website demo starter, including products, brands, materials, collections, product variations, sizes, colors, sale pricing, reviews, related products, the `/[lng]/products` listing page, sidebar filters, search query parameters, product detail rendering, and header category links built from layout menu records. Do not use for homepage section blocks, new record-backed page routes, generic ecommerce strategy, generic DatoCMS imports, or generic CMA scripts unless the task is tied to this starter's catalog files and schema.

Use for route-level page and preview work in the DatoCMS ecommerce website demo starter, especially adding or troubleshooting a new record-backed page route, static params, Next.js metadata, draft preview-links mapping, Web Previews URLs, or SEO analysis route mapping. Trigger on prompts like "add a new lookbook page", "create /[lng]/campaign/[slug]", "map this model in preview-links", or "SEO analysis does not know this page route". Covers the starter's meta.ts, query.graphql, page.tsx, Content.tsx, RealTime.tsx, app/api/draft/preview-links/route.tsx, and app/api/seoAnalysis/route.tsx when the request is about a page route. Do not use for homepage sections, product listing filters, product detail rendering, product sale price or card UI changes, generic DatoCMS frontend setup, or generic Next.js routing outside this starter.

Use for homepage section work in the DatoCMS ecommerce website demo starter, especially requests like "add a new homepage section", "add a featured brands section", "show three featured brands on the homepage", or "add a homepage block". Handles sections rendered through app/[lng]/home/Content.tsx, app/[lng]/home/query.graphql, components/Sections/**/fragment.graphql, and components/Sections/** React components. Also use when the section displays existing catalog data such as brands, materials, collections, or products. Do not use for product listing filters, product detail blocks, new page routes, generic schema modeling, or unrelated frontend components.