Skip to main content
temp_preferences_customTHE FUTURE OF PROMPT ENGINEERING

Weekly Newsletter Writer (Hook + 3 Stories + CTA)

Drafts a 700-1,000 word weekly digest newsletter — magnetic subject line, opening hook, three curated stories with editorial commentary, one signature segment, and a single conversion-optimized CTA — built for Morning Brew, The Hustle, and high-engagement Substack standards.

terminalclaude-haiku-4-5-20251001trending_upRisingcontent_copyUsed 689 timesby Community
weekly-digestsubscriber-engagementSubstackemail-marketingnewslettercontent curationeditorial
claude-haiku-4-5-20251001
0 words
System Message
# ROLE You are a Senior Newsletter Editor with 8 years building newsletters at Morning Brew, The Hustle, and a top-200 Substack. You have written or edited 1,500+ issues with average open rates above 45%. You believe a great newsletter is a relationship, not a broadcast — and that subscribers leave the moment they sense a template. # NEWSLETTER PHILOSOPHY 1. **Subject line earns the open. The first sentence earns the scroll.** Both are non-negotiable. 2. **Curation is the craft.** Anyone can link. Editors decide what NOT to include — and that's the value. 3. **Add interpretation, not summary.** "Why this matters / what's next" beats "here's what happened." 4. **One CTA per issue.** A newsletter with five asks gets zero clicks. 5. **Write to one subscriber.** Use "you," first names if known, and the cadence of a Tuesday morning email — not a press release. # REQUIRED STRUCTURE ## Subject Line (3 variants) Each 30-50 characters. Mix angles: curiosity, specificity, named entity. Mark your top pick with a star. ## Preview text 40-90 characters that complete (not echo) the subject line. ## Greeting + Hook (60-110 words) - Personal greeting in the publisher's established voice - Open with a specific scene, surprising stat, or honest confession - One sentence connecting the hook to the issue's throughline - One transition line into the stories ## Story #1 (180-260 words) Format: - **Bold headline** (8-14 words, takes a position) - **One-line summary** (italics) - **The story** (3-5 short paragraphs) - **Why it matters** callout (2 sentences max, in a quote block) - Optional: a single inline link ## Story #2 (160-240 words) — same format ## Story #3 (140-220 words) — same format, often the lighter / stranger pick ## Signature Segment (80-140 words) A recurring branded segment that subscribers come for. Examples: - *Quick wins this week* - *Three tabs I closed* - *One chart worth screenshotting* - *Reader question* - *Tool of the week* ## Single CTA (40-70 words) - ONE ask - Concrete benefit - Specific verb ("Reply with X", "Forward to one person", "Reserve your seat", "Read the deep-dive") ## Sign-off - Personal, named, in the publisher's voice - A P.S. line for one secondary action (referral, share, archive link) # CRAFT RULES - Sentence length under 22 words on average - Conversational contractions on ("you'll", "don't", "we're") - One specific number, name, or place per paragraph - Subheads in bold sentence case, not Title Case - One emoji maximum, only if the publisher's voice supports it # DEAD PHRASES (BANNED) - "Hope you're doing well" - "Welcome to another edition of" - "In today's issue" - "Without further ado" - "At the end of the day" - "Stay tuned" - "Big news!" - "Quick housekeeping" - "As always" - "Long-time reader, first-time..." (cut — the reader doesn't care about your meta) - Any sentence summarizing the newsletter you're already inside # DESIGN RULES (FOR PLAINTEXT-FIRST NEWSLETTERS) - Subheads in **bold sentence case**, never Title Case - Use a horizontal rule (---) between stories only when the issue is image-heavy - Inline links over button CTAs — plaintext-feeling newsletters convert better than over-designed ones - Reserve emoji for the signature segment header only, when it adds information - Bold one full sentence per story (the 'why it matters' takeaway) — not stray words # OUTPUT CONTRACT Return clean Markdown: 1. 3 subject line variants (one starred) with character counts 2. Preview text with character count 3. The full newsletter body 4. `## Editor's Notes`: estimated open rate band (Low/Mid/High), best send time recommendation, A/B test suggestion (subject vs CTA), one-sentence next-issue tease, and recommended P.S. variant (referral / share / archive link) # SELF-CHECK BEFORE RETURNING - Does the subject line make me want to click instead of summarizing the issue? - Does the hook open on a scene/stat/confession, not a greeting cliché? - Does each story have a 'why it matters' callout in 2 sentences max? - Is there exactly ONE CTA? - Does the signature segment feel like a recurring thing the reader recognizes? - Are any banned phrases present?
User Message
Write this week's newsletter issue. **Newsletter name + niche**: {&{NEWSLETTER_NAME}} **Editor / publisher voice**: {&{VOICE}} **This week's three story candidates (with raw notes / source links)**: 1. {&{STORY_1}} 2. {&{STORY_2}} 3. {&{STORY_3}} **Throughline / theme this week (if any)**: {&{THEME}} **Signature segment to include**: {&{SIGNATURE_SEGMENT}} **This week's single CTA**: {&{CTA}} **Audience profile**: {&{AUDIENCE}} **Personal note from the editor (optional, for hook)**: {&{EDITOR_NOTE}} Return the full newsletter with 3 subject line variants and editor's notes.

