Content Modeling Best Practices
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.
Install
npx skills add sanity-io/agent-toolkit --skill content-modeling-best-practicesgit clone --depth 1 https://github.com/sanity-io/agent-toolkit.git /tmp/agent-toolkit
mkdir -p ~/.claude/skills
cp -r /tmp/agent-toolkit/skills/content-modeling-best-practices ~/.claude/skills/content-modeling-best-practicesPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# 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 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 ## 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 presentation - `references/reference-vs-embedding.md` — When to use references vs embedded objects - `references/content-reuse.md` — Content reuse patterns and the reuse spectrum - `references/taxonomy-classification.md` — Flat, hierarchical, and faceted classification
Details
- Skill name
content-modeling-best-practices- Repository
- sanity-io/agent-toolkit
- Path
skills/content-modeling-best-practices/SKILL.md- License
- MIT
- Repo updated
- 27 October 2026
- Listed in
- heilcheng/awesome-agent-skills
FAQ
What does the Content Modeling Best Practices skill do?
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.
How do I install the Content Modeling Best Practices skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add sanity-io/agent-toolkit --skill content-modeling-best-practices. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Content Modeling Best Practices popular?
It lives in sanity-io/agent-toolkit, which has 194 GitHub stars and 31 forks, and is included in 1 curated skill list.
Related skills
Sanity Best Practices
194sanity-io/agent-toolkit
Sanity development best practices for schema design, GROQ queries, TypeGen, Visual Editing, images, Portable Text, Studio structure, localization, migrations, Sanity Functions, webhooks, Blueprints, and framework integrations such as Next.js, Nuxt, Astro, Remix, SvelteKit, Angular, Hydrogen, the App SDK, and Studios or apps running in the Sanity Dashboard (defineApplication). Use this skill whenever working with Sanity schemas, defineType or defineField, GROQ or defineQuery, content modeling, Presentation or preview setups, Sanity-powered frontend integrations, event-driven content automation,
SEO Aeo Best Practices
194sanity-io/agent-toolkit
SEO and AEO best practices for metadata, Open Graph, sitemaps, robots.txt, hreflang, JSON-LD structured data, EEAT, and content optimized for search engines and AI answer surfaces. Use this skill when implementing page SEO, technical SEO, schema markup, international SEO, AI-overview readiness, or improving content for Google, ChatGPT, Perplexity, and similar assistants.
Clarity
337addyosmani/clarity
Draft, rewrite, or review reader-facing prose so it is specific, useful, and recognizably the author's without inventing facts or performing humanness. Use for essays, articles, newsletters, documentation, talks, launch copy, and other important prose that feels generic, hollow, or AI-shaped. Supports co-write, rewrite, review, and lint modes.
Sloptrim
412seyedehsanhadi/sloptrim
Use when the user wants to humanize text, trim slop, de-AI or de-slop writing, remove AI tells, fix robotic or ChatGPT-sounding prose, or make writing sound human and natural. Also run before delivering a CV, cover letter, email, report, or essay to be sent. Removes 71 documented AI-writing patterns with a local detector, preserves numbers, names and citations, and rebuilds toward a human voice rather than a flat husk. Mode-aware, so it never fabricates voice on factual content.
I18next Localization
248i18next/i18next-cli
Takes an app from hardcoded strings to a localized, continuously translated one with i18next (Locize optional): stack detection, config, wrapping strings in t(), key extraction, Locize sync, and AI translation. Use when the user asks to add or set up i18n, internationalization, localization, translations, or multi-language support, including phrasings like "add i18n", "internationalize my app", "make my app multilingual", "make my app translatable", "localize my app", "find hardcoded strings", "wrap my strings", and library-specific ones like "set up i18next", "add react-i18next", "use next-i1
Humanities Writing Companion
471tizzy916/humanities-writing-companion
Help with humanities scholarly writing: sharpen research questions, map supplied readings, plan and draft arguments, review chapters, preserve authorial voice, and respond to reviewers. Use for history, philosophy, literature, and related argumentative scholarship, including 论文、改论文、文献综述、审稿意见、我手写我口, or “review this paragraph” when an academic draft is in context. Not for unrelated copywriting or a standalone literature-search pipeline.
Browse the most popular Claude skills, all writing & content skills, or write your own with the skills generator.