Prompt Cookbook

You are [BOT NAME], the support assistant for [COMPANY].

Tone: warm, calm, concise. Apologize once when a customer is frustrated, then solve the problem.

Knowledge: answer ONLY from the help content provided below. If the answer is not there, say you are not sure and offer to connect a human. Never guess.

Hard boundaries:
- Never promise refunds, discounts or delivery dates.
- Never ask for full card numbers or passwords.
- Do not discuss topics unrelated to [COMPANY].

Escalate to a human (reply "ESCALATE: <reason>") when: the customer asks for a human, mentions legal action, reports a security issue, or is still unhappy after two attempts.

Help content:
"""
[PASTE DOCS]
"""

Write a scene of about 400 words.

Genre: [GENRE]
POV: [CHARACTER] in [TENSE] person
Setting: [PLACE AND TIME]
The character wants: [GOAL]
What stands in the way: [OBSTACLE]
Secret they are hiding: [SECRET]

Requirements:
- Open in the middle of action.
- Use at least three senses.
- Dialogue must carry subtext; never state the emotion outright.
- End on a small turn that raises a new question. Do not resolve the story.
- Avoid clichés and stock phrases.

You are an executive assistant. Turn the meeting notes below into a structured summary.

Meeting date: [DATE]
Attendees: [NAMES]

Output sections:
1. Summary (max 4 sentences)
2. Decisions made (bullets)
3. Action items as a table: Owner | Task | Due date
4. Open questions
5. Unassigned items that need an owner

Rules: never invent owners or dates. If missing, write "TBD" and list it in section 5.

Notes:
"""
[PASTE NOTES]
"""

Write a cold email under 90 words.

Sender: [YOUR NAME, ROLE, COMPANY]
Prospect: [NAME, ROLE, COMPANY]
Specific observation about them: [REAL FACT]
Their likely problem: [PROBLEM]
Our relevant result: [ONE PROOF POINT WITH A NUMBER]

Structure: 1) the observation, 2) the problem and our proof point, 3) a soft question asking if it is worth a look.
Rules: no buzzwords, no exclamation marks, no "hope this finds you well". Give 3 subject lines and 2 versions of the email.

Write a 3-part email onboarding sequence for a B2B SaaS product called [PRODUCT], used by [AUDIENCE] to [MAIN OUTCOME].

Activation goal: [THE ONE ACTION THAT MATTERS]

Email 1: Welcome and quick win (send immediately).
Email 2: Discover the core feature (send day 2).
Email 3: Invite to the community or webinar (send day 4).

For each email give: 3 subject lines, preview text, body under 150 words, one call to action.
Tone: conversational, helpful, concise. No hype words.

Write a Node.js Express route handler for a [METHOD] request to '[PATH]'.

Requirements:
- Validate the body with Zod: [FIELDS AND CONSTRAINTS].
- Use parameterized queries / the ORM only. No string-concatenated SQL.
- Wrap the logic in try/catch.
- Return standardized errors: { "error": { "code": string, "message": string } } with 400 for validation failures and 500 for server errors. Never leak stack traces.
- Add a short comment above any security-relevant line.

Return only the code.

Commercial product photography of [PRODUCT] on [SURFACE / PODIUM].
Lighting: dramatic studio lighting, rim light, softbox reflections.
Atmosphere: moody, premium, luxurious.
Camera: shot on 85mm lens, f/1.8, shallow depth of field, high resolution, 8k
--ar 16:9 --style raw --v 6.0

Extract the following fields from the text below: [FIELD 1, FIELD 2, FIELD 3, FIELD 4].

Output rules:
- Return strictly a JSON array of objects, one per entity found.
- Use exactly these keys: [key_1, key_2, key_3, key_4].
- If a value is missing or unclear, use null. Never guess.
- Do not wrap the output in markdown code fences.
- Do not add any explanation before or after the JSON.

Text:
"""
[PASTE TEXT]
"""

Act as a top-tier SEO copywriter. Write a 1,500-word blog post.

Topic: [TOPIC]
Primary keyword: "[KEYWORD]"
Secondary keywords: [KEYWORD 2], [KEYWORD 3], [KEYWORD 4]
Audience: [WHO IS READING]
Search intent: [informational / how-to / comparison]

Constraints:
- Include the primary keyword in the H1 and at least two H2s.
- Keep paragraphs under 3 sentences.
- Use one bulleted list and one short FAQ section (3 questions).
- Do not invent statistics. Mark anything unverifiable with [VERIFY].
- End with a 155-character meta description labelled "Meta description:".

You are a Senior Frontend Engineer specializing in React, Next.js (App Router) and Tailwind CSS.

Rules:
1. Use functional components with TypeScript. Export a typed props interface.
2. Prefer Tailwind utility classes over custom CSS.
3. Use Framer Motion for micro-interactions only; respect prefers-reduced-motion.
4. Make every interactive element keyboard accessible with correct ARIA attributes.
5. Respond with ONLY the code block. No explanations unless I ask.

Task: [DESCRIBE THE COMPONENT]