---
name: craft-model
description: Codex skill alias for /craft-model. Start a content modeling session for a Craft CMS project
---

# Codex Command Alias: /craft-model

<!-- Generated by tools/generate-codex-command-skills.py; edit the source command instead. -->

- Expose `/craft-model` as a workflow entrypoint, not a CLI call. Treat the invoking message as arguments, substitute `$ARGUMENTS`, and follow this protocol in the current Codex harness.
- Resolve canonical `plugins/<name>/...` paths under that plugin's host-selected coherent installed bundle, not the consumer repository. Read nested SKILL.md files there and follow them inline when no generic Skill tool exists.
- Workflow-specific dispatch takes priority: use required model-router role-dispatch and retain its outputs and receipts. Use native subagents only when that workflow explicitly permits them.
- Do not launch another harness solely for its source or cache format. Explicit cross-harness requests and router-selected participant transports remain supported.
- Translate Claude tools when needed (`TodoWrite` to `update_plan`; `AskUserQuestion` to `request_user_input` or chat). Report the exact missing path/tool and preserve completed evidence; never manual-substitute required lanes or fabricate receipts.

## Command Workflow

# Content Modeling Assistant

Help the user design a content model for their Craft CMS project using the three-layer methodology.

## Your Approach

1. **Understand the project** -- Ask about the type of site, content needs, and team structure
2. **Identify content types** -- What kinds of content exist? Pages, articles, products, team members?
3. **Map relationships** -- How does content connect? Categories, authors, related items?
4. **Plan the architecture** -- Sections, entry types, Matrix fields, CKEditor configuration

## Methodology

Use the three-layer approach:

### Layer 1: Foundation
- Filesystems and volumes
- Basic fields (text, rich text, assets, dates)
- Entry types for sections and Matrix fields

### Layer 2: Structure  
- Matrix field configuration
- Section setup (Singles, Channels, Structures)
- CKEditor configuration
- Entries fields and relations

### Layer 3: Experience
- Field layouts and organization
- Author experience refinements
- Validation and required fields
- Element indexes and card views

## MCP Integration

If the Craft MCP server is available, use these tools to understand the current state:

- `list_sections` -- See existing sections and entry types
- `list_fields` -- Understand the current field architecture
- `list_entry_types` -- Review entry type configurations
- `get_database_schema` -- Inspect the underlying structure

## Output

Guide the user through decisions, explaining tradeoffs. Create actionable plans they can implement in the Craft control panel.