new-domain
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.
Best use case
new-domain is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
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.
Teams using new-domain should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/new-domain/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How new-domain Compares
| Feature / Agent | new-domain | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
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.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
Create a new `.context/` domain folder for `$ARGUMENTS`. ## Steps 1. Create the directory `.context/$ARGUMENTS/` 2. Create `overview.md` with this structure: ```markdown # 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. ``` 3. Create `patterns.md` if the domain has code patterns to document 4. Update `.context/substrate.md` to add the new domain under "Core Domains" 5. Add the domain to `CLAUDE.md` under "Task-Specific Context" if it needs task-specific file pointers 6. Update `agents.md` to add the domain under "Context Files by Task" ## Rules - Follow existing domain structure (see `.context/auth/` or `.context/api/` as examples) - Use project-specific content, not generic best practices - Include decision rationale in every section - Keep files under 200 lines each
Related Skills
validate-context
Validate .context/ files for quality, staleness, and conformance to the Substrate methodology. Run after making changes to documentation.
generate-tool-config
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.
add-adr
Create a new Architecture Decision Record in .context/decisions/. Use when documenting an architectural decision.
domain-driven-design
Plan and route Domain-Driven Design work from strategic modeling to tactical implementation and evented architecture patterns.
domain-driven-design
Plan and route Domain-Driven Design work from strategic modeling to tactical implementation and evented architecture patterns.
domain-name-brainstormer
Generates creative domain name ideas for your project and checks availability across multiple TLDs (.com, .io, .dev, .ai, etc.). Saves hours of brainstorming and manual checking.
railway-domain
Add, view, or remove domains for Railway services. Use when user wants to add a domain, generate a railway domain, check current domains, get the URL for a service, or remove a domain.
performing-subdomain-enumeration-with-subfinder
Enumerate subdomains of target domains using ProjectDiscovery's Subfinder passive reconnaissance tool to map the attack surface during security assessments.
hunting-for-domain-fronting-c2-traffic
Detect domain fronting C2 traffic by analyzing SNI vs HTTP Host header mismatches in proxy logs and TLS certificate discrepancies using pyOpenSSL for certificate inspection
conducting-domain-persistence-with-dcsync
Perform DCSync attacks to replicate Active Directory credentials and establish domain persistence by extracting KRBTGT, Domain Admin, and service account hashes for Golden Ticket creation.
analyzing-typosquatting-domains-with-dnstwist
Detect typosquatting, homograph phishing, and brand impersonation domains using dnstwist to generate domain permutations and identify registered lookalike domains targeting your organization.
Background jobs, domain events, and side effects
**When to use:** Queues and workers, domain event publishers, async notifications or projections, or **not** doing that work inside HTTP handlers.