From content-management-system
Designs CMS content type schemas with fields, parts, validation, and relationships. Supports full workshop, quick, or guided modes; outputs YAML, JSON, or C# EF Core models.
How this skill is triggered — by the user, by Claude, or both
Slash command
/content-management-system:model-contentThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Design a content type schema with parts, fields, and validation rules.
Design a content type schema with parts, fields, and validation rules.
/cms:model-content Article --mode guided
/cms:model-content Product --mode quick --format csharp
/cms:model-content Event --mode full
Extract content type name and options from the command.
Full Mode:
cms-facilitator content-modeling agent for workshopQuick Mode:
content-type-modeling skillGuided Mode:
Generate content type definition in requested format:
content_type:
name: Article
display_name: Article
description: Blog articles and news posts
stereotype: Document
parts:
- name: TitlePart
built_in: true
- name: AutoroutePart
built_in: true
- name: ArticlePart
custom: true
fields:
- name: Body
type: HtmlField
required: true
editor: wysiwyg
- name: Excerpt
type: TextField
required: false
hint: Short summary for listings
- name: FeaturedImage
type: MediaField
required: false
allowed_types: [image/*]
- name: Categories
type: TaxonomyField
taxonomy: categories
required: true
min: 1
- name: Tags
type: TaxonomyField
taxonomy: tags
required: false
- name: Author
type: ContentPickerField
content_types: [Author]
required: true
settings:
creatable: true
listable: true
draftable: true
versionable: true
content-type-modeling - Content type patternsdynamic-schema-design - EF Core JSON columnscontent-relationships - Field relationshipsnpx claudepluginhub melodic-software/claude-code-plugins --plugin content-management-systemDesigns 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 structured content models for headless CMSes: schema design, content reuse, reference vs. embedded objects, separation of concerns, taxonomies. Use when creating or refactoring content types.
Creates content type definitions, display templates, and contracts for Optimizely CMS. Use when modeling pages, components, or reusable property sets.