Appendix A: Prompt Templates Library (Quick-Reference)

These templates are designed to be copied, adapted, and reused. Replace all [VARIABLE] placeholders with your specific content. Each template has been structured to produce consistently useful outputs across the major AI chat platforms.

Section 1: Writing and Editing Templates

1.1 Blog Post First Draft

Write a blog post on the topic: [TOPIC].

Target audience: [AUDIENCE — e.g., "small business owners with no technical background"]
Desired length: approximately [WORD COUNT] words
Tone: [TONE — e.g., conversational, authoritative, encouraging]
Key points to cover:
1. [POINT 1]
2. [POINT 2]
3. [POINT 3]

Include a compelling headline and a call-to-action at the end that encourages readers to [DESIRED ACTION].
Do not include generic filler phrases like "In today's fast-paced world" or "In conclusion."

1.2 Executive Summary

Write an executive summary of the following document or content.

Content to summarize:
[PASTE DOCUMENT OR DESCRIPTION OF CONTENT]

The executive summary should be [LENGTH — e.g., "no more than 300 words"] and should address:
- The core problem or opportunity being described
- The recommended action or key finding
- Supporting rationale (2-3 main points)
- Any critical risks or dependencies

The audience is [AUDIENCE — e.g., "senior leadership with limited technical knowledge"]. Avoid jargon. Be direct.

1.3 Email Draft — Formal

Draft a formal professional email with the following details:

From: [SENDER NAME / ROLE]
To: [RECIPIENT NAME / ROLE]
Purpose: [ONE SENTENCE PURPOSE — e.g., "request a budget extension for the Q3 project"]
Key information to include:
- [DETAIL 1]
- [DETAIL 2]
- [DETAIL 3]
Desired response from recipient: [WHAT YOU WANT THEM TO DO]
Tone: formal, respectful, clear

Keep the email concise — no longer than [LENGTH] paragraphs.

1.4 Email Draft — Informal / Internal

Write an informal email to a colleague with the following purpose:
[PURPOSE — e.g., "check in on the status of a delayed deliverable without sounding accusatory"]

Context: [BRIEF BACKGROUND]
Key asks or updates to include:
- [ITEM 1]
- [ITEM 2]

Tone: friendly, direct, not overly formal. We work closely together and have a good relationship.

1.5 Email Draft — Difficult Conversation

Help me write an email to address a sensitive situation at work.

Situation: [DESCRIBE THE SITUATION — e.g., "a team member has repeatedly missed deadlines and I need to address it without damaging the relationship"]
My role: [YOUR ROLE]
Recipient's role: [THEIR ROLE]
Goal: [WHAT OUTCOME YOU WANT]
Constraints: [ANYTHING TO AVOID — e.g., "do not sound accusatory; do not make it feel like a formal warning"]

Draft an email that is direct but empathetic. Include a clear path forward.

1.6 Editing and Proofreading Request

Please edit the following text for [TYPE OF EDIT — choose one or more]:
- Grammar and spelling
- Clarity and concision
- Flow and transitions
- Tone consistency
- Factual plausibility (flag anything that seems questionable)

Preserve my original voice and structure. If you make significant changes, briefly explain why.

Text to edit:
[PASTE TEXT]

1.7 Tone Adaptation — Make Formal

Rewrite the following text in a more formal, professional tone suitable for [CONTEXT — e.g., "a published report" or "a board presentation"].

Do not change the factual content. Maintain all key points. Eliminate casual language, contractions, and colloquialisms.

Original text:
[PASTE TEXT]

1.8 Tone Adaptation — Make Casual / Conversational

Rewrite the following in a more casual, conversational tone suitable for [CONTEXT — e.g., "a blog post aimed at young professionals" or "an internal team Slack message"].

Keep all the main ideas intact. Add natural-sounding language and make it feel like a knowledgeable friend is explaining it.

Original text:
[PASTE TEXT]

1.9 Tone Adaptation — Simplify

