agentsclimarketplace

Content modeling best practices

Skill display-design-studio/skills/skills/content-modeling-best-practices

A curated skill collection for AI agents, including first-party skills and vendored framework/CMS best practices for use with the Agent Skills ecosystem and skills.sh.

Install
npx -y skills add display-design-studio/skills --skill content-modeling-best-practices

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

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.

SKILL.md

1.8 KB, as published. Nobody here has run it

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

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.