Social MediaHook Writingbeginner

Viral Community Discussion & High-Reply Engagement Catalyst

Craft compelling community prompts that spark hundreds of thoughtful peer discussions.

#social-media #community #discussion-starters #engagement #slack-communities

Compatibility & Specs

Compatible AI Models

ClaudeChatGPTGemini

Last UpdatedOct 3, 2026

Customizable Variables3 parameters

Main Prompt Template3 Variables

202 words • 1470 characters

You are a Community Architect and Online Engagement Strategist. Most community channels (Discord, Slack, Circle, Reddit) suffer from the 'lurker graveyard': people read silently, nobody posts, and admins post desperate questions like 'How is everyone's week going?' that receive zero replies. High-engagement prompts present safe, polarizing, or emotionally resonant professional dilemmas that compel people to weigh in. Community Domain & Member Demographics: [community_niche] Core Topic or Debate to Spark: [discussion_topic] Desired Community Vibe (Peer mentorship, technical debate, hilarious venting, or career advice): [community_vibe] Deliver the Community Discussion Catalyst Package: 1. 3 Calibrated Discussion Starters: - Option A (The Safe Polarizing Dilemma): A classic 'forced choice' debate where both sides have valid points (e.g., 'Tailwind vs Vanilla CSS', 'Monolith vs Microservices'). - Option B (The Vulnerable Failure Share): A prompt that normalizes admitting a mistake or imposter syndrome, inviting senior leaders to share war stories. - Option C (The Unpopular Truth / Hot Take): A provocative, respectfully framed contrarian question. 2. The 'Low-Barrier-to-Entry' First Post: The exact seeding comment the community manager should post immediately to break the ice and model the expected answer format. 3. Engagement Catalyst Rules: 2 psychological tactics to keep the conversation flowing across 48 hours without feeling forced.

Tip:Variables marked in purple brackets can be tailored below.

Customize Prompt

Fill in the variables below. Your customized prompt updates instantly in the browser — no AI API needed.

Parameters (3)* Indicates required field

Community Niche & Members*[community_niche]

Who is in this community

Core Topic to Spark*[discussion_topic]

The subject matter you want members discussing

Desired Community Vibe*[community_vibe]

Tone of the exchange

3 parameters active

Live Customized OutputLive Preview

245 words

You are a Community Architect and Online Engagement Strategist. Most community channels (Discord, Slack, Circle, Reddit) suffer from the 'lurker graveyard': people read silently, nobody posts, and admins post desperate questions like 'How is everyone's week going?' that receive zero replies. High-engagement prompts present safe, polarizing, or emotionally resonant professional dilemmas that compel people to weigh in. Community Domain & Member Demographics: A 3,000-member private community for Staff Software Engineers, Tech Leads, and Engineering Managers. Core Topic or Debate to Spark: The reality of AI coding assistants in production: Are they genuinely increasing delivery speed, or are they quietly generating massive technical debt? Desired Community Vibe (Peer mentorship, technical debate, hilarious venting, or career advice): Unfiltered engineering war stories, zero corporate PR hype, high technical honesty. Deliver the Community Discussion Catalyst Package: 1. 3 Calibrated Discussion Starters: - Option A (The Safe Polarizing Dilemma): A classic 'forced choice' debate where both sides have valid points (e.g., 'Tailwind vs Vanilla CSS', 'Monolith vs Microservices'). - Option B (The Vulnerable Failure Share): A prompt that normalizes admitting a mistake or imposter syndrome, inviting senior leaders to share war stories. - Option C (The Unpopular Truth / Hot Take): A provocative, respectfully framed contrarian question. 2. The 'Low-Barrier-to-Entry' First Post: The exact seeding comment the community manager should post immediately to break the ice and model the expected answer format. 3. Engagement Catalyst Rules: 2 psychological tactics to keep the conversation flowing across 48 hours without feeling forced.

Launch in:

ChatGPT Claude Gemini

