AI Prompt Templates

Act as an experienced [type of writer].

Write a [content type] about [topic].

Purpose:
[What the content should help the reader understand, decide, or do.]

Audience:
[Describe the intended reader and what they already know.]

Key points to include:
- [Key point 1]
- [Key point 2]
- [Key point 3]

Requirements:
- Use a [tone] tone.
- Keep the content between [length].
- Use only the supplied facts.
- Avoid [claims, phrases, style, or topics to exclude].
- Include [examples, evidence, steps, or recommendations].

Output format:
[Specify headings, paragraphs, bullets, table, or other structure.]

Source material:
[Paste notes, facts, or references.]

Proofread the text below.

Check for:
- Spelling and grammar errors
- Incorrect punctuation
- Awkward or unclear sentences
- Inconsistent capitalization and terminology
- Repeated words or unnecessary repetition
- Formatting inconsistencies

Rules:
- Preserve the author's meaning and voice.
- Make only necessary corrections.
- Do not rewrite correct sentences purely for stylistic preference.
- Do not add new facts or arguments.

Output:
1. Provide the corrected text.
2. List any changes that materially affect meaning or clarity.
3. Flag statements that appear ambiguous but cannot be safely corrected without more context.

Text:
[Paste text]

Act as an experienced content strategist.

Create a detailed outline for a blog post about [topic].

Audience:
[target reader]

Search intent:
[informational / commercial / transactional / navigational]

Reader goal:
[What the reader should understand or accomplish.]

Requirements:
- Propose one clear working title.
- Organize the article with logical H2 and H3 headings.
- Explain the purpose of every section.
- Include important questions the article should answer.
- Identify where examples, data, screenshots, or expert sources are needed.
- Avoid overlapping sections and unnecessary filler.
- Include a concise conclusion with an appropriate next step.

Output format:
Return a structured outline with Title, Introduction, H2 sections, H3 subsections, Key Points, Evidence Needed, and Conclusion.

Act as a senior content strategist.

Create an actionable content brief for an article about [topic].

Business goal:
[traffic / leads / education / product adoption / authority]

Target audience:
[Describe the reader, experience level, and primary problem.]

Primary query or topic:
[keyword or subject]

Include:
1. Recommended title
2. Search intent
3. Reader goal
4. Unique angle
5. Recommended word-count range
6. H2 and H3 outline
7. Questions the article must answer
8. Examples or evidence needed
9. Relevant internal-link opportunities
10. Potential external sources
11. Conversion or next-step recommendation
12. Accuracy risks and claims requiring verification

Avoid generic advice. Make every recommendation specific enough for a writer to execute.

Act as an SEO strategist.

Analyze the supplied keyword list for [website, product, or topic].

For each keyword:
- Identify the likely search intent.
- Assign one category: informational, commercial, transactional, or navigational.
- Group closely related keywords into logical topic clusters.
- Recommend one primary keyword for each cluster.
- Identify supporting secondary keywords.
- Suggest the most appropriate content type.
- Flag keywords with ambiguous intent.

Rules:
- Use only the supplied keyword data.
- Do not invent search volume, competition, CPC, or trend data.
- Explain any uncertain classification.
- Avoid creating separate pages for keywords with the same underlying intent.

Output format:
Return a Markdown table with Keyword, Intent, Cluster, Recommended Page Type, Primary or Secondary, and Notes.

Keyword data:
[Paste keyword list and available metrics]

Create SEO title and meta-description options for the page described below.

Primary query:
[focus keyword]

Search intent:
[informational / commercial / transactional / navigational]

Page value:
[What makes the page useful or different.]

Requirements:
- Place the primary query naturally near the beginning of the title.
- Keep every title clear, specific, and readable.
- Avoid clickbait, unsupported superlatives, and keyword stuffing.
- Make every description accurately summarize the page.
- Include a meaningful benefit or reason to visit.
- Do not promise features that the page does not contain.

Return:
- Five SEO title options
- Five matching meta descriptions
- Character count for every option
- One recommended title-description pair with a short explanation

Page summary:
[Paste summary or page content]

Act as a social media strategist.

Create a [number]-week content calendar for [brand, creator, or organization].

Primary goal:
[awareness / education / engagement / leads / community]

Audience:
[Describe the target audience.]

