Prompt library
Draft a newsletter issue readers finish
Leading the subject line with a payload instead of a theme is the highest-leverage open-rate fix. The cut-if-no-why-care rule keeps issues short and reader-centric, and the forwarding-colleague voice instruction reliably strips newsletter-brand mush from the draft.
Last reviewed July 17, 2026
The prompt
Draft a newsletter issue from the raw items below.
Audience and promise of the newsletter: {{premise}}
Raw items: {{items}}
Structure:
1. Subject line and preview text (under 50 and 90 characters): the issue's single most concrete payload, not a theme.
2. Opening: 2-3 sentences on the one item that matters most this issue, with your take. First sentence carries a fact.
3. 3-5 items. Each: a bold one-line takeaway, 2-3 sentences of context, and why the reader should care in their job. Cut any item you cannot give a why-care.
4. One short closing line that sets up the next issue or asks one specific question.
Voice: write like a sharp colleague forwarding links with opinions, not a brand. No greetings longer than one line.Run in idaptOpens a new chat with the prompt prefilled. Nothing sends until you press send.
Fill in the variables
| Variable | What it is | Example |
|---|---|---|
| {{premise}} | Who reads it and what it promises | indie game developers; practical production news |
| {{items}} | Links, notes, and half-thoughts to build from | [paste your raw links and notes for this issue] |