# Newsletter Issue Schema

Every issue follows this exact structure. Fill in each field. Nothing more, nothing less.

---

## Frontmatter (metadata)

```
issue: 001
date: Tuesday, January 1, 2026
subject: <50 chars — the email subject line. Make it the tip itself, not the topic name.
preview: <110 chars — preview text shown in inbox before opening.
type: Command | Config | Workflow | Agent | Debug
```

---

## Required fields (all must be present)

### `TIP_HEADLINE`
The technique name. Bold, specific, outcome-focused.
- Max 60 characters
- Format: `Verb + what + outcome`
- No questions, no ellipsis, no "how to"

### `TLDR`
Three bullets. Skim-reader's escape hatch.
- Each bullet: ~15 words, one concrete takeaway
- Should summarise the technique, not describe the issue structure

### `TIP_INTRO`
The hook. 2 sentences max.
- Sentence 1: The problem or cost (concrete, relatable)
- Sentence 2: What this issue delivers

### `TIP_BODY`
The technique itself. Required structure:
1. **THE SETUP** — 1 paragraph of context
2. Prompt teaser callout (if god-tier prompt included)
3. **THE TECHNIQUE** — 2-4 numbered steps
4. Code block (if applicable) — must be copy-paste runnable
5. **THE RESULT** — what changes, how much

Rules:
- Max 4 steps. If more, split into two issues.
- Every code block must be runnable as-is. No `YOUR_VALUE_HERE`, no `...`
- No "as you know", "obviously", "simply" — treat the reader as expert

### `DEEP_DIVE_TITLE`
Title of the curated external resource.

### `DEEP_DIVE_URL`
URL to the curated external resource. Must be HTTPS and not 404.

### `DEEP_DIVE_DESCRIPTION`
2 sentences max. Why this specific resource, why this specific week.

### `PROMPT`
Plain-English instruction for the god-tier prompt block.
30-80 words. The instruction that introduces the prompt, not the prompt itself.

### `PRO_TIP_HEADLINE`
The advanced technique name.
Must be different content from `TIP_HEADLINE`.

### `PRO_TIP_BODY`
The ceiling reader's bonus. 30-80 words.
Must introduce a concept NOT in TIP_BODY.

### `QUICK_WIN_HEADLINE`
Short, achievable action. Max 15 words.

### `QUICK_WIN_BODY`
Achievable in under 10 minutes. 25-70 words. Specific enough that the reader knows exactly what to do.

### `READ_THIS_WEEK`
Exactly 3 items. Each: link + 1-sentence description. Total 50-130 words.

### `NEXT_TEASE`
One sentence. Names the specific technique or topic coming next issue.
Max 20 words. Creates genuine curiosity without vague click-bait.

---

## Optional fields

### `budget_exception`
If any budget is intentionally exceeded: document here.
Format: `budget_exception: TIP_BODY exceeded 450 words — complex 4-step technique, no cut possible without losing correctness`

---

## Issue file structure

```markdown
---
issue: NNN
date: [day], [month] [DD], [YYYY]
subject: [subject line]
preview: [preview text]
type: [Command | Config | Workflow | Agent | Debug]
---

## TIP_HEADLINE

[headline text]

## TLDR

- [bullet 1]
- [bullet 2]
- [bullet 3]

## TIP_INTRO

[intro text]

## TIP_BODY

[body text — HTML allowed for the code callout blocks]

## DEEP_DIVE_TITLE

[title]

## DEEP_DIVE_URL

[url]

## DEEP_DIVE_DESCRIPTION

[description]

## PROMPT

[prompt instruction]

## PRO_TIP_HEADLINE

[pro tip headline]

## PRO_TIP_BODY

[pro tip body]

## QUICK_WIN_HEADLINE

[quick win headline]

## QUICK_WIN_BODY

[quick win body]

## READ_THIS_WEEK

[3 items]

## NEXT_TEASE

[one sentence]
```