Platforms:
[list platforms]

Content pillars:
- [Pillar 1]
- [Pillar 2]
- [Pillar 3]

Available resources:
[team, time, existing content, images, video, budget]

Requirements:
- Adapt every idea to the selected platform.
- Balance educational, practical, conversational, and promotional content.
- Avoid repeating the same angle.
- Include a clear purpose for every post.
- Do not invent product claims, statistics, or customer stories.
- Keep the schedule realistic for the available resources.

Output format:
Return a table with Date, Platform, Content Pillar, Topic, Format, Hook, Key Message, CTA, and Asset Needed.

Turn the source material below into a [number]-slide social media carousel.

Platform:
[LinkedIn / Instagram / other]

Audience:
[target audience]

Goal:
[educate / explain / compare / summarize / persuade]

Structure:
- Slide 1: Clear title or problem
- Slides 2–[number minus 2]: One focused idea per slide
- Penultimate slide: Key takeaway or checklist
- Final slide: Relevant next step or discussion question

Requirements:
- Keep every slide understandable on its own.
- Use a short headline and concise supporting text.
- Preserve important qualifications and factual accuracy.
- Avoid repeating the same statement across slides.
- Suggest one simple visual concept for every slide.
- Do not invent statistics, quotations, or examples.

Output format:
Return Slide Number, Headline, Supporting Copy, and Visual Direction.

Source material:
[Paste content]

Write a professional email to [recipient or role].

Purpose:
[Explain why you are writing.]

Context:
[Provide the relevant situation, history, or background.]

Key information:
- [Important point 1]
- [Important point 2]
- [Important point 3]

Requested action:
[What the recipient should do and by when.]

Tone:
[professional / friendly / appreciative / apologetic / firm]

Requirements:
- Use a clear subject line.
- State the purpose early.
- Keep the email concise.
- Make the requested action specific.
- Preserve all names, dates, amounts, and deadlines.
- Avoid unnecessary jargon and exaggerated language.

Return:
1. Subject line
2. Email body
3. A shorter alternative version

Write a polite follow-up email about [topic, request, proposal, or meeting].

Recipient:
[name or role]

Previous contact:
[Describe when and how you last contacted them.]

Reason for following up:
[Explain what response, decision, document, or action is needed.]

Deadline or timing:
[date or time frame]

Tone:
[professional / friendly / concise / gently urgent]

Requirements:
- Refer briefly to the previous communication.
- Restate the request clearly.
- Explain why the timing matters without sounding demanding.
- Make it easy for the recipient to respond.
- Offer a reasonable next step or alternative.
- Keep the email under [length].

Return two versions:
1. Standard follow-up
2. Short final reminder

Act as a market research analyst.

Create an evidence-based audience persona using only the supplied research.

Product or service:
[Describe the offer.]

Research data:
[Paste survey results, interviews, reviews, support tickets, analytics, or sales notes.]

Identify:
1. Primary goals
2. Most important problems
3. Common objections
4. Decision criteria
5. Current alternatives
6. Frequently used language
7. Information needed before purchasing
8. Preferred channels, if supported by the data
9. Relevant differences between audience segments
10. Important unanswered questions

Rules:
- Separate direct evidence from reasonable inference.
- Quote or reference the supplied data when useful.
- Do not invent demographics, motivations, income, behavior, or preferences.
- Mark unsupported assumptions clearly.
- Recommend additional research for important gaps.

Output format:
Return Persona Summary, Evidence, Goals, Problems, Objections, Decision Criteria, Messaging Implications, and Research Gaps.

Act as a senior marketing strategist.

Create a campaign plan for [product, service, event, or launch].

Objective:
[specific business goal]

Target audience:
[describe the audience]

Core message:
[primary value proposition]

Campaign period:
[start date and end date]

Available channels:
[list approved channels]

Budget and resources:
[budget, team, assets, tools, and limitations]

Include:
- Campaign objective and measurable KPIs
- Audience insight and message
- Channel strategy
- Content and asset plan
- Weekly timeline
- Responsibilities
- Budget allocation
- Tracking requirements
- Risks and contingency actions
- Post-campaign review plan

Rules:
- Keep the plan realistic for the available resources.
- Do not invent benchmarks or expected results.
- Connect every activity to an objective and KPI.

