Skip to main content
Prompts Human LinkedIn Project Post Generator

general user marketing system risk: low

Human LinkedIn Project Post Generator

Instructs the model to ask 3–5 questions about the user's project before generating one main LinkedIn post and one alternative variation in a simple, human style following a strict…

PROMPT 

You will help me write LinkedIn posts that sound human, simple, and written from real experience — not corporate or robotic.

Before writing the post, you must ask me 3–5 short questions to understand:
1. What exactly I built
2. Why it matters
3. What problem it solves
4. Any specific result, struggle, or insight worth highlighting.
Do NOT generate the post before asking questions.

My Posting Style
Follow this strictly:
1. Use simple English (no complex words)
2. Keep sentences short
3. Write in short lines (mobile-friendly format)
4. Add spacing between lines for readability
5. Slightly professional tone (not casual, not corporate)
6. No fake hype, no “game-changing”, no “revolutionary”

Post Structure
Your post must follow this flow:

1. Hook (Curiosity-based)
   1.1. First 1–2 lines must create curiosity
   1.2. Make people want to click “see more”
   1.3. No generic hooks
2. Context
   2.1. What I built (${project:Project 1} or feature)
   2.2. Keep it clear and direct
3. Problem
   3.1. What real problem it solves
   3.2. Make it relatable
4. Insight / Build Journey (optional but preferred)
   4.1. A small struggle, realisation, or learning
   4.2. Keep it real, not dramatic
5. Outcome / Value
   5.1. What users can now do
   5.2. Why it matters
6. Soft Push (Product)
   6.1. Mention Snapify naturally
   6.2. No hard selling
7. Ending Line
   7.1. Can be reflective, forward-looking, or slightly thought-provoking
   7.2. No cliché endings

Rules
1. Keep total length tight (not too long)
2. No emojis unless they genuinely fit (default: avoid)
3. No corporate tone
4. No over-explaining
5. No buzzwords
6. No “I’m excited to announce”
7. No hashtags spam (max 3–5 if needed)

Your Task
After asking questions and getting answers, generate:
1. One main LinkedIn post
2. One alternative variation (slightly different hook + angle)

After generating both, ask:
“Which one should we post?”

INPUTS

project REQUIRED

name of the project or feature

e.g. Project 1

REQUIRED CONTEXT

  • answers to 3-5 questions on what was built, why it matters, problem solved, results/struggles/insights

ROLES & RULES

Role assignments

  • You will help me write LinkedIn posts that sound human, simple, and written from real experience — not corporate or robotic.
  1. Ask me 3–5 short questions to understand what was built, why it matters, what problem it solves, and any specific result, struggle, or insight.
  2. Do NOT generate the post before asking questions.
  3. Use simple English (no complex words)
  4. Keep sentences short
  5. Write in short lines (mobile-friendly format)
  6. Add spacing between lines for readability
  7. Slightly professional tone (not casual, not corporate)
  8. No fake hype, no “game-changing”, no “revolutionary”
  9. Keep total length tight (not too long)
  10. No emojis unless they genuinely fit (default: avoid)
  11. No corporate tone
  12. No over-explaining
  13. No buzzwords
  14. No “I’m excited to announce”
  15. No hashtags spam (max 3–5 if needed)
  16. After asking questions and getting answers, generate one main LinkedIn post and one alternative variation
  17. After generating both, ask “Which one should we post?”

EXPECTED OUTPUT

Format
markdown
Schema
markdown_sections · Hook, Context, Problem, Insight / Build Journey, Outcome / Value, Soft Push (Product), Ending Line
Constraints
  • follow exact post structure
  • simple English with short sentences and lines
  • one main post and one alternative variation
  • end with 'Which one should we post?'
  • no emojis unless they fit
  • tight length, no buzzwords or hype

SUCCESS CRITERIA

  • Posts must sound human, simple, and from real experience
  • Strictly follow posting style
  • Posts must follow the specified structure flow
  • Generate one main post and one alternative variation
  • Ask questions first before generating posts
  • End by asking which post to use

FAILURE MODES

  • Generating posts without first asking questions
  • Using complex words, buzzwords, or corporate tone
  • Including fake hype or hard selling
  • Posts too long or not mobile-friendly formatted
  • Ignoring post structure
  • Overusing emojis or hashtags

CAVEATS

Dependencies
  • User answers to the 3–5 questions
  • Project details such as ${project:Project 1}
Missing context
  • Exact word/character count for posts.
  • Examples of compliant posts.
  • What 'Snapify' is (assumed product name).
Ambiguities
  • 'Keep total length tight (not too long)' does not specify exact length.
  • 'No emojis unless they genuinely fit' is subjective.
  • Placeholder '${project:Project 1}' syntax may need clarification.

QUALITY

OVERALL
0.92
CLARITY
0.92
SPECIFICITY
0.95
REUSABILITY
0.90
COMPLETENESS
0.93

IMPROVEMENT SUGGESTIONS

  • Add 'Posts should be 150-250 words.' to Rules.
  • Include 1-2 full example posts after structure.
  • Clarify placeholder usage: 'Replace ${project} with the project name from answers.'
  • Specify 'Max 3 hashtags, relevant only.'

USAGE

Copy the prompt above and paste it into your AI of choice — Claude, ChatGPT, Gemini, or anywhere else you're working. Replace any placeholder sections with your own context, then ask for the output.

MORE FOR GENERAL USER