content-model-planner

Design CMS content model architectures with entity types, field bundles, and taxonomy relationships.

Updated Mar 5, 2026
One-click install
npx skills add https://github.com/zivtech/joyus-desktop --skill content-model-planner
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: content-model-planner
Source: https://github.com/zivtech/joyus-desktop/tree/main/.claude/skills/content-model-planner
Command: npx skills add https://github.com/zivtech/joyus-desktop --skill content-model-planner

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill eliminates technical debt and editorial friction by providing a structured, strategic approach to designing CMS content models before any configuration begins.

Core Features & Use Cases

  • Strategic Architecture: Define entity types, composition patterns, and field bundles to ensure long-term maintainability.
  • Editorial Alignment: Map content structures to actual editorial workflows to prevent user confusion and model workarounds.
  • Use Case: When planning a new headless CMS implementation, use this skill to design a robust entity relationship map and field architecture that supports future growth and simplifies content migration.

Quick Start

Invoke the content-model-planner skill to design a new content model architecture for a headless CMS project by providing your content requirements and platform details.

Frequently Asked Questions about content-model-planner

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I design a scalable content model architecture for a headless CMS?

Map content structures directly to actual editorial workflows to prevent user confusion, eliminate technical debt, and stop editors from relying on model workarounds during daily operations.

What is the best way to structure taxonomy relationships and field bundles for CMS governance?

The best way to structure taxonomy relationships for governance is applying a strategic architecture approach that defines entity types and field bundles before any platform configuration begins.

Can I use this approach to plan a migration-safe data structure for complex content migrations?

Yes, you can plan migration-safe data structures by designing performance-optimized reference mapping and robust entity relationship maps that simplify complex content migrations to new platforms.

Does content modeling strategy work for refactoring existing CMS platforms with technical debt?

Content modeling strategy works for refactoring existing platforms by providing a structured approach to redefine entity types and eliminate accumulated technical debt and editorial friction.

When do I need a formal content model architecture instead of building CMS configurations directly?

You need a formal content model architecture when implementing a new headless CMS, requiring editorial workflow alignment, or planning complex migrations that demand governance and long-term scalability.