Output format:
Return an executive summary followed by a campaign table with Phase, Activity, Channel, Owner, Deadline, Budget, and KPI.

Create a focused meeting agenda.

Meeting:
[meeting name]

Objective:
[The decision, outcome, or progress the meeting must achieve.]

Participants:
[List roles or attendees.]

Duration:
[number of minutes]

Context:
[Relevant background, previous decisions, or current status.]

Topics:
- [Topic 1]
- [Topic 2]
- [Topic 3]

Requirements:
- Prioritize decisions and discussion over status updates.
- Assign a time limit and owner to every agenda item.
- Identify required pre-reading or preparation.
- Separate discussion items from decisions.
- Reserve time for actions, owners, and deadlines.
- Remove topics that can be handled asynchronously.

Output format:
Return Meeting Objective, Preparation, Timed Agenda, Decisions Required, and Action-Item Template.

Act as an impartial business analyst.

Create a decision memo for [decision].

Decision required:
[State the exact question.]

Options:
- [Option 1]
- [Option 2]
- [Option 3]

Evaluation criteria:
- [Criterion 1]
- [Criterion 2]
- [Criterion 3]

Evidence and constraints:
[Paste verified data, costs, requirements, risks, and limitations.]

Include:
1. Executive summary
2. Decision context
3. Options considered
4. Comparison against each criterion
5. Benefits and limitations
6. Risks and reversibility
7. Missing information
8. Recommended option
9. Conditions that would change the recommendation
10. Immediate next steps

Rules:
- Use only the supplied evidence.
- Separate facts, assumptions, and judgment.
- Do not hide meaningful disadvantages.
- Do not force a recommendation if evidence is insufficient.

Act as an experienced consultative salesperson.

Prepare discovery questions for a conversation with [prospect or customer type].

Product or service:
[Describe the offer.]

Known context:
[Company, role, current situation, previous contact, or stated need.]

The questions should uncover:
1. Current process
2. Primary goals
3. Important problems
4. Impact of the current problem
5. Existing tools or alternatives
6. Decision criteria
7. Stakeholders
8. Budget or resource constraints
9. Timing
10. Risks and objections
11. Definition of success

Requirements:
- Use open-ended, neutral questions.
- Avoid leading questions and premature pitching.
- Organize questions from broad context to specific needs.
- Mark which questions are essential and which are optional.
- Do not assume needs that are not supported by the context.

Output format:
Return a table with Question, Purpose, Follow-Up Question, and Priority.

Help me respond to the following sales objection.

Customer objection:
[Paste the exact objection.]

Customer context:
[Goals, requirements, concerns, current solution, and decision stage.]

Verified product information:
[Relevant capabilities, limitations, pricing, evidence, and policies.]

Create a response that:
- Acknowledges the concern without dismissing it.
- Clarifies the reason behind the objection.
- Answers using only verified information.
- Explains relevant tradeoffs honestly.
- Asks one useful follow-up question.
- Suggests a reasonable next step.

Rules:
- Do not pressure the customer.
- Do not invent discounts, guarantees, features, or results.
- State clearly when the product is not a good fit.
- Keep the response concise and conversational.

Return:
1. Spoken response
2. Email response
3. Follow-up question
4. Situations where the objection should not be challenged

Act as a senior [programming language] developer and patient technical educator.

Explain the code below for a developer with [beginner / intermediate / advanced] experience.

Cover:
1. The code's overall purpose
2. Inputs and outputs
3. Execution flow
4. Important functions, classes, and variables
5. External dependencies
6. State changes and side effects
7. Error handling
8. Time and space complexity when relevant
9. Security or reliability concerns
10. One concrete example using sample input

Requirements:
- Explain the actual code rather than providing a generic language tutorial.
- Define unfamiliar terminology.
- Distinguish confirmed behavior from assumptions.
- Flag missing context that could change the explanation.
- Do not rewrite the code unless asked.

Code:
[Paste code]

Act as a senior [language, framework, or platform] developer.

Implement the following feature:
[Describe the exact feature.]

Existing system:
[Describe the architecture, relevant files, interfaces, and current behavior.]

Inputs:
[Expected inputs and data types.]

Expected outputs:
[Expected return values, UI behavior, or side effects.]

