create-content-sdk-app 2.0.0-canary.9 → 2.0.0

package/dist/templates/nextjs-app-router/.agents/skills/content-sdk-multisite-management/SKILL.md

@@ -1,37 +0,0 @@
----
-name: content-sdk-multisite-management
-description: Handles multisite: site resolution, .sitecore/sites.json, and proxy in src/proxy.ts. App Router proxy order is fixed: LocaleProxy → AppRouterMultisiteProxy → RedirectsProxy → PersonalizeProxy. Use when working with multiple sites or hostnames.
----
-
-# Content SDK Multisite Management (App Router)
-
-Site resolution from request (e.g. hostname or cookie); proxy rewrites to /[site]/[locale]/...path. **Locale must run first** so next-intl and multisite see the correct locale.
-
-## When to Use
-
-- User asks about multiple sites, hostnames, or site resolution.
-- Task involves .sitecore/sites.json, multisite config, or proxy/middleware for site.
-- User mentions "multisite," "site resolution," "hostname," or "sites.json."
-
-## How to perform
-
-- Site list: `.sitecore/sites.json`. Proxy logic lives in `src/proxy.ts`; ensure `src/middleware.ts` re-exports it if present. Keep chain order: LocaleProxy → AppRouterMultisiteProxy → RedirectsProxy → PersonalizeProxy. Exclude API, _next, static assets in the matcher.
-
-## Hard Rules
-
-- Site list is in `.sitecore/sites.json` (typically generated by Sitecore CLI or deployment). Avoid hand-editing unless the format is known.
-- **Proxy:** Implemented in `src/proxy.ts`. Next.js runs middleware from `middleware.ts` at root or in `src/` — if the app only has `proxy.ts`, add `src/middleware.ts` that re-exports it.
-- **Chain order is fixed:** LocaleProxy → AppRouterMultisiteProxy → RedirectsProxy → PersonalizeProxy. **Do not change this order.** LocaleProxy runs first so i18n and multisite see the correct locale. AppRouterMultisiteProxy rewrites to /[site]/[locale]/[...path].
-- **Matcher:** Exclude API routes, _next/, sitemap, robots, healthz, Sitecore paths, and static assets so the proxy stays lightweight.
-- Config: sitecore.config.ts → multisite, redirects, personalize. Single SitecoreClient; pass resolved site and locale from route params into getPage, getDictionary, etc.
-
-## Stop Conditions
-
-- Stop if the user wants to reorder the proxy chain; explain that LocaleProxy must run first for App Router.
-- Stop if sites.json format is unknown and the change could break resolution; suggest checking SDK docs or CLI output.
-- Do not add a second site resolution mechanism; use the existing proxy and config.
-
-## References
-
-- [AGENTS.md](../../../AGENTS.md) for proxy chain, matcher, and multisite config.
-- [Official Content SDK docs](https://doc.sitecore.com/xmc/en/developers/content-sdk/sitecore-content-sdk-for-xm-cloud.html).

package/dist/templates/nextjs-app-router/.agents/skills/content-sdk-route-configuration/SKILL.md

@@ -1,38 +0,0 @@
----
-name: content-sdk-route-configuration
-description: Configures routing and layout for App Router. Single catch-all at src/app/[site]/[locale]/[[...path]]/page.tsx; call setRequestLocale at top of page. Use when changing routing, placeholders, or Layout.
----
-
-# Content SDK Route Configuration (App Router)
-
-Single catch-all route and layout hierarchy. Site and locale are **in the path**; proxy rewrites incoming requests to /[site]/[locale]/...path.
-
-## When to Use
-
-- User asks to change routing, add a route, or fix 404/not-found behavior.
-- Task involves catch-all route, placeholders, root layout, or Layout.tsx.
-- User mentions "[site]," "[locale]," "[[...path]]," "placeholder," or "layout hierarchy."
-
-## How to perform
-
-- Single Sitecore page: `src/app/[site]/[locale]/[[...path]]/page.tsx`. Use `await params` for `{ site, locale, path? }`; pass to getPage and call `setRequestLocale(\`${site}_${locale}\`)` at the top. Layout: app/layout.tsx → app/[site]/layout.tsx (Bootstrap, draftMode) → page. Not-found: use parseRewriteHeader and getErrorPage in the route's not-found.tsx.
-
-## Hard Rules
-
-- **Single Sitecore page:** `src/app/[site]/[locale]/[[...path]]/page.tsx`. This is the **only** page that renders Sitecore content. Do not add another page or catch-all for Sitecore content.
-- **Params:** Next.js 15+ — `params` is a Promise. Use `await params` to get `{ site, locale, path? }`. Pass `site` and `locale` to `client.getPage(path ?? [], { site, locale })`.
-- **Locale for next-intl:** Call `setRequestLocale(\`${site}_${locale}\`)` at the **top** of the page so next-intl and `src/i18n/request.ts` see the correct locale. Do not omit when adding new page branches.
-- **Layout hierarchy:** `app/layout.tsx` → `app/[site]/layout.tsx` (Bootstrap with `siteName={site}` and `draftMode()`) → page. Do not put site/locale-specific data fetching in the root layout.
-- Placeholders are rendered by the layout (e.g. Placeholder component); do not change placeholder names or structure without aligning with Sitecore layout definition.
-- **Not-found:** `src/app/[site]/[locale]/[[...path]]/not-found.tsx`. For Sitecore-driven 404 use `parseRewriteHeader(headers())` for site/locale, then `client.getErrorPage(ErrorPage.NotFound, { site, locale })`. Wrap in Suspense if using async logic.
-
-## Stop Conditions
-
-- Stop if the user wants to add a second catch-all or a different URL shape for Sitecore pages; explain single-entry-point constraint.
-- Stop if changing proxy/middleware order; order is fixed (LocaleProxy → AppRouterMultisiteProxy → RedirectsProxy → PersonalizeProxy).
-- Do not move or rename the catch-all file without updating all references.
-
-## References
-
-- [AGENTS.md](../../../AGENTS.md) for exact paths, params, and layout hierarchy.
-- [Official Content SDK docs](https://doc.sitecore.com/xmc/en/developers/content-sdk/sitecore-content-sdk-for-xm-cloud.html).

package/dist/templates/nextjs-app-router/.agents/skills/content-sdk-site-setup-and-env/SKILL.md

@@ -1,36 +0,0 @@
----
-name: content-sdk-site-setup-and-env
-description: Configures site and environment: sitecore.config.ts, environment variables, default site and language. Use when configuring the app or adding env vars. Document in .env.example only; never commit .env or .env.local.
----
-
-# Content SDK Site Setup and Environment (App Router)
-
-Central config in sitecore.config.ts; all secrets and environment-specific values via env vars.
-
-## When to Use
-
-- User asks to configure site, default language, API host, or environment.
-- Task involves sitecore.config.ts, .env, or defaultSite/defaultLanguage.
-- User mentions "config," "environment variables," "API key," or "default site."
-
-## How to perform
-
-- Edit `sitecore.config.ts` with `defineConfig`; read all secrets and env-specific values from `process.env.*`. Add or change vars in `.env.example` (or `.env.remote.example` / `.env.container.example`) with placeholders; never commit `.env` or `.env.local`.
-
-## Hard Rules
-
-- Use `sitecore.config.ts` with `defineConfig` from the SDK. Expose api (edge, local), defaultSite, defaultLanguage, editingSecret, multisite, redirects, personalize as needed.
-- All sensitive or environment-specific values must come from environment variables (e.g. process.env.SITECORE_API_KEY). Never hardcode API keys, secrets, or production URLs in source.
-- Document every new or changed env var in `.env.example` (or `.env.remote.example` / `.env.container.example`). Use placeholder or empty value and a short comment; never put real secrets in example files.
-- Never commit `.env` or `.env.local`; they are gitignored. Example files are the source of truth for which vars exist.
-
-## Stop Conditions
-
-- Stop if the user wants to commit real secrets or production values; insist on env vars and .env.example only.
-- Stop if adding a new env var would require CI or deployment changes without explicit instruction; document the var and note that deployment must set it.
-- Do not edit .next/, node_modules/, or lockfiles unless the task explicitly requires it.
-
-## References
-
-- [AGENTS.md](../../../AGENTS.md) for boundaries and env rules.
-- [Official Content SDK docs](https://doc.sitecore.com/xmc/en/developers/content-sdk/sitecore-content-sdk-for-xm-cloud.html).

package/dist/templates/nextjs-app-router/.agents/skills/content-sdk-sitemap-robots/SKILL.md

@@ -1,37 +0,0 @@
----
-name: content-sdk-sitemap-robots
-description: Sitemap and robots.txt for App Router: src/app/api/sitemap/route.ts and src/app/api/robots/route.ts with createSitemapRouteHandler and createRobotsRouteHandler. Rewrites in next.config.ts. Use when configuring sitemap, robots.txt, or SEO.
----
-
-# Content SDK Sitemap and Robots (App Router)
-
-Sitemap and robots.txt are served via **route handlers** and rewrites. Use the SDK route handler helpers and sites from .sitecore/sites.json.
-
-## When to Use
-
-- User asks to add or change sitemap or robots.txt.
-- Task involves SEO, sitemap.xml, or robots route.
-- User mentions "sitemap," "robots," "SEO," or "rewrites."
-
-## How to perform
-
-- Sitemap: `src/app/api/sitemap/route.ts` with `createSitemapRouteHandler({ client, sites })`; robots: `src/app/api/robots/route.ts` with `createRobotsRouteHandler({ client, sites })`. Use sites from `.sitecore/sites.json`. Add rewrites in `next.config.ts` for `/sitemap*.xml` and `/robots.txt` with `locale: false`. Set `dynamic = 'force-dynamic'` if needed.
-
-## Hard Rules
-
-- **Sitemap:** `src/app/api/sitemap/route.ts` — use `createSitemapRouteHandler({ client, sites })`. Export `{ GET }`. Use `sites` from `.sitecore/sites.json`. Set `export const dynamic = 'force-dynamic'` if the handler relies on request.
-- **Robots:** `src/app/api/robots/route.ts` — use `createRobotsRouteHandler({ client, sites })`. Same pattern.
-- **Rewrites:** In `next.config.ts`, add rewrites for `/sitemap*.xml` and `/robots.txt` to these route handlers. Use `locale: false` so they are not localized.
-- Use the same SitecoreClient instance as the rest of the app; do not create a dedicated client for sitemap/robots.
-- Avoid hardcoding the site list; use .sitecore/sites.json.
-
-## Stop Conditions
-
-- Stop if the user wants to serve sitemap/robots from a different origin or with different auth; document and suggest proxy or edge config.
-- Do not add new env vars for sitemap/robots without documenting them in .env.example.
-- Do not change rewrite paths without updating docs and any references.
-
-## References
-
-- [AGENTS.md](../../../AGENTS.md) for API routes and rewrites.
-- [Official Content SDK docs](https://doc.sitecore.com/xmc/en/developers/content-sdk/sitecore-content-sdk-for-xm-cloud.html).

package/dist/templates/nextjs-app-router/.agents/skills/content-sdk-troubleshoot-editing/SKILL.md

@@ -1,39 +0,0 @@
----
-name: content-sdk-troubleshoot-editing
-description: Troubleshoots XM Cloud editing, preview, and design library for App Router. Check draftMode(), getPreview/getDesignLibraryData from searchParams, setRequestLocale, and component maps. Use when editing or preview does not behave as expected.
----
-
-# Content SDK Troubleshoot Editing (App Router)
-
-This skill focuses on **diagnosing** editing, preview, and design library issues. For implementing editing-safe rendering (draftMode, getPreview/getDesignLibraryData, API routes), use the **content-sdk-editing-safe-rendering** skill; the two are complementary (implementation vs. troubleshooting).
-
-Diagnose and fix editing, preview, and design library issues without breaking the single client or proxy order. This app uses **draftMode()** and **searchParams** for preview data.
-
-## When to Use
-
-- User reports that editing, preview, or design library is broken or inconsistent.
-- Task involves debugging "not working in editor," missing chromes, or wrong data in preview.
-- User mentions "editing broken," "preview not working," "design library," or "editor issues."
-
-## How to perform
-
-- Confirm `draftMode()` and searchParams-based getPreview/getDesignLibraryData; ensure `setRequestLocale` is called at the top of the page. Verify editing API routes are not rewritten (check proxy matcher) and both component maps include the component. Check env (editingSecret, API config) and .env.example documentation.
-
-## Hard Rules
-
-- **Preview flow:** Use `draftMode()` in Server Components; when enabled, use `client.getPreview(editingParams)` or `client.getDesignLibraryData(editingParams)` from **searchParams**. Ensure site/locale are passed correctly (e.g. from route params or editingParams).
-- **next-intl:** Ensure `setRequestLocale(\`${site}_${locale}\`)` is called at the top of the page; missing setRequestLocale can cause locale or dictionary issues in editor.
-- Editing API routes (`src/app/api/editing/config/route.ts`, `editing/render/route.ts`) must be reachable and use the same component maps (component-map.ts and component-map.client.ts) and config as the app. Check matcher in proxy.ts so /api/editing is not rewritten or blocked.
-- Check that both component maps include all components used in the layout; missing registration causes "component not found" in editor.
-- Environment: editingSecret and API config must be set (in env); document in .env.example only. Do not log or commit secrets.
-
-## Stop Conditions
-
-- Stop if the fix would require changing CI, deployment, or XM Cloud project settings; suggest the user do that and document the required env or config.
-- Stop if the issue might be in Sitecore (layout, template) rather than the app; suggest checking layout and content in XM Cloud.
-- Do not recommend disabling security (e.g. skipping secret validation) without explicit user request and warning.
-
-## References
-
-- content-sdk-editing-safe-rendering skill and [AGENTS.md](../../../AGENTS.md) for preview and editing flow.
-- [Official Content SDK docs](https://doc.sitecore.com/xmc/en/developers/content-sdk/sitecore-content-sdk-for-xm-cloud.html).

package/dist/templates/nextjs-app-router/.agents/skills/content-sdk-upgrade-assistant/SKILL.md

@@ -1,36 +0,0 @@
----
-name: content-sdk-upgrade-assistant
-description: Guides upgrading @sitecore-content-sdk/* packages: version bumps, breaking changes, migration steps. Use when moving to a newer SDK or package version. Check Content SDK repo CHANGELOG and upgrade guides.
----
-
-# Content SDK Upgrade Assistant (App Router)
-
-Upgrade @sitecore-content-sdk/* packages safely; follow the Content SDK repo changelog and migration guides.
-
-## When to Use
-
-- User asks to upgrade SDK packages, update to a new version, or apply a migration.
-- Task involves version bumps, @sitecore-content-sdk/* dependencies, or breaking changes.
-- User mentions "upgrade," "migration," "new version," or "breaking change."
-
-## How to perform
-
-- Bump all @sitecore-content-sdk/* to consistent versions; read the Content SDK repo CHANGELOG (and MIGRATION/upgrade docs) for breaking changes and migration steps. Update package.json, run `npm install` and `npm run build`; test editing and preview after upgrade.
-
-## Hard Rules
-
-- Prefer upgrading all @sitecore-content-sdk/* packages together to a consistent set of versions unless the user requests a partial upgrade. Check peer dependencies and compatibility.
-- Update dependencies in package.json; run `npm install` and `npm run build`. Test editing and preview after upgrade.
-- Read the **Content SDK repository** CHANGELOG (and any MIGRATION.md or upgrade guide) for breaking changes and required code/config updates. Apply migration steps before or with the version bump.
-- Do not edit .next/, node_modules/, or lockfiles unless required for the upgrade. Do not change CI or root tooling unless the task explicitly includes it.
-
-## Stop Conditions
-
-- Stop if the target version is not specified or unclear; ask or suggest checking the Content SDK CHANGELOG and supported versions.
-- Stop if a breaking change requires product or deployment decisions (e.g. new env vars, config schema); list required changes and ask the user to confirm.
-
-## References
-
-- Content SDK repo [CHANGELOG](https://github.com/Sitecore/content-sdk/blob/dev/CHANGELOG.md) and upgrade docs.
-- [AGENTS.md](../../../AGENTS.md) for build commands.
-- [Official Content SDK docs](https://doc.sitecore.com/xmc/en/developers/content-sdk/sitecore-content-sdk-for-xm-cloud.html).

package/dist/templates/nextjs-app-router/Skills.md

@@ -1,79 +0,0 @@
-# Skills.md — Capability groupings for this app (Next.js App Router)
-
-This file describes **this application** in terms of **capability-style groupings**: high-level areas that help AI tools and developers map tasks to the right part of the app. This is an App Router app with `[site]`/`[locale]` segments, next-intl, and separate server/client component maps. For concrete steps and patterns, see [AGENTS.md](AGENTS.md) and the [official Content SDK documentation](https://doc.sitecore.com/xmc/en/developers/content-sdk/sitecore-content-sdk-for-xm-cloud.html).
-
-**Agent Skills:** Each grouping is also available as a skill in [.agents/skills/](.agents/skills/) in the standard [Agent Skills](https://agentskills.io) format (`SKILL.md` per capability). Tools that support this standard can discover and load these skills automatically; the skills are tailored for **App Router** (e.g. setRequestLocale, draftMode(), component-map.ts + component-map.client.ts).
-
----
-
-## Why capability grouping
-
-Grouping related capabilities makes it easier to know which area of the app applies to a given task and to point to the right docs and patterns. Map the task to one or more of the groupings below; use AGENTS.md and the official docs for concrete steps.
-
----
-
-## Capability groupings
-
-### content-sdk-component-scaffold
-
-Creating new Sitecore components: file structure, props interface, and placement under `src/components/`. Use when adding a new component from scratch. In App Router, decide Server vs Client and register in the appropriate map.
-
-### content-sdk-component-registration
-
-Registering components in `.sitecore/component-map.ts` (Server) and `.sitecore/component-map.client.ts` (Client). Required so layout and editing can resolve and render components. App Router has separate server and client maps.
-
-### content-sdk-editing-safe-rendering
-
-Safe rendering in XM Cloud editing and preview: `draftMode()`, editing chromes, and design library. Use when ensuring components work in the Sitecore editor and preview. Use `client.getPreview(searchParams)` or `client.getDesignLibraryData(searchParams)` when draft mode is enabled.
-
-### content-sdk-field-usage-image-link-text
-
-Using SDK field components: `<Text>`, `<RichText>`, `<Image>`, `<Link>`, with proper validation and fallbacks. Use when rendering Sitecore fields.
-
-### content-sdk-graphql-data-fetching
-
-Page and dictionary fetching via the single Sitecore client in `src/lib/sitecore-client.ts`. Use `getPage(path ?? [], { site, locale })`, `getDictionary`, `getAppRouterStaticParams` for SSG. For preview use `draftMode()` and `getPreview`/`getDesignLibraryData` from searchParams.
-
-### content-sdk-route-configuration
-
-Routing: single catch-all at `src/app/[site]/[locale]/[[...path]]/page.tsx`. Layout: app/layout.tsx → app/[site]/layout.tsx → page. Call `setRequestLocale(\`${site}_${locale}\`)` at top of page. Use placeholders and Layout.tsx as in AGENTS.md.
-
-### content-sdk-site-setup-and-env
-
-Site and environment: `sitecore.config.ts`, environment variables, default site and language. Document vars in `.env.example` only; never commit `.env` or `.env.local`.
-
-### content-sdk-multisite-management
-
-Multisite: `.sitecore/sites.json`, proxy in `src/proxy.ts`. Chain order is **fixed:** LocaleProxy → AppRouterMultisiteProxy → RedirectsProxy → PersonalizeProxy. Do not change proxy order.
-
-### content-sdk-dictionary-and-i18n
-
-Dictionary and i18n: next-intl with `src/i18n/routing.ts` and `src/i18n/request.ts`. Request locale is `${site}_${locale}`; call `setRequestLocale(\`${site}_${locale}\`)` in the page; in request.ts parse and load dictionary with `client.getDictionary({ locale, site })`.
-
-### content-sdk-sitemap-robots
-
-Sitemap and robots: `src/app/api/sitemap/route.ts` and `src/app/api/robots/route.ts` with `createSitemapRouteHandler` and `createRobotsRouteHandler`. Rewrites in next.config.ts for /sitemap*.xml and /robots.txt.
-
-### content-sdk-component-variants
-
-Component variants: different renderings or data-driven variants of the same component type. Use when one component has multiple presentations. Register in the appropriate component map (server or client).
-
-### content-sdk-troubleshoot-editing
-
-Troubleshooting XM Cloud editing, preview, and design library. Use when editing or preview does not behave as expected. Check draftMode(), getPreview/getDesignLibraryData from searchParams, and component maps.
-
-### content-sdk-upgrade-assistant
-
-Upgrading @sitecore-content-sdk/* packages: version bumps, breaking changes, migration steps. Use when moving to a newer SDK version. Check the Content SDK repo CHANGELOG and upgrade guides.
-
-### content-sdk-component-data-strategy
-
-Component data: layout data from getPage (or getPreview/getDesignLibraryData in editing). Pass site and locale from route params; Server Components use the client in server context; Client Components receive serializable props from parent. BYOC must be registered in the component map.
-
----
-
-## How to use this
-
-Map the task to one or more groupings above. Use [AGENTS.md](AGENTS.md) for app-level instructions and the [official documentation](https://doc.sitecore.com/xmc/en/developers/content-sdk/sitecore-content-sdk-for-xm-cloud.html) for APIs.
-
-**If your tool supports Agent Skills:** Load skills from [.agents/skills/](.agents/skills/) (one folder per capability). They provide when-to-use, hard rules, and stop conditions tailored for this App Router app.