home / skills / bityoungjae / marketplace / domain-profiles

domain-profiles skill

needs review

This skill provides domain-specific configuration profiles for research and writing, guiding search strategies, terminology, and content structure across

npx playbooks add skill bityoungjae/marketplace --skill domain-profiles

Review the files below or copy the command above to add this skill to your agents.

Files (6)

SKILL.md

3.8 KB

---
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
user-invocable: false
---

# 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

| Profile    | File                           | Description                                    |
| ---------- | ------------------------------ | ---------------------------------------------- |
| Technology | [technology.md](technology.md) | Programming, frameworks, tools, APIs           |
| History    | [history.md](history.md)       | Historical events, periods, civilizations      |
| Science    | [science.md](science.md)       | Physics, chemistry, biology, mathematics       |
| Arts       | [arts.md](arts.md)             | Visual arts, music, performing arts            |
| General    | [language.md](language.md)     | General topics, linguistics, language learning |

**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:

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

**Domain to File Mapping**:

| Input Domain | File to Read |
|--------------|--------------|
| technology | technology.md |
| history | history.md |
| science | science.md |
| arts | arts.md |
| general | language.md |

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

### Agent-Specific Usage

| Agent | Sections to Extract |
|-------|---------------------|
| researcher | Search Strategy, Special Fields, Quality Indicators |
| research-collector | Search Strategy, Special Fields |
| writer | Content Structure, Terminology Policy |
| reviewer | Review Criteria (Critical Checks, Quality Checks, Style Checks) |

## Usage Example

```
# 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:

| Domain           | Typical Topics                         |
| ---------------- | -------------------------------------- |
| technology       | Python, React, Docker, API, 프로그래밍 |
| history          | 조선시대, 르네상스, 세계대전, 문명     |
| science          | 양자역학, 미적분, 세포생물학, 화학     |
| arts             | 유화, 작곡, 조각, 연기, 디자인         |
| language/general | 언어학, 글쓰기, 일반 교양              |

## Fallback Behavior

If domain is unclear or "general", use:

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

Overview

This skill provides domain-specific configuration profiles for creating learning resources across technology, history, science, arts, and general domains. It standardizes search strategies, domain metadata fields, terminology policies, and recommended content structures so researcher and writer agents behave appropriately for each subject area.

How this skill works

Agents load a profile file for the chosen domain and extract only the sections they need (search strategy, special fields, terminology policy, content structure, or review criteria). The skill maps input domain names to specific Markdown files and prescribes which sections each agent type should use. When domain is unclear or set to general, the language profile is used as a fallback.

When to use it

During research collection (Phase 2 of initialization) to drive domain-appropriate searches
When a researcher agent needs authoritative search patterns and source guidance
When a writer agent needs domain-adapted document structure and terminology rules
When assembling a persona or guidelines with domain-specific sections
When a reviewer agent needs targeted review criteria for quality and style checks

Best practices

Always load the profile via the standardized Read("skills/domain-profiles/{domain}.md") pattern
Map the input domain name to the exact file name (use language.md for general)
Extract only the sections relevant to the agent role to avoid information overload
Prefer authoritative sources and domain-specific search patterns listed in the profile
Use the terminology policy to decide when to define terms, translate, or cite

Example use cases

A researcher agent reads technology.md to generate API and framework search queries
A writer uses history.md content structure to build timelines, primary-source excerpts, and contextual analysis
A science curriculum author follows science.md special fields to collect formulas, units, and experiment safety notes
An arts educator applies arts.md pedagogy suggestions to structure technique lessons and portfolio prompts
A general educator loads language.md for broad-topic resource templates and language-focused guidance

FAQ

What file should I read for the general domain?

Use language.md; there is no general.md file. The language profile contains broadly applicable patterns.

Which sections should each agent extract?

Researchers: Search Strategy, Special Fields, Quality Indicators. Research-collectors: Search Strategy, Special Fields. Writers: Content Structure, Terminology Policy. Reviewers: Review Criteria.