Requirements:
- [Functional requirement 1]
- [Functional requirement 2]
- [Validation requirement]
- [Performance requirement]
- [Accessibility or security requirement]

Constraints:
- Use [approved language, framework, API, or version].
- Do not add external dependencies unless essential.
- Preserve existing public interfaces.
- Do not modify unrelated behavior.
- Handle expected errors explicitly.

Return:
1. Assumptions and clarifying questions
2. Implementation plan
3. Production-ready code
4. Tests for normal, edge, and failure cases
5. Integration instructions
6. Important tradeoffs or limitations

Act as an experienced data analyst.

Review the dataset description and sample below, then create a data-cleaning plan.

Analysis goal:
[What the cleaned data will be used for.]

Dataset:
[Paste schema, column definitions, data types, and representative sample rows.]

Check for:
1. Missing values
2. Duplicate records
3. Incorrect data types
4. Inconsistent categories or labels
5. Invalid dates
6. Impossible or out-of-range values
7. Formatting inconsistencies
8. Units and currency differences
9. Potential outliers
10. Personally identifiable or sensitive information

For every issue:
- Explain how to detect it.
- Recommend a safe treatment.
- Describe the risk of that treatment.
- State when human review is required.
- Suggest a validation check.

Rules:
- Do not silently delete or replace uncertain values.
- Preserve the original data.
- Do not assume missing values mean zero.
- Flag any cleaning decision that could bias the analysis.

Output format:
Return a prioritized table with Issue, Detection Method, Recommended Action, Risk, and Validation.

Act as a careful data analyst and explain the results below for [target audience].

Original question:
[What the analysis was intended to answer.]

Method:
[Describe calculations, filters, sample, and time period.]

Results:
[Paste tables, statistics, model output, or observations.]

Explain:
1. The most important findings
2. The magnitude and practical meaning of each result
3. Important comparisons
4. Uncertainty and limitations
5. Alternative explanations
6. What the analysis does not prove
7. Decisions the results may inform
8. Additional data or tests needed

Rules:
- Use only the supplied results.
- Distinguish statistical findings from business interpretation.
- Do not imply causation unless the study design supports it.
- Preserve units, sample sizes, and time periods.
- Flag missing context that prevents reliable interpretation.

Output format:
Return Executive Summary, Key Findings, Limitations, Decision Implications, and Next Analysis.

Act as a patient teacher with expertise in [subject].

Explain [topic] to a learner at [beginner / intermediate / advanced] level.

The learner already understands:
[list prior knowledge]

The learner is confused about:
[list difficult areas or questions]

Structure:
1. Plain-language definition
2. Why the topic matters
3. Required background concepts
4. Step-by-step explanation
5. One concrete example
6. One useful analogy, if accurate
7. Common misconceptions
8. Short summary
9. Three questions to check understanding
10. Recommended next topic

Requirements:
- Define technical terms when first used.
- Do not oversimplify away essential details.
- Separate established facts from interpretation.
- State when an analogy has limitations.
- Use equations, diagrams, or code only when helpful.
- Flag areas where current information may require verification.

Create a practice quiz about [topic] for a learner at [level].

Learning objectives:
- [Objective 1]
- [Objective 2]
- [Objective 3]

Source material:
[Paste approved notes, textbook section, or study guide.]

Create:
- [number] multiple-choice questions
- [number] short-answer questions
- [number] application or scenario questions

Requirements:
- Test understanding rather than trivial memorization.
- Cover every learning objective.
- Use only information found in the source material.
- Avoid ambiguous wording and trick questions.
- Make incorrect options plausible but clearly incorrect.
- Vary difficulty from basic recall to application.
- Do not reveal answers beside the questions.

After the questions, provide:
1. Answer key
2. Explanation for every answer
3. Learning objective tested
4. Difficulty level
5. Common misconception addressed

Act as an experienced research-methods advisor.

Help refine the following broad topic into a clear research question.

Broad topic:
[topic]

Purpose:
[academic paper / business decision / product research / policy / personal learning]

Population or context:
[who, where, industry, system, or situation]

Available time and resources:
[time, data access, tools, participants, and limitations]

Existing knowledge:
[what is already known]

Create:
1. Five possible research questions
2. Scope and key concepts for each
3. Suitable research method
4. Required evidence or data
5. Feasibility risks
6. Ethical or privacy considerations
7. Important assumptions
8. One recommended question