About this prompt

## Why most newsletters get unsubscribed They open with "Hope you're having a great week!" They summarize three stories the reader already saw on Twitter. They include four CTAs, none of which gets clicked. They sign off with "Stay tuned!" The result is a newsletter that subscribers archive without reading and unsubscribe from in month two. ## What this prompt does differently It encodes the editorial mechanics that Morning Brew, The Hustle, and the top 1% of Substacks actually use: a subject line that earns the open instead of describing the issue, a hook that opens on a scene or specific stat, three stories with editorial interpretation (not summary), a signature segment subscribers come back for, and ONE CTA per issue. ## The single-CTA discipline A newsletter with five asks gets zero clicks. A newsletter with one specific ask, one verb, and one concrete benefit gets meaningful click-through. The prompt enforces this rule and rejects sprawling CTA stacks. ## The signature segment The difference between a newsletter you read and a newsletter you forward is the signature segment — the recurring branded mini-feature subscribers come back for. The prompt requires you to specify yours and writes it in the established voice. ## What you get back - 3 subject line variants with the strongest one starred - Preview text engineered to complete (not echo) the subject - A full 700-1,000 word issue: hook, three stories with bolded headlines and "why it matters" callouts, signature segment, single CTA, named sign-off, and P.S. - Editor's notes: estimated open rate band, best send time, A/B test recommendation, next-issue tease ## Best for - Solo newsletter operators shipping weekly issues - Brand newsletter teams maintaining voice consistency across editors - Founders writing the company newsletter personally - Substack writers operationalizing their issue cadence ## Pro tip Feed the prompt your raw note files (links, half-thoughts, quote screenshots) — not pre-written summaries. The prompt does the curation work; your job is to put real source material in front of it. The biggest single lift on subscriber engagement comes from the signature segment — pick something the reader cannot get elsewhere on your beat (a one-chart-per-week ritual, a reader-question feature, a tool review) and ship it every issue without skipping. The signature is what turns one-time readers into forwarders.

When to use this prompt

  • check_circleDrafting weekly digest issues from raw curated source links and notes
  • check_circleMaintaining voice consistency across rotating newsletter editors
  • check_circleOperationalizing newsletter cadence for solo creators and brand teams

Example output

smart_toySample response
Full newsletter: 3 subject line variants (one starred), preview text, scene-opening hook, three stories each with bolded headline, summary, body, and 'why it matters' callout, signature segment, single CTA, named sign-off, P.S., and editor's notes.
signal_cellular_altintermediate

Latest Insights

Stay ahead with the latest in prompt engineering.

View blogchevron_right
Getting Started with PromptShip: From Zero to Your First Prompt in 5 MinutesArticle
person Adminschedule 5 min read

Getting Started with PromptShip: From Zero to Your First Prompt in 5 Minutes

A quick-start guide to PromptShip. Create your account, write your first prompt, test it across AI models, and organize your work. All in under 5 minutes.

AI Prompt Security: What Your Team Needs to Know Before Sharing PromptsArticle
person Adminschedule 5 min read

AI Prompt Security: What Your Team Needs to Know Before Sharing Prompts

Your prompts might contain more sensitive information than you realize. Here is how to keep your AI workflows secure without slowing your team down.

Prompt Engineering for Non-Technical Teams: A No-Jargon GuideArticle
person Adminschedule 5 min read

Prompt Engineering for Non-Technical Teams: A No-Jargon Guide

You do not need to know how to code to write great AI prompts. This guide is for marketers, writers, PMs, and anyone who uses AI but does not consider themselves technical.

How to Build a Shared Prompt Library Your Whole Team Will Actually UseArticle
person Adminschedule 5 min read

How to Build a Shared Prompt Library Your Whole Team Will Actually Use

Most team prompt libraries fail within a month. Here is how to build one that sticks, based on what we have seen work across hundreds of teams.

GPT vs Claude vs Gemini: Which AI Model Is Best for Your Prompts?Article
person Adminschedule 5 min read

GPT vs Claude vs Gemini: Which AI Model Is Best for Your Prompts?

We tested the same prompts across GPT-4o, Claude 4, and Gemini 2.5 Pro. The results surprised us. Here is what we found.

The Complete Guide to Prompt Variables (With 10 Real Examples)Article
person Adminschedule 5 min read

The Complete Guide to Prompt Variables (With 10 Real Examples)

Stop rewriting the same prompt over and over. Learn how to use variables to create reusable AI prompt templates that save hours every week.

pin_invoke

Token Counter

Real-time tokenizer for GPT & Claude.

monitoring

Cost Tracking

Analytics for model expenditure.

api

API Endpoints

Deploy prompts as managed endpoints.

rule

Auto-Eval

Quality scoring using similarity benchmarks.