An agentic flow for SitecoreAI head apps.

Reads the existing CM's content model — templates, renderings, field contracts — so /architect designs against real shapes, not assumptions. Runs before /architect.

Stands up the decoupled CM + editing host and deploys the baseline — non-interactive, idempotent, from one deploy-admin client. Runs before /implement.

A visual Components Map — every component, its variants, its fields, and a real screenshot — so the Content Author knows when to use which component and which variant. Proven on Umbra Roasters. Runs before authoring.

Writes on-brand copy in a chosen voice and lands it in Sitecore via the Marketer MCP — and commissions on-brand imagery for empty slots. A Content QA gate confirms it actually rendered. The content phase now runs AFTER /ship, against preview.

The final live step. Publishes everything — layout, content, media — onto a LIVE edge context, ser-pulls the authored items back into the CM code base for git durability, and redeploys the public host. Preview-first / publish-last: nothing goes live before this operator-confirmed gate.

4 resolver variants → 2 React shapes

Datasource + Context, each in Item + Children form, look like four distinct patterns. They collapse to TWO React-side payload shapes (single-item flat hash; children-list wrapper). Same React code handles both members of each pair.

Edge has hard, undocumented limits

15-level depth limit kills the standard IntrospectionQuery. Query complexity scales with pagination + nesting — first:100 with nested fields gets rejected, first:10 works. There is no /schema endpoint; POST + per-type introspection is the only path.

Server Action for reads = endless flicker

Server Actions auto-trigger router.refresh() after returning. For mutations, that is the feature. For client-triggered reads from a hover handler, it wipes every NavBranch state, the dropdown closes, the user re-hovers, repeat. Route Handlers have zero refresh side-effect; that is the right tool for reads.

Component-level nav > SXA Navigation Resolver

The resolver was returning fields: [] with no clear cause. Replacing it with a custom GraphQL query — server L1 with hasChildren flag, lazy L2 per-hover — is more predictable, type-safe, recursive to any depth, and stays under Edge limits because each branch fetch is independent.

Support files inside component folders auto-register

Place types.ts, queries.ts, a NavBranch.tsx client child, or an actions.ts under src/components/<X>/ — gen-map registers them as variants of <X> or as standalone Sitecore renderings. Only the rendering .tsx (plus .<Variant>.tsx siblings) belongs in that folder. Everything else lives in src/lib/, src/ui/, or src/app/api/.

Generic parameter names collide silently

Naming a rendering parameter "Levels" made it disappear from the Pages editor — collision with a base-template field. Renaming to "Level" (singular) made it visible. The rule: namespace your rendering-parameter names or use singular forms; avoid Levels / Depth / Style / Items.

Multilingual support

The big one. Author and publish a head app across multiple languages in one run — next-intl wiring, per-language Edge fetches, dictionary loading, and the content agent writing each locale. The playground already carries four languages on file; making the whole flow language-aware is the next major lift.

Fully autonomous runs

Idea to a published, live site with zero operator gates — the pipeline running the whole distance on its own, gated only by the checks it runs on itself. The highest-trust item on the list; it has to earn its way there run by run.

Testing & hardening

Broader automated coverage across the Sitecore branch — more edge cases, content-resilience, and real-tenant smoke automation — so a green run means more than it does today. The unglamorous work that makes autonomy safe.

Token-consumption optimization

Make each run leaner and cheaper — trim context, prune the dark skills, tighten agent hand-offs, and measure token spend per stage. Efficiency treated as a first-class goal, not an afterthought.

Personalization

Deferred. @sitecore-content-sdk/personalize integration, A/B variants, audience targeting. Distinctively Sitecore; needs its own probing session.

Forms

Deferred. Sitecore Forms rendering, validation, submission flow. A common requirement for any real site; gets its own skill once the first project needs it.