Every decision already
made. So you can skip
to the actual work.
The Content Architecture is the production foundation underneath my client work.
Hundreds of choices, schema, fetching, structure, SEO, made once over six years and
committed. Not a starter you outgrow in a month. Clone it, rename it, ship. The
architecture is fixed; the tools are defaults you can swap. Fixed decisions are also
what make agentic development work: an agent inside committed conventions ships, an
agent without them redesigns.
001 / AGENT-NATIVE
AGENTS.md and a dozen scoped skills let Claude Code or Cursor ingest the conventions before the first prompt, instead of proposing a plausible new architecture per run. Two preconfigured MCP servers ship in the repo: one reads the Next.js runtime, compilation errors, routes, docs matching the installed version, the other drives a real Chrome for screenshots, traces, and screencasts. The agent builds inside the decisions and checks its own work.
002 / AGENT-READY IN PRODUCTION
The shipped site stays legible to agents that read it. An editable llms.txt, drafted from your content with Sanity Agent Actions, and a token-light Markdown version of every page, served on the same URL through content negotiation. Generated in Studio, served verbatim, and a feature you can put in your own proposal.
003 / SCHEMA AS A SYSTEM
Document roles, factory functions, singletons. Every schema looks the same, so every editor knows where to go. You never model the structure from scratch again.
004 / THE HARD FIELDS, ALREADY BUILT
The three fields nobody gets right the first time. A link field that handles internal refs, external URLs, email, and params. A media field that normalizes image, Mux, Rive, and Lottie into one shape, each returning dimensions, so you forget layout shift. A page builder with guardrails. Reusable, typed, composed everywhere.
005 / FETCH LAYER, SOLVED
CDN bypassed in production, Data Cache doing the work, webhooks invalidating on publish, draft mode wired in. Stale content after publish stops being a midnight problem.
006 / A STUDIO EDITORS ACTUALLY USE
Every document type where editors expect it. Pages own their routes, singletons stay locked, no hunting. Clients stop emailing to ask where their homepage lives.
007 / SEO, DONE NOT DEFERRED
Per-page metadata from schema, sitemap driven by Sanity, OpenGraph with auto-cropped images, robots.txt included. Nothing bolted on the week before launch.
008 / PRODUCTION-READY FROM DAY ONE
Basic auth, spam-protected forms, redirects managed in Sanity, analytics, view transitions. The plumbing you reconfigure every project, already wired.
009 / WIRED UP, NOT JUST CLONED
An interactive setup script provisions the Sanity project, mints the tokens, adds CORS, and registers the revalidation webhook, then writes your .env. Export and migration scripts back up production and move content between environments. The first run is handled, not documented.