Rewrite the following text so it is easy to understand for someone with no background in [FIELD/TOPIC].

Target reading level: approximately [GRADE LEVEL / DESCRIPTION — e.g., "8th grade" or "a curious non-specialist"].
Replace technical jargon with plain language. Use short sentences. Add brief explanations where helpful.

Original text:
[PASTE TEXT]

1.10 Style Matching

I want you to write in the style of the example below. Analyze the tone, sentence length, vocabulary level, use of humor, and structural patterns.

Style example:
[PASTE 2-3 PARAGRAPHS OF WRITING IN TARGET STYLE]

Now write [CONTENT DESCRIPTION — e.g., "a 300-word introduction to a chapter on decision-making"] in the same style.
Topic: [TOPIC]
Key points to cover: [POINTS]

Section 2: Research and Analysis Templates

2.1 Topic Orientation / Landscape Overview

Give me an orientation to the topic of [TOPIC].

I am [YOUR BACKGROUND — e.g., "a product manager with no prior knowledge of this field"]. I need to understand:
1. What this topic is and why it matters
2. The key concepts and vocabulary I need to know
3. The main debates or open questions in this space
4. The most important figures, organizations, or resources I should know about
5. Where a practitioner typically starts

Keep this high-level and practical. Flag where there is genuine disagreement among experts.

2.2 Literature Synthesis

Synthesize what is known about [TOPIC] based on the following sources or your training knowledge.

[OPTIONAL: PASTE KEY EXCERPTS OR CITATIONS]

Specifically, I want to understand:
- What the research consensus says (if one exists)
- Where findings diverge or contradict each other
- Key gaps in the research
- Methodological concerns I should be aware of

Audience: [AUDIENCE — e.g., "a policy maker drafting guidelines on this topic"]
Format: prose synthesis, approximately [LENGTH]

2.3 Comparative Analysis

Compare and contrast [OPTION A] and [OPTION B] across the following dimensions:
1. [DIMENSION 1 — e.g., cost, performance, ease of use]
2. [DIMENSION 2]
3. [DIMENSION 3]
4. [DIMENSION 4]

For each dimension, indicate which option performs better and why.
Conclude with a recommendation for [USE CASE / DECISION CONTEXT].

Any claims you are uncertain about: flag them explicitly rather than stating them as fact.

2.4 SWOT Analysis

Conduct a SWOT analysis for [SUBJECT — e.g., "our proposed entry into the mid-market CRM segment"].

Context:
[PROVIDE RELEVANT BACKGROUND — company size, current market, key constraints, goals]

For each quadrant (Strengths, Weaknesses, Opportunities, Threats), provide 4-6 substantive, specific points. Avoid generic statements. Ground each point in the context I have provided.

Format as a structured table followed by a brief (2-paragraph) synthesis of the most critical strategic implications.

2.5 Decision Matrix Population

Help me build a decision matrix to evaluate the following options:

Options to evaluate:
1. [OPTION 1]
2. [OPTION 2]
3. [OPTION 3]

Criteria to score them on (rate 1-5, where 5 is best):
1. [CRITERION 1] — weight: [WEIGHT e.g., 30%]
2. [CRITERION 2] — weight: [WEIGHT]
3. [CRITERION 3] — weight: [WEIGHT]
4. [CRITERION 4] — weight: [WEIGHT]

Context for scoring: [DESCRIBE WHAT FACTORS SHOULD INFORM THE SCORES]

Present the matrix as a table, show weighted scores, and then briefly explain the top-scoring option and any important caveats.

2.6 Pre-Mortem Analysis

I am planning to [DESCRIBE PROJECT OR DECISION]. Help me conduct a pre-mortem analysis.

Imagine it is [TIMEFRAME — e.g., "12 months from now"] and the project has failed badly. Working backward:
1. List the 5-8 most plausible causes of failure
2. For each cause, rate the likelihood (High/Medium/Low) and the potential impact (High/Medium/Low)
3. For the top 3 risks, suggest a specific mitigation action I could take now