How to Use This Prompt

Follow this 3-step workflow to extract high-signal responses from any compatible AI model.

1. Tailor the Parameters

Use the interactive customizer above to substitute the bracketed placeholders with your exact context, requirements, and constraints.

2. Send to AI Model

Copy the prompt and paste it into Claude, ChatGPT, Gemini, or Copilot. These models follow structured multi-step constraints reliably.

3. Review and Iterate

Review the output against the verified benchmark below. Follow up in the conversation to stress-test edge cases or refine tone.

Prompt Variables & Parameters

Reference breakdown of every dynamic variable embedded in this prompt template.

Placeholder	Parameter Name	Type	Status	Description & Guidance
[community_niche]	Community Niche & Members	text	Required	Who is in this communityDefault: A 3,000-member private community for Staff Software Engineers, Tech Leads, and Engineering Managers.
[discussion_topic]	Core Topic to Spark	text	Required	The subject matter you want members discussingDefault: The reality of AI coding assistants in production: Are they genuinely increasing delivery speed, or are they quietly generating massive technical debt?
[community_vibe]	Desired Community Vibe	text	Required	Tone of the exchangeDefault: Unfiltered engineering war stories, zero corporate PR hype, high technical honesty.

Example Execution & Benchmark Output

Sample input arguments and the verified AI response demonstrating expected quality and formatting.

Sample VariablesInputs

[community_niche]

A 3,000-member private community for Staff Software Engineers, Tech Leads, and Engineering Managers.

[discussion_topic]

The reality of AI coding assistants in production: Are they genuinely increasing delivery speed, or are they quietly generating massive technical debt?

[community_vibe]

Unfiltered engineering war stories, zero corporate PR hype, high technical honesty.

Expected AI ResponseVerified Result

### Community Discussion Catalyst Package #### 1. Three Calibrated Discussion Starters * **Option A: The 'Real Production War Story' (Vulnerable & Honest — Recommended)** > *'Let's have an honest check-in without LinkedIn hype.* > *For those of you running AI coding assistants (Copilot, Cursor, Claude) in active production codebases: What is the most subtle, terrifying bug an AI assistant has introduced into a PR that almost slipped past code review?* > *(I'll share mine first: Cursor hallucinated an obscure third-party API query parameter that silently defaulted to deleting user draft records on error instead of archiving them.)'* * **Option B: The Forced Trade-Off Dilemma** > *'Engineering leaders: If you were forced to choose right now between:* > *A) A junior engineer who uses Cursor to ship PRs 3x faster but struggles to explain the AST or memory model, OR* > *B) A junior engineer who refuses AI tools, codes manually at standard speed, but deeply understands underlying systems.* > *Who are you hiring in 2026 and why?'* #### 2. The Icebreaker Seeding Comment * The community manager must comment immediately after posting to remove the intimidation barrier: > *'My personal take: We saw initial PR volume spike 40% after rolling out Cursor, but our PR review turnaround time doubled because senior engineers spent twice as long auditing subtle edge-case hallucinations. Curious if others are seeing this review bottleneck?'*

Best Use Cases

Scenarios and roles where this prompt produces maximum leverage.

Community managers reviving quiet Slack and Discord professional groups

DevRel leads sparking lively, authentic technical debates on developer forums

Substack writers generating hundreds of high-quality subscriber comments

Tips for Best Results

Techniques to elevate response fidelity

•Provide rich background context rather than one-sentence inputs to receive deep, non-generic responses.
•Engage in multi-turn conversation: use the initial output as a baseline, then ask the AI to sharpen specific sections.
•Prompt the model to highlight any hidden assumptions or missing trade-offs in its recommendations.

Common Mistakes to Avoid

Frequent failure modes and anti-patterns

•Giving minimal context and expecting nuanced, expert-level strategic output.
•Not validating factual references, citations, or statistical claims with verified primary sources.
•Skipping the customization step and pasting raw bracketed template variables into the AI chat.