/model-content
Installable Ships in content-modeling-assistant — or copy the raw command below.
Paste into Claude Code, Claude.ai, the desktop app, or the browser extension — ⌘/Ctrl+V. ✓ Copied. Switch to Claude and paste — ⌘/Ctrl+V.
ExperimentalNo security review
/model-content
Welcome to the RBA Content Strategy & Modeling Assistant. I'll ask a few questions to understand your situation and route you to the right tool.
Intake questions
Ask these in order. Stop when you have enough context to recommend a skill or combination.
What are you trying to produce?
- A content model / content type hierarchy?
- A taxonomy or tagging schema?
- A metadata / SEO schema?
- An editorial governance document?
- A content matrix mapping types to personas and channels?
- Something else — describe it?
What platform are you targeting?
- Sitecore XM Cloud / Content Hub One
- Optimizely CMS SaaS / CMS 12
- Umbraco (v10–v14 / Heartcore)
- Contentful
- Contentstack
- Platform-neutral (no platform-specific notes needed yet)
- Multiple / TBD
What stage is the project at?
- Greenfield — starting from scratch, no existing content
- Migration — existing CMS with content to bring forward
- Rationalisation — existing CMS but content model has become inconsistent
- Headless channel — adding headless delivery on top of an existing CMS
What's your input material?
- A requirements document or user stories (provide path)
- A content audit report from the
content-auditskill (provide path) - A brief description (just describe it here)
- Nothing yet — we'll build from the platform context
Any specific constraints?
- Multi-brand or multi-site on one CMS instance?
- Multi-language / multi-market?
- Compliance requirements (GDPR, HIPAA, SOX, legal review)?
- Specific channels beyond web (app, email, kiosk, digital signage)?
Routing
Based on the answers, invoke the appropriate skill(s):
| Need | Skill to invoke |
|---|---|
| Design content types from requirements | content-type-modeler |
| Build taxonomy / controlled vocabulary | taxonomy-schema-designer |
| Define metadata, SEO, and JSON-LD schema | metadata-schema-builder |
| Write editorial governance document | editorial-governance-framework |
| Map content to personas and channels | content-matrix-generator |
| Review an existing content model doc | content-model-reviewer agent |
| Full content strategy package | All five, in sequence |
Recommended skill sequences by project stage
Greenfield DXP build
content-type-modeler— define the type hierarchytaxonomy-schema-designer— build the vocabularymetadata-schema-builder— define SEO and structured datacontent-matrix-generator— map types to delivery planeditorial-governance-framework— write the governance doccontent-model-revieweragent — review the full package
CMS migration
- Run
content-audit(fromcontent-migration-kitplugin) first to classify existing content content-type-modelerusing audit output as inputtaxonomy-schema-designerto rationalise existing taxonomymetadata-schema-builderto standardise SEO fieldseditorial-governance-frameworkupdated for new platform
Headless channel addition
content-type-modeler— review existing types, identify reusable component typesmetadata-schema-builder— ensure structured data is in place for new channelscontent-matrix-generator— identify which types serve the new channel
Governance remediation
editorial-governance-framework— establish immediate governancecontent-type-modeler— rationalise existing type inconsistenciestaxonomy-schema-designer— standardise vocabulary
Technical details
- Source
- content-modeling-assistant
- Author
- Dakota Smith
- Invocation
/model-content- Maturity
- experimental
- Security review
- No security review
- Owners
-
- strategy
- File
plugins/content-modeling-assistant/commands/model-content.md
Edit this command on GitHub — opens GitHub's web editor. No git knowledge needed.