From sanity
Designs structured content models for headless CMSes: schema design, content reuse, reference vs. embedded objects, separation of concerns, taxonomies. Use when creating or refactoring content types.
How this skill is triggered — by the user, by Claude, or both
Slash command
/sanity:content-modeling-best-practicesThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Principles for designing structured content that's flexible, reusable, and maintainable. These concepts apply to any headless CMS but include Sanity-specific implementation notes.
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:
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:
references/separation-of-concerns.md — Separating content from presentationreferences/reference-vs-embedding.md — When to use references vs embedded objectsreferences/content-reuse.md — Content reuse patterns and the reuse spectrumreferences/taxonomy-classification.md — Flat, hierarchical, and faceted classificationnpx claudepluginhub sanity-io/agent-toolkit --plugin sanityDesigns content type hierarchies, reusable parts, and field compositions for headless CMS using Type > Part > Field pattern. Covers composition vs inheritance and multi-channel reusability.
Explains core Contentful concepts and routes users to the right implementation skill or documentation. Clarifies APIs (CDA/CPA/CMA/GraphQL) and Contentful MCP server.
Provides Sanity development best practices for schema design, GROQ queries, Visual Editing, images, Portable Text, Studio structure, localization, migrations, Sanity Functions, Blueprints, and framework integrations (Next.js, Nuxt, Astro, Remix, SvelteKit, Angular, Hydrogen).