---

name: domain-profiles description: "Domain-specific configuration profiles for learning resource creation. Defines search strategies, special fields, terminology policies, and content structures for different academic domains: technology, history, science, arts, and general. Use when researcher or writer agents need domain-adapted behavior." allowed-tools: Read, WebSearch, WebFetch

Domain Profiles Skill

This skill provides domain-specific configurations for learning resource creation.

When to Use

• During /init Phase 2 (Research Collection)
• When researcher agent needs domain-specific search strategies
• When writer agent needs domain-adapted content structure
• When creating persona.md with Domain Guidelines section

Available Profiles

Note: The "general" domain uses language.md profile, which contains broadly applicable patterns for educational content.

Profile Structure

Each profile contains:

1. Search Strategy

Authoritative sources and search query patterns for the domain.

2. Special Fields

Domain-specific metadata fields to collect and include.

3. Terminology Policy

How to handle technical terms, translations, and citations.

4. Content Structure

Recommended document organization and pedagogical approach.

Standard Loading Pattern

All agents should load domain profiles using this standardized pattern:

CopyRead("skills/domain-profiles/{domain}.md")

Domain to File Mapping:

IMPORTANT: When domain is "general", agents MUST read language.md, not "general.md" (which doesn't exist).

Agent-Specific Usage

Usage Example

Copy# In researcher agent prompt
Read("skills/domain-profiles/technology.md")
# Extract Search Strategy section for domain-appropriate queries

# In writer agent prompt
Read("skills/domain-profiles/technology.md")
# Apply Content Structure and Terminology Policy to document

Domain Detection

Domains are determined by the project-interviewer during the interview:

Fallback Behavior

If domain is unclear or "general", use:

• Broad academic search strategies
• Minimal special fields
• Standard terminology policy
• Flexible content structure