Design composable prompt sections for building agentic prompts. Use when creating reusable prompt components, designing LEGO-block prompt sections, or structuring prompts for the stakeholder trifecta.
Limited to specific tools
Additional assets for this skill
This skill is limited to using the following tools:
Design composable prompt sections that work like LEGO blocks for building prompts at any level.
Create well-structured prompt sections that are reusable, consistent, and effective for the stakeholder trifecta.
| Tier | Sections | Priority |
|---|---|---|
| S | Workflow | Always include (Level 2+) |
| A | Variables, Examples, Control Flow, Delegation, Template | High value |
| B | Purpose, High-Level, Higher Order, Instructions | Supporting |
| C | Metadata, Codebase Structure, Relevant Files, Report | As needed |
Ask:
Based on level:
| Level | Required | Recommended |
|---|---|---|
| 1 | Title, Prompt | - |
| 2 | Title, Workflow | Variables, Report |
| 3 | Title, Workflow | Variables, Control Flow |
| 4 | Title, Workflow | Variables, Delegation |
| 5 | Title, Workflow | Variables |
| 6 | Title, Workflow, Template | Variables |
| 7 | Title, Workflow, Expertise | Variables |
---
description: Clear, searchable description
argument-hint: [arg1] [arg2]
allowed-tools: Read, Write, Edit
model: sonnet
---
```markdown
**Guidelines:**
- `description`: What does it do? When to use?
- `argument-hint`: What parameters expected?
- `allowed-tools`: Minimal set needed
- `model`: Match to task complexity
#### Title
```markdown
# Action-Oriented Title
```markdown
**Guidelines:**
- Use imperative verb: Create, Build, Generate, Analyze
- Be specific: "Create Implementation Plan" not "Plan"
- Keep concise: 2-5 words
#### Purpose
```markdown
## Purpose
[1-2 sentences describing what the prompt accomplishes]
```markdown
**Guidelines:**
- Direct language to agent
- Reference key sections
- Explain the "what" and "why"
#### Variables
```markdown
## Variables
# Dynamic (from user)
USER_PROMPT: $ARGUMENTS
FILE_PATH: $1
COUNT: $2 or 3 if not provided
# Static (fixed)
OUTPUT_DIR: specs/
MODEL: sonnet
```markdown
**Guidelines:**
- SCREAMING_SNAKE_CASE
- Dynamic first, static second
- Include defaults where appropriate
- Clear descriptions
#### Workflow (S-Tier)
```markdown
## Workflow
1. Validate inputs
- Check USER_PROMPT is provided
- If not, STOP and ask user
2. Process task
- Sub-step detail
3. Generate output
4. Report results
```markdown
**Guidelines:**
- Numbered steps for sequence
- Sub-bullets for details
- STOP conditions explicit
- Clear progression
#### Instructions
```markdown
## Instructions
- IMPORTANT: Always validate before processing
- Handle edge cases gracefully
- Never modify files outside project
```markdown
**Guidelines:**
- Bullet points for rules
- IMPORTANT markers for critical
- Edge cases explicit
#### Report
```markdown
## Report
## Task Complete
**Files:** [count]
**Status:** [status]
### Changes
- [change 1]
- [change 2]
```markdown
**Guidelines:**
- Template for output
- Consistent format
- Easy to parse
#### Template (Level 6)
```markdown
## Specified Format
```md
---
allowed-tools: <tools>
description: <description>
---
# <name>
## Variables
<VAR>: $1
## Workflow
<steps>
```markdown
**Guidelines:**
- Complete template
- Placeholders marked clearly
- Follows prompt conventions
#### Expertise (Level 7)
```markdown
## Expertise
### Domain Knowledge
- Pattern 1 learned
- Pattern 2 discovered
### Discovered Patterns
- Implementation insight 1
- Best practice 2
```yaml
**Guidelines:**
- Organized by category
- Grows over time
- Never modify Workflow
### Step 4: Validate Structure
Checklist:
- [ ] Title is action-oriented
- [ ] Workflow has numbered steps
- [ ] Variables use SCREAMING_SNAKE_CASE
- [ ] STOP conditions are explicit
- [ ] Frontmatter has description
- [ ] Sections in logical order
## Section Order Convention
```markdown
---
[frontmatter]
---
# [Title]
## Purpose
[purpose]
## Variables
[variables]
## Instructions
[instructions]
## Workflow
[workflow]
## Report
[report format]
```markdown
## Output Format
When designing sections:
```markdown
## Section Design
**Prompt:** [name]
**Level:** [1-7]
### Recommended Sections
1. **Title**: [suggested title]
2. **Frontmatter**:
```yaml
description: ...
argument-hint: ...
allowed-tools: ...
model: ...
```yaml
1. **Variables**:
- Dynamic: [list]
- Static: [list]
2. **Workflow**: [step count] steps
- Step 1: [overview]
- Step 2: [overview]
...
3. **Report**: [format type]
| Anti-Pattern | Problem | Solution |
|---|---|---|
| No Workflow section | Agent lacks direction | Always add for Level 2+ |
| Inconsistent variable names | Confusion | SCREAMING_SNAKE_CASE |
| Missing STOP conditions | Runaway execution | Explicit early exits |
| Over-detailed workflow | Reduces agent autonomy | High-level steps |
| No frontmatter | Hard to discover | Add description |
"Build libraries of reusable battle-tested agentic prompts with composable sections that work like LEGO blocks."