domain-expertise-template
Template for creating domain expertise skills. Copy and customize for your specific domain.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
메뉴
Template for creating domain expertise skills. Copy and customize for your specific domain.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
An example skill demonstrating the basic structure. Use when user asks about examples or templates.
Use when reviewing code, PRs, or discussing code quality standards. Applies team coding standards and review methodology.
Use when reviewing code, PRs, or discussing code quality standards. Applies team coding standards and review methodology.
| name | domain-expertise-template |
| description | Template for creating domain expertise skills. Copy and customize for your specific domain. |
Copy this template to create your own domain expertise skill.
~/.claude/skills/your-domain/SKILL.md[PLACEHOLDER] text with your content---
name: [your-skill-name]
description: Use when [trigger conditions]. Applies [your methodology/framework] for [outcome].
---
<framework_overview>
## What This Is
[One paragraph describing what this expertise covers and why it matters]
## When to Use
- [Trigger situation 1]
- [Trigger situation 2]
- [Trigger situation 3]
## Key Terms
| Term | Definition |
|------|------------|
| [Term 1] | [Definition] |
| [Term 2] | [Definition] |
</framework_overview>
<principles>
## Core Philosophy
### 1. [PRINCIPLE NAME IN CAPS]
[2-3 sentences explaining this principle and why it matters]
Example:
- Good: [example of applying this principle well]
- Bad: [example of violating this principle]
### 2. [PRINCIPLE NAME IN CAPS]
[2-3 sentences explaining this principle and why it matters]
Example:
- Good: [example]
- Bad: [example]
### 3. [PRINCIPLE NAME IN CAPS]
[2-3 sentences explaining this principle and why it matters]
Example:
- Good: [example]
- Bad: [example]
</principles>
<process>
## The Process
### Step 1: [Name]
**Purpose**: [Why this step matters]
**Actions**:
- [Action 1]
- [Action 2]
**Output**: [What this step produces]
### Step 2: [Name]
**Purpose**: [Why this step matters]
**Actions**:
- [Action 1]
- [Action 2]
**Output**: [What this step produces]
### Step 3: [Name]
**Purpose**: [Why this step matters]
**Actions**:
- [Action 1]
- [Action 2]
**Output**: [What this step produces]
</process>
<templates>
## Output Templates
### [Template Name 1]
```markdown
# [Document Title]
## Section 1
[What goes here]
## Section 2
[What goes here]
## Section 3
[What goes here]
[Another template if needed]
## Common MistakesWhat it looks like: [Description of the mistake] Why it's wrong: [Consequences] Instead: [Correct approach]
What it looks like: [Description] Why it's wrong: [Consequences] Instead: [Correct approach]
What it looks like: [Description] Why it's wrong: [Consequences] Instead: [Correct approach]
Before I help with [domain], I need to understand:[Question about scope]
[Question about context] [Open-ended question]
[Question about constraints] [Open-ended question]
Any specific concerns or requirements?
I'll wait for your answers before proceeding.
---
## Customization Checklist
- [ ] Updated skill name and description
- [ ] Added 3+ principles with examples
- [ ] Added 3+ process steps
- [ ] Created output templates
- [ ] Added 2+ anti-patterns
- [ ] Created intake questions
- [ ] Tested skill triggers correctly