// Create a new .context domain folder with overview and patterns files following the Substrate methodology. Use when adding a new documentation domain to the project.
Validate .context/ files for quality, staleness, and conformance to the Substrate methodology. Run after making changes to documentation.
Create a new Architecture Decision Record in .context/decisions/. Use when documenting an architectural decision.
Generate tool-specific configuration files (Cursor rules, Copilot instructions, Windsurf rules) from the .context/ documentation. Use when setting up a project for a specific AI coding tool.
| name | new-domain |
| description | Create a new .context domain folder with overview and patterns files following the Substrate methodology. Use when adding a new documentation domain to the project. |
| argument-hint | ["domain-name"] |
| disable-model-invocation | true |
Create a new .context/ domain folder for $ARGUMENTS.
.context/$ARGUMENTS/overview.md with this structure:# Domain: [Name]
Brief description of what this domain covers.
## Overview
High-level description with context.
## Implementation Patterns
Code examples and standard approaches.
## Decision History & Trade-offs
Why choices were made, alternatives considered.
## Integration Points
How this domain connects to others.
patterns.md if the domain has code patterns to document.context/substrate.md to add the new domain under "Core Domains"CLAUDE.md under "Task-Specific Context" if it needs task-specific file pointersAGENTS.md to add the domain under "Context Files by Task".context/auth/ or .context/api/ as examples)