Prompt library

Act as a senior content strategist writing for an audience of {{audience}}.
Write a search-optimised blog post about: {{topic}}

Requirements:
- Compelling title (max 60 characters) plus a 1-sentence meta description (max 155 characters)
- Hook in the first 2 sentences, no generic "In today's world" openings
- 4-6 H2 sections with skimmable sub-points
- Include one concrete example or mini case per section
- Close with a clear call to action
Tone: {{tone}}. Length: {{length}}. Output clean markdown.

You are a specialist writer for {{audience}}.
Create a numbered roundup article on: {{topic}}

Rules:
- 7 items, each with a bold title, 2-3 sentences of substance and a "Why it matters" line
- No filler items, no repeated ideas
- Add a short intro (max 60 words) and a summary table at the end
Tone: {{tone}}. Length: {{length}}. Output markdown.

Write a LinkedIn post for {{audience}} about: {{topic}}

Constraints:
- First line is a scroll-stopping hook under 12 words
- One central insight, supported by a specific personal-style example
- Line breaks every 1-2 sentences for readability
- End with an open question to drive comments
- No hashtags spam: max 3 relevant hashtags
Tone: {{tone}}. Length: {{length}}.

You are an outreach specialist emailing {{audience}}.
Write a cold email about: {{topic}}

Rules:
- 3 subject line options (under 45 characters each)
- Body under 120 words, one idea, no buzzwords
- Open with a specific observation about the recipient, not about us
- One measurable benefit, one soft call to action (a question, not a demo demand)
- Plain-text friendly, no emojis
Tone: {{tone}}. Length: {{length}}.

Write a 3-email follow-up sequence to {{audience}} regarding: {{topic}}

For each email give: send delay, subject line, body (max 90 words).
- Email 1: add new value (insight, resource), do not "just check in"
- Email 2: address the most likely objection
- Email 3: polite break-up email leaving the door open
Tone: {{tone}}. Length: {{length}}.

You are a customer support lead replying to {{audience}}.
Situation: {{topic}}

Write a reply that:
- Acknowledges the specific issue in the first line (no templated apology wall)
- Explains what happened in plain language
- Gives numbered next steps with owner and timeline
- Offers one goodwill gesture if appropriate
- Ends with a direct contact route
Tone: {{tone}}. Length: {{length}}.

You are a senior engineer writing production code for {{audience}}.
Task: {{topic}}

Deliver:
- One clean, runnable code block (state the language)
- Inline comments only where logic is non-obvious
- Edge cases handled explicitly
- A short usage example
- A note on time/space complexity or performance trade-offs where relevant
Tone: {{tone}}. Length: {{length}}.

Act as a staff engineer reviewing code for {{audience}}.
Code / context: {{topic}}

Output:
1. Summary verdict (2 sentences)
2. Findings table: issue | severity (high/medium/low) | fix
3. Refactored version of the code
4. Tests you would add
Be specific, cite line-level reasoning. Tone: {{tone}}. Length: {{length}}.

Write technical documentation for {{audience}} covering: {{topic}}

Structure:
- What it does (3 sentences)
- Installation
- Quick start with a copy-paste example
- API reference table: name | type | default | description
- Common pitfalls
Use markdown, no marketing language. Tone: {{tone}}. Length: {{length}}.