domain-onboarding

Domain Onboarding — New Domain Setup Guide

You guide users through setting up a complete new domain in the architecture catalog. Every step follows the project's schema-driven approach — no hardcoded paths.

Process

Step 1: Understand the Schema

Read models/registry-mapping.yaml to discover:

• Available element types and their folders
• Which element type represents a "domain" (look for graph_rank: 0)
• Required fields for each type
• Available relationship types

Step 2: Gather Domain Information

Ask the user:

• Domain name (e.g., "Payment Processing")
• Domain slug — derive from name: lowercase, spaces → hyphens, & → and (e.g., "payment-processing")
• Key components — what logical components does this domain contain?
• Owner — who owns this domain?

Step 3: Create Domain Entry

1. Find the domain type's folder from registry-mapping.yaml
2. Read the _template.md in that folder
3. Create <domain-slug>.md with proper frontmatter
4. Fill known fields, use TBD for unknowns

Step 4: Create Initial Component Entries

For each key component the user mentioned:

1. Find the component type's folder from registry-mapping.yaml
2. Read the _template.md
3. Create <component-slug>.md with relationship back to the domain
4. Fill known fields, use TBD for unknowns

Step 5: Create Views Folder

mkdir -p views/<domain-slug>

Optionally create a docs.md with initial domain documentation.

Step 6: Create Domain Skill

Create .claude/skills/<domain-slug>-archi/SKILL.md following the /<domain>-archi naming pattern.

Use the existing /enterprise-platform-archi skill as a template — read it, then customize:

• Update name, description, domain keywords
• Update search scope paths
• Update domain knowledge table

Step 7: Create Domain Agent (Optional)

Create .claude/agents/<domain-slug>.md for auto-delegation.

Use the existing domain-expert.md as a template — read it, then customize:

• Update name, description, domain keywords
• Update to be read-only (tools: Read, Glob, Grep)