content-modeling-best-practices
Guidelines for designing scalable content models in Sanity
Developer Setup
Setup & Installation
npx skills add https://github.com/sanity-io/agent-toolkit --skill content-modeling-best-practicesnpx skills add https://github.com/sanity-io/agent-toolkit --skill content-modeling-best-practicesOverview
What This Skill Does
Structured guidance for designing content schemas in Sanity and other headless CMSes. Covers when to use references versus embedded objects, how to avoid page-shaped schemas, content reuse patterns, and taxonomy design. Applies to new projects and schema refactors alike.
Application
When to use this Skill
- Configuring integration settings for custom agent workflows.
- Optimizing query execution and response latency in production.
- Developing clean, standard-compliant implementations for enterprise services.
- Troubleshooting connection timeouts and authentication handshakes.
- Monitoring API rate limits and execution pipelines programmatically.
Documentation
Show Skills.md file
Content Modeling Best Practices
Principles for designing structured content that's flexible, reusable, and maintainable. These concepts apply to any headless CMS but include Sanity-specific implementation notes.
When to Apply
Reference these guidelines when:
- Starting a new project and designing the content model
- Evaluating whether content should be structured or free-form
- Deciding between references and embedded content
- Planning for multi-channel content delivery
- Refactoring existing content structures
Core Principles
- Content is data, not pages — Structure content for meaning, not presentation
- Single source of truth — Avoid content duplication
- Future-proof — Design for channels that don't exist yet
- Editor-centric — Optimize for the people creating content
References
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 objects
Recommendations
Explore other random skills
meeting-intelligence
Prepare meeting materials by gathering Notion context and creating pre-reads and agendas
research-documentation
Search Notion workspace, synthesize findings, and create comprehensive research reports
spec-to-implementation
Turn product/tech specs into concrete Notion tasks with acceptance criteria and progress tracking