Skill

map-relationships

Visualizes content type relationships as Mermaid diagrams, ASCII trees, or YAML data. Flags circular dependencies, orphans, and coupling issues in CMS models.

developer-tools

documentation

npx claudepluginhub melodic-software/claude-code-plugins --plugin content-management-system

Tool Access

This skill is limited to using the following tools:

ReadGlobGrepTaskSkill

Preview

Generate a visual representation of content type relationships.

SKILL.md

Similar Skills

content-relationships

Designs content relationships in headless CMS: one-to-many, many-to-many junctions, hierarchies, polymorphic refs, bidirectional links, reference integrity, and loading strategies.

5 tools

content-management-system

mapping-visualization-scaffolds

Guides creation of diagrams, concept maps, and architectural blueprints to visualize relationships, dependencies, and structures. Useful for documenting complex systems, component mappings, hierarchies, processes, architectures, and data flows.

3 files

thinking-frameworks-skills

content-modeling-best-practices

114

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.

4 files

sanity

Stats

Parent Repo Stars40

Parent Repo Forks6

Last CommitMar 17, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

Map Relationships Command

Generate a visual representation of content type relationships.

Usage

/cms:map-relationships --output mermaid
/cms:map-relationships --output ascii --scope type:Article
/cms:map-relationships --output yaml

Output Formats

mermaid: Mermaid diagram syntax
ascii: Text-based diagram
yaml: Structured relationship data

Workflow

Step 1: Parse Arguments

Extract output format and scope from command.

Step 2: Analyze Content Types

Read existing content type definitions from:

Skill knowledge (if designing)
Codebase (if implemented)

Step 3: Invoke Skill

Invoke content-relationships skill to analyze:

Direct references (ContentPickerField)
Taxonomy associations
Media references
Self-referential relationships

Step 4: Generate Output

Mermaid Output:

graph LR
    Article -->|author| Author
    Article -->|categories| Category
    Article -->|tags| Tag
    Article -->|featuredImage| Media
    Article -->|relatedArticles| Article

    Product -->|categories| ProductCategory
    Product -->|images| Media
    Product -->|variants| ProductVariant

    ProductVariant -->|product| Product

    Page -->|parent| Page
    Page -->|featuredImage| Media

ASCII Output:

CONTENT RELATIONSHIP MAP
========================

Article
├── author ──────────> Author (1:1)
├── categories ──────> Category (1:N)
├── tags ────────────> Tag (1:N)
├── featuredImage ───> Media (1:1)
└── relatedArticles ─> Article (N:N, self)

Product
├── categories ──────> ProductCategory (1:N)
├── images ──────────> Media (1:N)
└── variants ────────> ProductVariant (1:N)

ProductVariant
└── product ─────────> Product (N:1, inverse)

Page
├── parent ──────────> Page (N:1, self)
└── featuredImage ───> Media (1:1)

YAML Output:

relationships:
  Article:
    - field: author
      target: Author
      cardinality: one-to-one
      required: true

    - field: categories
      target: Category
      cardinality: one-to-many
      required: true

    - field: relatedArticles
      target: Article
      cardinality: many-to-many
      self_referential: true

  Product:
    - field: variants
      target: ProductVariant
      cardinality: one-to-many
      inverse: product

Step 5: Identify Issues

Flag potential problems:

Circular dependencies
Orphan content types
Missing inverse relationships
Over-coupled types

Related Skills

content-relationships - Relationship patterns
content-type-modeling - Content type structure