From sanity
Guides content modeling best practices for Sanity and headless CMSes: schema design, content architecture, reuse, references vs. embeds, separation of concerns, taxonomies. For designing or refactoring content types.
npx claudepluginhub anthropics/claude-plugins-official --plugin sanityThis skill uses the workspace's default tool permissions.
Principles for designing structured content that's flexible, reusable, and maintainable. These concepts apply to any headless CMS but include Sanity-specific implementation notes.
Designs content type hierarchies, reusable parts, and field compositions for headless CMS using Type > Part > Field pattern. Covers composition vs inheritance and multi-channel reusability.
Designs author-friendly content models for AEM Edge Delivery blocks. Use when creating new blocks or changing existing ones that alter authoring structure.
Provides Sanity best practices for schema design, GROQ queries, TypeGen, Visual Editing, images, Portable Text, Studio structure, localization, migrations, Functions, Blueprints, and integrations with Next.js, Nuxt, Astro, Angular, SvelteKit.
Share bugs, ideas, or general feedback.
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 classification