content-experimentatio…
Content experimentation and A/B testing guidance covering experiment design, hypotheses, metrics, sample size, statistical…
Structured content modeling guidance for schema design, content architecture, content reuse, references versus embedded objects, separation of concerns, and taxonomies across Sanity and other headless CMSes. Use this skill when designing or refactoring content types, deciding
Claude Code
$ npx -y skills add sanity-io/agent-toolkit --skill content-modeling-best-practices --agent claude-code
Codex
$ npx skills add sanity-io/agent-toolkit --skill content-modeling-best-practices -a codex -y
Cursor
$ npx skills add sanity-io/agent-toolkit --skill content-modeling-best-practices -a cursor -y
Gemini CLI
$ npx skills add sanity-io/agent-toolkit --skill content-modeling-best-practices -a gemini-cli -y
GitHub Copilot
$ npx skills add sanity-io/agent-toolkit --skill content-modeling-best-practices -a github-copilot -y
OpenCode
$ npx skills add sanity-io/agent-toolkit --skill content-modeling-best-practices -a opencode -y
Windsurf
$ npx skills add sanity-io/agent-toolkit --skill content-modeling-best-practices -a windsurf -y
name: content-modeling-best-practices description: Structured content modeling guidance for schema design, content architecture, content reuse, references versus embedded objects, separation of concerns, and taxonomies across Sanity and other headless CMSes. Use this skill when designing or refactoring content types, deciding field shapes, debating reusable versus nested content, planning omnichannel content models, or reviewing whether a schema is too page-shaped or presentation-driven.
Principles for designing structured content that's flexible, reusable, and maintainable. These concepts apply to any headless CMS but include Sanity-specific implementation notes.
Reference these guidelines when:
1. **Content is data, not pages** — Structure content for meaning, not presentation 2. **Single source of truth** — Avoid content duplication 3. **Future-proof** — Design for channels that don't exist yet 4. **Editor-centric** — Optimize for the people creating content
Start with the reference that matches the modeling decision in front of you, instead of loading every topic at once. See `references/` for detailed guidance on specific topics:
Content experimentation and A/B testing guidance covering experiment design, hypotheses, metrics, sample size, statistical…
Convert HTML and Markdown content into Portable Text blocks for Sanity. Use when migrating content from legacy CMSs, importing…
Render and serialize Portable Text to React, Svelte, Vue, Astro, HTML, Markdown, and plain text. Use when implementing Portable…
Sanity development best practices for schema design, GROQ queries, TypeGen, Visual Editing, images, Portable Text, Studio…
Fix a Sanity Studio custom form component (components.input, components.field, components.item, or a plugin's form.components)…
Plans, implements, and reviews migrations from other CMSes and content systems into Sanity. Use when migrating or replatforming…
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or…
Ask which skill or flow fits your situation. A router over the skills in this repo.