content-modeling-assistant
Install
Pick the surface you use. Plugins run inside Claude Code, which is available in the terminal CLI, the desktop app on Mac and Windows, the web app at claude.ai/code, and the VS Code and JetBrains extensions. The slash commands are identical on every surface.
From inside any Claude Code session — terminal, desktop app, web app, or IDE extension:
-
Add the RBA Skills marketplace (only needed once per machine):
/plugin marketplace add rbaconsulting/rba-skills-plugin -
Install content-modeling-assistant:
/plugin install content-modeling-assistant@rba-ai-hub -
Activate it without restarting:
/reload-plugins
Prefer to browse and click? Run /plugin inside Claude Code to open the interactive plugin manager. It looks the same in the desktop app, web app, terminal, and IDE extensions.
-
Open the plugin manager:
/plugin - Press Tab to reach Marketplaces, choose Add, then enter
rbaconsulting/rba-skills-plugin. - Press Tab again to Discover. Search for
content-modeling-assistant, press Enter, and pick a scope (User, Project, or Local). - Run
/reload-pluginsto activate it.
If you have the Claude Code CLI installed and want to drive it from a normal shell prompt:
$ claude plugin marketplace add rbaconsulting/rba-skills-plugin
$ claude plugin install content-modeling-assistant@rba-ai-hub The next Claude Code session loads it automatically.
Overview
Content Strategy & Modeling Assistant
RBA Consulting's toolkit for designing enterprise content architectures from first principles. This plugin gives strategists, information architects, and DXP engineers a structured, repeatable process for defining content types, building taxonomy and metadata schemas, producing editorial governance frameworks, and generating content matrices — all calibrated to RBA's Microsoft/Azure foundation and certified Sitecore, Optimizely, and Umbraco partnerships.
What's inside
| Artifact | Purpose |
|---|---|
content-type-modeler skill |
Designs a complete, platform-neutral content type hierarchy from requirements. Outputs a structured schema with fields, field types, inheritance, and relationship map. Adapters for Sitecore XM Cloud, Optimizely CMS SaaS, Umbraco, Contentful, and Contentstack. |
taxonomy-schema-designer skill |
Builds a controlled-vocabulary taxonomy: hierarchical, flat, or faceted. Produces term lists, parent–child relationships, usage guidelines, and a governance policy for term creation and retirement. |
metadata-schema-builder skill |
Defines a canonical metadata schema covering SEO, Open Graph, structured data (JSON-LD), localization, and personalization signals. Produces a field-by-field spec with required/optional flags, allowed values, and per-platform implementation notes. |
editorial-governance-framework skill |
Authors an editorial governance document: content lifecycle, roles and responsibilities, workflow stages (draft → review → approve → publish → archive), quality gates, and compliance requirements. |
content-matrix-generator skill |
Maps content types to channels, audiences, personas, and lifecycle stages. Produces a prioritised matrix that connects strategy and IA decisions to implementation backlog. |
content-model-reviewer agent |
Reviewer subagent: validates a draft content model or taxonomy against RBA's structured-content principles and returns a structured critique. |
/model-content command |
Guided entry-point slash command: collects project context and routes to the right skill or combination. |
When to use
Use this plugin at the strategy and discovery phase of any DXP, CMS re-platform, or headless-channel project. It is especially valuable when:
- A client is migrating from a legacy CMS and needs a clean content model before field mapping begins
- A new digital experience is being designed and content strategy has not yet defined types, taxonomy, or metadata
- Multiple editorial teams are working in one CMS with inconsistent content structures
- A composable DXP is being introduced and content reusability across channels (web, app, kiosk, email) must be designed in from day one
- Editorial governance is absent or outdated and the client needs role/workflow policies before go-live
Platform adapters
All skills are platform-neutral by default and produce implementation notes for each target platform:
- Sitecore XM Cloud — Data Templates, Base Templates, template inheritance, field sharing (Shared vs. Versioned vs. Unversioned), Content Hub One content types and components, Stream AI field hints
- Optimizely CMS SaaS — Content types (Experience, Section, Element, Page, Block, Media), Properties with attribute decoration, Content Graph schema impact, Opal AI metadata signals
- Umbraco — Document Types, Compositions (mixins), Data Types, Media Types, Member Types, Content Delivery API shape, Heartcore JSON output
- Contentful — Content Types, Fields, Rich Text with embedded entries, References, Locales, Content Model export JSON
- Contentstack — Content Types, Global Fields (reusable), Extensions, Branches for multi-brand, Automation Hub taxonomy sync
How to install
claude plugin install content-modeling-assistant@rba-ai-hub
Start with the guided entry point for an intake conversation that routes to the right skill:
/model-content
Or invoke any skill directly — for example, to design a content model from an existing requirements document:
/content-type-modeler requirements.md --platform sitecore-xm-cloud
Tools and permissions
These skills read project files, produce structured Markdown and JSON deliverables, and optionally fetch platform documentation for adapter-specific field type references. No credentials, no cloud CLI access, no destructive file operations.
Bundled artifacts
Skills
- content-matrix-generator — Maps content types to channels, audiences, personas, and buyer journey stages to produce a prioritised content matrix. Shows which content types serve which audiences across which channels, identifies gaps where personas are underserved, and connects IA decisions to a prioritised implementation backlog. Use when aligning strategy and IA to delivery planning, after content types are defined — e.g. "create a content matrix for our B2B SaaS site", "map our content types to buyer journey stages", or "which content types do we need for our launch MVP vs phase 2".
- content-type-modeler — Designs a complete, platform-neutral content type hierarchy from project requirements, existing content audits, or a brief description. Outputs a structured schema with content types, field definitions, field types, inheritance/composition chains, relationship maps, and per-platform implementation notes. Use when starting a new DXP build, migrating from a legacy CMS, or rationalising an inherited content model — e.g. "model content types for a B2B services site on Sitecore XM Cloud", "design a composable content model for a multi-brand retail DXP", or "turn this content audit into a clean type hierarchy".
- editorial-governance-framework — Authors a comprehensive editorial governance document covering content lifecycle, roles and responsibilities, workflow stages (draft → review → approve → publish → archive), quality gates, compliance requirements, and taxonomy maintenance policies. Designed for DXP and headless CMS projects where multiple editorial teams or stakeholders share one publishing platform. Use when onboarding a new editorial team to a CMS, establishing governance before a platform migration go-live, or remediating inconsistent content practices — e.g. "write an editorial governance document for our Sitecore XM Cloud site", "define content workflow roles for our multi-brand Optimizely CMS", or "document publishing standards for our Umbraco site ahead of launch".
- metadata-schema-builder — Defines a canonical metadata schema for a DXP or CMS project covering SEO, Open Graph, Twitter Card, structured data (JSON-LD Schema.org), localisation, personalization signals, and analytics data layer. Produces a field-by-field specification with required/optional flags, allowed values, character limits, and per-platform implementation notes (Sitecore, Optimizely, Umbraco, Contentful, Contentstack). Use when standardising metadata across a multi-template site, establishing SEO hygiene before migration go-live, or designing the structured data layer for a new DXP build — e.g. "build a metadata schema for our Sitecore XM Cloud site", "define SEO and JSON-LD fields for our Optimizely product pages", or "standardise metadata across 12 content types".
- taxonomy-schema-designer — Builds a controlled-vocabulary taxonomy for a DXP or CMS project: hierarchical, flat, or faceted structures. Produces term lists, parent–child relationships, scope notes, usage guidelines, and a governance policy for term creation, maintenance, and retirement. Includes per-platform implementation notes (Sitecore, Optimizely, Umbraco, Contentful, Contentstack). Use when establishing the tagging and categorisation foundation for a new or re-platformed digital experience — e.g. "design a product taxonomy for our B2B site", "build a topic taxonomy for our editorial CMS", or "design faceted taxonomy for a resource library".
Agents
- content-model-reviewer — Reviews a draft content model, taxonomy schema, or metadata schema document against RBA's structured-content principles and returns a structured critique. Flags anti-patterns (deep inheritance, unstructured rich text over-reliance, missing base types, undocumented taxonomy governance, incomplete metadata), scores the deliverable, and provides actionable remediation steps. Use as a review step before presenting content model deliverables to a client or handing off to the engineering team.
Slash Commands
- /model-content — Guided entry point for the Content Strategy & Modeling Assistant plugin. Runs a structured intake conversation to identify the project context, target platform, and desired output, then routes to the appropriate skill or combination: content-type-modeler, taxonomy-schema-designer, metadata-schema-builder, editorial-governance-framework, or content-matrix-generator. Use to start any new content modeling engagement.
Technical details
- Homepage
- https://rba-skills.tylerschroeder.net/plugins/content-modeling-assistant/
- License
- MIT
- Maturity
- experimental
- Security review
- No security review
- Owners
-
- strategy
- Platforms
- sitecore, optimizely, umbraco
- Disciplines
- strategy, design
- Lifecycle
- plan, build
- Tags
- Last updated
- by Tyler Schroeder
- Source
plugins/content-modeling-assistant/
Edit this plugin's README on GitHub — opens GitHub's web editor. No git knowledge needed.