Context: [RELEVANT DETAILS ABOUT THE PROJECT, TEAM, CONSTRAINTS]

Section 3: Brainstorming and Ideation Templates

3.1 Idea Generation with Constraints

Generate [NUMBER] ideas for [GOAL OR CHALLENGE].

Constraints I am working within:
- Budget: [BUDGET]
- Timeline: [TIMELINE]
- Resources available: [RESOURCES]
- Must avoid: [CONSTRAINTS]

For each idea, include: the core concept (1-2 sentences), why it fits the constraints, and one potential downside.

Prioritize ideas that are [CRITERIA — e.g., "unconventional but feasible" or "low-cost and high-impact"].

3.2 Devil's Advocate / Steelman

I am about to [DESCRIBE DECISION OR PLAN]. I want you to challenge this thinking.

My current plan:
[DESCRIBE PLAN]

Please do the following:
1. Devil's advocate: Give me the strongest case AGAINST this plan. What am I missing? What assumptions might be wrong?
2. Steelman: Give me the strongest possible version of an alternative approach.
3. Blind spots: What questions should I be asking that I have not asked?

Be direct and honest. I am not looking for validation.

3.3 Problem Reframing

I am stuck on the following problem:
[DESCRIBE PROBLEM AS YOU CURRENTLY UNDERSTAND IT]

Help me reframe this problem in at least 3 different ways by:
1. Questioning my assumptions about what the problem actually is
2. Identifying whose perspective I may be missing
3. Asking what the problem would look like from a [DIFFERENT DOMAIN — e.g., systems design / economics / psychology] perspective

The goal is to surface new solution paths I have not yet considered.

3.4 Creative Concept Generation

Generate [NUMBER] creative concepts for [PROJECT — e.g., "a brand campaign," "a product feature," "a workshop activity"].

Context:
- Audience: [AUDIENCE]
- Goal: [GOAL]
- Tone / aesthetic direction: [DESCRIPTION]
- Reference points or inspirations: [EXAMPLES]

For each concept: give it a working title, describe the core idea in 2-3 sentences, and explain what makes it distinctive.

Push for variety — give me a range from conventional to unexpected.

Section 4: Coding and Technical Templates

4.1 Code Generation with Context

Write [LANGUAGE] code to accomplish the following:

Task: [CLEAR DESCRIPTION OF WHAT THE CODE SHOULD DO]

Context:
- This code will run in [ENVIRONMENT — e.g., "a Python 3.11 FastAPI backend"]
- Existing relevant code or data structures:
  [PASTE RELEVANT CODE SNIPPETS OR DESCRIBE DATA STRUCTURES]
- Constraints: [e.g., "must not use external libraries other than the standard library", "must handle null inputs gracefully"]

Please include:
- Inline comments explaining non-obvious logic
- Basic error handling
- A brief usage example at the end

4.2 Code Review — Security

Review the following code for security vulnerabilities.

Language: [LANGUAGE]
Context: [WHERE THIS CODE RUNS — e.g., "this is a public-facing API endpoint that processes user-submitted data"]

Code:
[PASTE CODE]

For each issue found:
1. Identify the vulnerability type (e.g., SQL injection, XSS, insecure deserialization)
2. Show the problematic line(s)
3. Explain the risk
4. Provide a corrected version

Also note anything that is done correctly from a security standpoint.

4.3 Code Review — Performance

Review the following code for performance issues.

Language: [LANGUAGE]
Expected scale: [e.g., "this function will be called 10,000 times per second" or "the input list may contain up to 1 million items"]

Code:
[PASTE CODE]

Identify:
- Algorithmic inefficiencies (e.g., O(n²) operations that could be O(n))
- Unnecessary memory allocation
- Missing caching opportunities
- Any I/O bottlenecks

Provide an optimized version with comments explaining what changed and why.

4.4 Bug Debugging with Context

Help me debug the following issue.

