domain-expertise-template
Template for creating domain expertise skills. Copy and customize for your specific domain.
Full skill instructions
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] </templates>
<anti-patterns> ## 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] </anti-patterns>
<intake> 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. </intake>
---
## 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
Comprehensive document creation, editing, and analysis with support for tracked changes, comments, formatting preservation, and text extraction. When Claude needs to work with professional documents (.docx files) for: (1) Creating new documents, (2) Modifying or editing content, (3) Working with tracked changes, (4) Adding comments, or any other document tasks
This handles everything around building autonomous agents for Claude Code plugins.
Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.
This is the meta-skill for building skills themselves.
Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
Helps you build event-driven automation for Claude Code using hooks that trigger on tool use, session events, and stop conditions.
Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.
Shows Claude Code how to build slash commands from markdown files, covering the YAML frontmatter options, dynamic arguments with $1/$2...
This is your reference when scaffolding Claude Code plugins or figuring out why components aren't loading.
Install Codex skills into $CODEX_HOME/skills from a curated list or a GitHub repo path. Use when a user asks to list installable skills, install a curated skill, or install a skill from another repo (including private repos).
Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn/ui). Use for complex artifacts requiring state management, routing, or shadcn/ui components - not for simple single-file HTML/JSX artifacts.
Generate, edit, and beat-sync AI video with leading models in one workspace.
The world's fastest calendar for remote work
Transform Your Design with AI Designer by ImgCreator.ai
Revolutionizing Video Production with AI-Powered Creativity
Extend an image past the frame and let AI fill the new aspect ratio.
Discover your celebrity doppelgänger with StarByFace!
ChainClarity explains 700+ crypto whitepapers in plain English, with layered summaries, comparisons, research tools, alerts, and a $4.99 Pro plan.
Opus.ai: Revolutionize Your Web Experience