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.

terminalclaudetrending_upRisingcontent_copyUsed 689 timesby Community

weekly-digestsubscriber-engagementSubstackemail-marketingnewslettercontent curationeditorial

claude

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

How to Write System Prompts That Actually Work

Article

person Admin•schedule 5 min read

How to Write System Prompts That Actually Work

System prompts set the rules of the game for every AI interaction. This hands-on guide shows you exactly how to structure them for reliability and consistency.

Claude vs GPT-4o: Which Model Fits Your Use Case?

Article

person Admin•schedule 5 min read

Claude vs GPT-4o: Which Model Fits Your Use Case?

Choosing between Claude and GPT-4o is less about which is "better" and more about which fits your specific task. Here is a practical breakdown.

How Our Design Team Cut Brief-Writing Time by 70% with AI

Article

person Admin•schedule 5 min read

How Our Design Team Cut Brief-Writing Time by 70% with AI

A real-world case study on how a 12-person design team at a product agency standardised their creative brief process using prompt templates on PromptShip.

Why AI Hallucinations Happen (and How to Reduce Them)

Article

person Admin•schedule 5 min read

Why AI Hallucinations Happen (and How to Reduce Them)

Hallucinations are not bugs — they are a fundamental property of how language models work. Understanding why they happen is the first step to minimising them.

The State of AI Coding Assistants in 2026

Article

person Admin•schedule 5 min read

The State of AI Coding Assistants in 2026

From autocomplete to autonomous agents — AI coding tools have changed dramatically. Here is where things stand and what to expect next.

From Idea to Shipped Prompt: A Solo Founder's AI Workflow

Article

person Admin•schedule 5 min read

From Idea to Shipped Prompt: A Solo Founder's AI Workflow

One founder. No team. A dozen AI-powered tools and a tight prompt library. Here is the workflow that runs a bootstrapped SaaS doing $15k MRR.

Recommended Prompts

claudeshieldTrusted

bookmark

Substack Newsletter Issue Writer

Crafts a fully written, high-retention Substack newsletter issue with a magnetic subject line, narrative arc, monetization hooks, and a shareable takeaway — ready to hit Send.

Newsletter Issue That Actually Gets Read

Drafts a crisp, value-dense newsletter with subject line, hook, and compounding structure.

Welcome / Onboarding Email Series Writer (First-Value-Anchored)

Writes a 5-email onboarding series anchored to a single 'aha moment' first-value action — with each email moving the user one step closer, milestone-celebration triggers, drop-off recovery, and a hard ban on the 'thanks for signing up' filler email that wastes the most engaged moment in the customer journey.

Twitter/X Thread Architect (Hook + 8-12 Body + CTA)

Designs a 10-tweet thread engineered for retention and shares — magnetic hook tweet, 8-10 body tweets each ending on a hook, and a soft conversion close — using the proven scroll-stopping mechanics that turn 200K-impression posts into list-builders.