Language / framework: [LANGUAGE/FRAMEWORK]
What the code is supposed to do: [EXPECTED BEHAVIOR]
What is actually happening: [ACTUAL BEHAVIOR]
Error message (if any): [PASTE ERROR MESSAGE]

Code:
[PASTE RELEVANT CODE]

Additional context: [RECENT CHANGES, ENVIRONMENT DETAILS, ANYTHING RELEVANT]

Walk me through your diagnosis step by step. If you cannot identify the bug with certainty, list the most likely causes ranked by probability and explain how I would test each hypothesis.

4.5 Test Generation

Write [UNIT / INTEGRATION / END-TO-END] tests for the following code.

Language / testing framework: [e.g., "Python / pytest"]

Code to test:
[PASTE CODE]

Cover:
- Happy path (typical expected inputs)
- Edge cases: [LIST ANY YOU KNOW ABOUT, e.g., "empty input, null values, maximum size input"]
- Error cases: [EXPECTED FAILURE CONDITIONS]

Use descriptive test names that explain what is being tested and why it should pass.

4.6 Documentation Generation

Generate documentation for the following code.

Target audience: [e.g., "developers who will use this as a library but did not write it"]
Format: [e.g., "docstrings in Google style" / "a README section" / "inline comments throughout"]

Code:
[PASTE CODE]

Include:
- Purpose of each function/class
- Parameter descriptions with types
- Return value descriptions
- Any important side effects or exceptions that can be raised
- A usage example for the most important function(s)

4.7 Code Explanation for Non-Technical Audiences

Explain what the following code does to someone who is not a programmer.

Use an analogy if it helps. Focus on what the code accomplishes (the "what" and "why"), not the syntax details (the "how").

Code:
[PASTE CODE]

Audience: [WHO WILL READ THIS EXPLANATION — e.g., "a product manager deciding whether to approve this feature"]
Length: approximately [LENGTH — e.g., "one paragraph"]

Section 5: Business Communication Templates

5.1 Meeting Agenda

Create a meeting agenda for the following:

Meeting purpose: [CLEAR GOAL — e.g., "decide on Q4 marketing budget allocation"]
Attendees: [LIST ROLES / NAMES]
Duration: [LENGTH]
Date/time: [DATE/TIME — optional]

Key topics to cover:
1. [TOPIC 1] — approximate time: [TIME]
2. [TOPIC 2] — approximate time: [TIME]
3. [TOPIC 3] — approximate time: [TIME]

Background / pre-reading attendees should know: [OPTIONAL]

Format: include a pre-meeting prep section, timed agenda items with clear owners, and a "decisions needed" section.

5.2 Status Update / Progress Report

Write a status update report for [PROJECT NAME].

Reporting period: [DATE RANGE]
Audience: [e.g., "executive sponsor and steering committee"]

Information to include:
- Overall status: [ON TRACK / AT RISK / OFF TRACK] and a one-line reason
- Accomplishments this period: [LIST]
- Planned next steps: [LIST]
- Blockers or risks: [LIST]
- Decisions needed from leadership: [LIST OR "NONE"]
- Key metrics: [METRICS AND CURRENT VALUES]

Format: executive-ready, scannable. Use bullet points. Keep to one page equivalent.

5.3 Proposal Outline

Create an outline for a proposal to [DECISION MAKER / ORGANIZATION] requesting [WHAT YOU ARE PROPOSING].

Context:
- Problem being solved: [PROBLEM]
- Proposed solution: [SOLUTION DESCRIPTION]
- Key benefits: [BENEFITS]
- Cost / resource requirement: [COST]
- Timeline: [TIMELINE]
- My organization / role: [CONTEXT]

Structure the proposal with:
1. Executive Summary
2. Problem Statement
3. Proposed Solution
4. Benefits and ROI
5. Implementation Plan
6. Budget
7. Risks and Mitigations
8. Conclusion and Ask

For each section, provide a 2-3 sentence description of what it should contain.

5.4 Customer Response — Support

Draft a customer support response to the following inquiry:

