content-model-critic

Evaluates CMS content model architectures for editorial scalability, maintainability, and migration readiness.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill identifies structural flaws in CMS content models that lead to editorial friction, maintenance debt, and migration nightmares, ensuring your architecture is built for long-term growth rather than just schema correctness.

Core Features & Use Cases

  • Architectural Audit: Evaluates entity type proliferation, field reuse patterns, and taxonomy coupling to prevent bloat.
  • Workflow Alignment: Diagnoses whether your model supports actual editorial processes or forces users into inefficient workarounds.
  • Risk Assessment: Identifies circular dependencies, performance bottlenecks like N+1 queries, and migration risks before they harden in production.

Quick Start

Use the content-model-critic skill to review the current content model documentation and identify potential architectural gaps.

Frequently Asked Questions about content-model-critic

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

FAQPage Schema
How do I audit a CMS content model for editorial scalability?

To audit a CMS content model for editorial scalability, evaluate entity type design, field reuse patterns, taxonomy coupling, and reference structures to identify structural flaws that cause maintenance debt and migration risks.

What causes editorial friction and maintenance debt in CMS architectures?

Structural flaws like entity type proliferation, circular dependencies, and tight taxonomy coupling cause editorial friction and maintenance debt by forcing inefficient workarounds and creating migration nightmares.

How do I identify circular dependencies and N+1 query bottlenecks in a content model?

You identify circular dependencies and N+1 query bottlenecks by analyzing reference structures and taxonomy coupling across CMS platforms, providing evidence-based findings on structural risks before they harden in production.

Can I evaluate content model migration readiness across different CMS platforms?

You can evaluate migration readiness across various CMS platforms by analyzing entity type design and reference structures to diagnose structural flaws that lead to migration nightmares before they harden.

Does the content model audit diagnose alignment with actual editorial workflow processes?

Yes, the audit diagnoses workflow alignment by evaluating whether your entity types and reference structures support actual editorial processes or force users into inefficient workarounds.