---
name: newsletter-layout-planner
description: "A one-issue newsletter plan covering section order, visual hierarchy, image placement, column width, headline length, and the send rhythm, with a summary table and content ideas per section. Use when one newsletter issue needs a full plan: section order, visual hierarchy, image and column guidelines, headline length, and send timing matched to how often it goes out. Do not use for a quick heading-and-column outline for a template or a critique of a sent newsletter. Related topics: marketing, business, newsletter."
---

# Newsletter Layout Planner

A one-issue newsletter plan covering section order, visual hierarchy, image placement, column width, headline length, and the send rhythm, with a summary table and content ideas per section.

## When to use

Use this skill when one newsletter issue needs a full plan: section order, visual hierarchy, image and column guidelines, headline length, and send timing matched to how often it goes out. Do not use it for a quick heading-and-column outline for a template or a critique of a sent newsletter.

## Workflow

1. Ask the user for each input listed below in a single message, skipping any they have already given. Where options are listed, offer them, but accept other answers too.
2. Order the selected sections so the highest-value item is above the fold and the primary call to action appears early and at the end.
3. Define the visual hierarchy: what is largest, what is second, and what recedes.
4. Set practical guidelines: 600px container, an image position per section, and a headline length for mobile.
5. Match the reading load to the issue frequency and propose a send day and time as a hypothesis to test.
6. Return the heading, the summary table, and a bullet list of content ideas for each section.

## Inputs

- **Target audience** (longer free text)
- **Newsletter type** (choose one: Product update, Event invitation, Blog digest, Internal memo, Promotional offer)
- **Issue frequency** (choose one: Weekly, Bi-weekly, Monthly, Quarterly)
- **Key sections to include** (choose any: Headline, Featured article, Quick tips, Customer spotlight, Upcoming events, Survey)
- **Visual style preference** (choose one: Minimalist, Bold colors, Classic, Modern, Brand-aligned)
- **Primary call-to-action** (free text, e.g. "Register or Buy now or Read more")

## Output

A markdown document with a heading, a summary table of type, frequency, style, CTA, and send timing, and a bullet list of recommended content per section.

## Prompt template

Fill the inputs into this template and follow it as the full instruction.

### Newsletter Layout Planner

Plan one full issue of a newsletter, including how often it should go out.

- Target audience: {{Target audience}}
- Newsletter type: {{Newsletter type}}
- Issue frequency: {{Issue frequency}}
- Key sections to include: {{Key sections to include}}
- Visual style preference: {{Visual style preference}}
- Primary call-to-action: {{Primary call-to-action}}

Treat the issue as a reading journey. Decide the order of the selected sections so that the most valuable item sits above the fold and the primary call to action appears twice, once early and once at the end. Set the visual hierarchy explicitly: what is largest, what is second, and what recedes. Give practical guidelines: a 600px container width, an image placement for each section, and a headline length (under 50 characters suits mobile). Tune the plan to the frequency: a quarterly issue can carry more content and a longer read, a weekly issue must be scannable in under two minutes. Suggest the best send day and time for the audience as a hypothesis to test.

Return a markdown document with a heading, a table summarising the choices (type, frequency, style, CTA, send timing), and a bullet list of recommended content for each section.

## Pitfalls

- Putting the call to action only at the bottom, where scrolling readers never reach it.
- Planning a long weekly issue that cannot be scanned in a couple of minutes.
- Presenting a send time as a fact when it needs testing with the audience.