Customer message:
[PASTE CUSTOMER MESSAGE]

Resolution or information available:
[WHAT YOU CAN OFFER OR TELL THEM]

Constraints: [ANYTHING YOU CANNOT SAY OR OFFER]

Tone: empathetic, professional, solution-focused. Acknowledge their frustration if present. Be direct about what will and will not happen. End with a clear next step.

5.5 Sales Outreach — Personalized

Write a personalized sales outreach email for the following prospect.

Prospect: [NAME, ROLE, COMPANY]
What I know about them / their company: [SPECIFIC RESEARCH — e.g., "they recently announced expansion into European markets," "their job posting mentions they are scaling a data team"]
What I am offering: [PRODUCT/SERVICE — one sentence]
Specific value for this prospect: [WHY THIS IS RELEVANT TO THEM]
Desired action: [WHAT I WANT THEM TO DO — e.g., "book a 20-minute call"]

Keep the email under [LENGTH] words. Lead with something specific to them, not a pitch. One clear call to action only.

Section 6: Advanced Technique Templates

6.1 Chain-of-Thought Prompt

I need you to think through the following problem step by step before giving me your final answer.

Problem: [DESCRIBE THE PROBLEM]

Relevant information:
[PROVIDE CONTEXT, DATA, OR CONSTRAINTS]

Instructions:
1. First, identify what type of problem this is and what approach you will use.
2. Work through the problem step by step, showing your reasoning at each step.
3. Check your work — are there any steps where you might have made an error?
4. State your final answer clearly at the end.

Do not skip to the answer. Show all reasoning.

6.2 Few-Shot with Examples Structure

I want you to perform the following task: [TASK DESCRIPTION]

Here are [NUMBER] examples of the input-output pairs I want:

Example 1:
Input: [EXAMPLE INPUT 1]
Output: [EXAMPLE OUTPUT 1]

Example 2:
Input: [EXAMPLE INPUT 2]
Output: [EXAMPLE OUTPUT 2]

Example 3:
Input: [EXAMPLE INPUT 3]
Output: [EXAMPLE OUTPUT 3]

Now perform the same task for:
Input: [YOUR ACTUAL INPUT]
Output:

6.3 Self-Critique and Improve

[COMPLETE YOUR INITIAL TASK PROMPT HERE AND GET A RESPONSE]

Now I want you to critique your own response above. Specifically:
1. What are the weakest parts of this response?
2. What important considerations did you miss?
3. Where might someone disagree with or push back on this?
4. What would make this significantly better?

Then produce an improved version that addresses the issues you identified.

6.4 Role Assignment + Task

You are a [SPECIFIC ROLE — e.g., "senior UX researcher with 15 years of experience in healthcare applications"].

You are known for: [2-3 DISTINCTIVE QUALITIES — e.g., "asking uncomfortable questions about user assumptions," "translating complex findings into executive-ready insights," "always centering edge-case users in your analysis"].

With that lens, help me with the following:
[TASK DESCRIPTION]

Relevant context:
[BACKGROUND INFORMATION]

Stay in this role throughout the conversation. If I ask something outside your expertise, say so.

6.5 Context Packet Structure

Before I give you my task, here is the full context you need:

**Who I am**: [ROLE, ORGANIZATION, RELEVANT BACKGROUND]

**The project**: [DESCRIPTION — what it is, its goals, its current stage]

**My audience**: [WHO WILL RECEIVE OR USE THE OUTPUT]

**Constraints and requirements**:
- [CONSTRAINT 1]
- [CONSTRAINT 2]
- [CONSTRAINT 3]

**What I have already tried**: [PREVIOUS APPROACHES AND WHY THEY DID NOT WORK]

**Success looks like**: [CLEAR DEFINITION OF A GOOD OUTPUT]

---

Now, with all of this context in mind, please: [TASK]

Quick-Reference Index

These templates are starting points. The best prompts are adapted to your specific context. For guidance on customizing templates and building your own library, see Chapter 4.