Setup & Installation
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.
Without explicit modeling guidance, schemas tend to drift toward presentation-driven structures that break when you add a new channel or reuse content in a different context.
When to use it
- Deciding whether an author field should be a reference or an embedded object
- Refactoring a schema that was built around page layouts instead of content meaning
- Designing a content model that works across web, mobile, and email from one source
- Choosing between flat tags and hierarchical categories for a product taxonomy
- Auditing an existing Sanity schema for content duplication before a replatform