Saves are the strongest signal LinkedIn has. They tell the algorithm someone wants to come back to your post later, which means you've earned the most expensive thing on the platform: a stranger's future attention.

These 17 prompts are built to engineer that. Every one of them produces a post format that historically over-indexes on save rate.

1. The named framework

What it does: Turns a process you already use into a named, memorable framework. Frameworks get saved because they're reusable. They get shared because attaching your name to one makes the sharer look smart.

The prompt:

`You're a LinkedIn ghostwriter for a [your role, e.g., B2B founder, agency owner, coach, fractional exec]. I'm going to describe a process I use to get [specific outcome]. Your job is to turn it into a named, memorable framework I can post.

Here's the process in plain language: [Write 3-7 steps you actually use. Don't dress it up. Just describe what you do.]

Audience: [your ICP in one line, e.g., "agency founders doing $30K-$200K MRR"]

Constraints:

• Framework name: 1-3 words, easy to say out loud. Aim for an acronym or a metaphor pulled from outside business (sports, cooking, construction, weather, anything). Avoid the words "method," "system," and "framework" in the name itself.
• Sentence case throughout. No emojis. No hashtags. No em dashes.
• Open with a hook that names a specific pain the ICP feels in their actual workday.
• Each step gets 2-3 lines maximum. Concrete actions, not abstract advice.
• Close with a punchline or a hard CTA. Not "what would you add?"

Output:

1. Three name options for the framework, with one-line rationale for each
2. The full LinkedIn post using your favorite of the three
3. A one-line caption I can use if I turn this into a carousel later`

Drop this in when: You've gotten a specific result for a client or yourself and the steps are replicable. The narrower the outcome, the harder this hits.

2. The save-worthy carousel

What it does: Takes one tight concept and breaks it into a 8-10 slide carousel. Carousels still over-perform on LinkedIn for save rate because they slow the scroll.

The prompt:

`You're a senior LinkedIn carousel writer. I want a 8-10 slide carousel breaking down [specific concept, e.g., "how to write a hook that gets clicks", "the 5 DM patterns I use to book calls"].

Context:

• Audience: [your ICP]
• My take/angle: [what's different about how I think about this. If you can say "common advice is X but I think Y," even better.]
• Proof points I have: [list any specific results, numbers, or examples you can pull from]

Constraints:

• Slide 1 is the hook. One line, max 8 words. No emojis. No "swipe to see."
• Slides 2-9 each have a one-line headline plus 2-3 lines of body. Headlines do the work; body is supporting evidence.
• Slide 10 is the CTA. Pick one: follow for more, comment a keyword, or DM me a word. Not all three.
• Sentence case. No hashtags. No em dashes. Short sentences only.
• No AI-sounding lines like "let's dive in," "here's why this matters," or "the truth is."

Output:

1. The 10 slides as a numbered list, each with [HEADLINE] and [BODY] clearly marked
2. A 3-line caption to post alongside the carousel
3. The hook line rewritten three different ways for A/B testing`

Drop this in when: You have a teaching moment or a counterintuitive take. Carousels reward depth, not breadth.

3. The swipe file post

What it does: Drops a list of templates, scripts, or examples in one post. Save rate spikes because the post itself becomes the resource.

The prompt:

`You're writing a LinkedIn post that functions as a swipe file. The post should give the reader [number, usually 5-10] copyable templates or examples for [specific use case, e.g., "DM openers that don't feel salesy", "cold email subject lines for SaaS demos"].

What I'll give you:

• The use case: [one line]
• My voice rules: [what all examples should follow, e.g., "no buzzwords," "under 15 words," "must be question-based"]
• Audience: [your ICP]
• Real examples I've used or seen work: [list 2-3 if you have them. helps the model match flavor.]

Constraints:

• Post structure: hook line, one-line setup, numbered list of templates, closing line.
• Each template must be copy-pasteable as-is. No "[insert name here]" placeholders unless the placeholder is the point.
• Every template is different in structure, not just wording. If two feel similar, replace one.
• Sentence case. No hashtags. No emojis at the start of lines. No em dashes.
• Closing line: a punchline or a "save this for later" nudge. Not a question.

Output:

1. The full post
2. A short alt-version of the hook`

Drop this in when: You want a guaranteed-save post and you have actual examples that work. This format dies if the templates are mid.