Requirements:
- Make each question specific and answerable.
- Avoid questions that already assume a conclusion.
- Distinguish descriptive, comparative, causal, and exploratory questions.
- Explain why the recommended question is useful and feasible.

Synthesize the supplied sources to answer this research question:

Research question:
[question]

Use only the provided sources.

For each major claim:
- Identify which sources support it.
- Identify disagreement or contradictory evidence.
- Compare methodology, population, sample, and time period.
- Assess evidence strength and important limitations.
- Distinguish findings from author interpretation.
- Note unanswered questions.

Return:
1. Executive summary
2. Major themes
3. Areas of agreement
4. Areas of disagreement
5. Strongest supporting evidence
6. Important limitations
7. Research gaps
8. Cautious conclusion
9. Source-to-claim table

Citation rules:
- Cite sources using the supplied source names or numbers.
- Do not invent authors, titles, quotations, page numbers, URLs, or findings.
- Mark any statement that cannot be supported by the provided material.

Sources:
[Paste numbered sources]

Act as an experienced resume editor.

Tailor my resume to the supplied job description.

Rules:
- Use only experience, skills, education, and results found in my resume.
- Do not invent responsibilities, achievements, tools, dates, or qualifications.
- Preserve accurate job titles and employment dates.
- Use terminology from the job description only when it truthfully matches my experience.
- Prioritize relevant evidence.
- Improve clarity and specificity without exaggeration.
- Keep the format concise and ATS-readable.

Return:
1. Match analysis
2. Important requirements supported by my resume
3. Important gaps
4. Revised professional summary
5. Revised experience bullets
6. Recommended skills order
7. Keywords used naturally
8. Claims that require my confirmation

Job description:
[Paste job description]

Current resume:
[Paste resume]

Act as an interview coach for [industry or role].

Help me prepare for the position below.

Job description:
[Paste job description]

My resume:
[Paste resume]

Company information:
[Paste verified company information]

Create:
1. Ten likely interview questions
2. Why each question may be asked
3. Key points from my real experience that could support an answer
4. Five behavioral questions
5. STAR-answer planning prompts
6. Role-specific technical or practical questions
7. Important gaps or difficult questions
8. Thoughtful questions I can ask the interviewer
9. A concise self-introduction
10. Final preparation checklist

Rules:
- Do not write fictional experiences for me.
- Flag answers requiring a specific example I have not provided.
- Avoid memorized-sounding scripts.
- Distinguish verified company information from assumptions.

Act as a creative strategist.

Generate [number] meaningfully different ideas for [project, campaign, product, story, or problem].

Goal:
[What the ideas should achieve.]

Audience:
[target audience]

Context:
[Relevant situation, brand, theme, or background.]

Constraints:
- [Budget, format, channel, length, or technical limitation]
- [Required element]
- [Element or approach to avoid]

For each idea, provide:
1. Short name
2. One-sentence concept
3. Why it fits the goal
4. Primary benefit
5. Possible limitation
6. First practical step
7. What makes it different from the other ideas

Requirements:
- Explore different strategic directions rather than minor variations.
- Avoid generic ideas that could apply to any project.
- Do not copy protected characters, logos, slogans, or recognizable campaigns.
- Rank the three strongest ideas against the stated goal.

Create a detailed image-generation prompt.

Purpose:
[website hero / illustration / poster / product image / thumbnail / concept art]

Primary subject:
[Describe the main subject.]

Scene and background:
[Describe the environment.]

Style and medium:
[photography / vector / 3D / watercolor / editorial illustration / other]

Composition:
[camera angle, framing, subject placement, and negative space]

Lighting and mood:
[lighting direction, contrast, atmosphere, and emotion]

Color palette:
[primary and accent colors]

Important details:
- [Detail 1]
- [Detail 2]
- [Detail 3]

Text:
[Exact text if required, otherwise state no text.]

Aspect ratio:
[ratio or intended dimensions]

Avoid:
[unwanted objects, artifacts, styles, logos, text, or visual problems]

Requirements:
- Make the subject and composition unambiguous.
- Do not reference a living artist's distinctive style.
- Avoid protected logos or characters unless authorized.
- Keep small-thumbnail readability in mind when relevant.

Return one polished prompt and two controlled variations.