prompt-section-design

# Prompt Section Design Skill

Design composable prompt sections that work like LEGO blocks for building prompts at any level.

## Purpose

Create well-structured prompt sections that are reusable, consistent, and effective for the stakeholder trifecta.

## When to Use

- Creating a new prompt
- Restructuring existing prompt
- Adding sections to prompt
- Standardizing team prompts

## Section Tier List

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

## Design Process

### Step 1: Identify Prompt Purpose

Ask:

- What does this prompt accomplish?
- Who will use it? (you, team, agents)
- What level is it? (1-7)
- What inputs/outputs are needed?

### Step 2: Select Required Sections

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 |

### Step 3: Design Each Section

#### Metadata (Frontmatter)

```yaml
---
description: Clear, searchable description
argument-hint: [arg1] [arg2]
allowed-tools: Read, Write, Edit
model: sonnet
---
```

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

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