Skip to main content
Back to Blog
Comprehensive GuideFeatured
prompt templatesframeworkscheat sheetcopy-pasteproductivityChatGPTClaude

The Ultimate AI Prompt Cheat Sheet: 30 Copy-Paste Frameworks (2026)

Stop writing prompts from scratch. These 30 proven frameworks cover every common AI task — just fill in the brackets and paste. Works with ChatGPT, Claude, Gemini, and any LLM.

SurePrompts Team
March 19, 2026
13 min read

Every prompt you'll ever need, distilled into 30 frameworks. Fill in the brackets, paste into any AI, get better results in seconds.

Why Frameworks Beat Freestyle

Most people write prompts the same way they'd text a friend — stream of consciousness, vague, and hoping for the best.

Frameworks fix this. They encode prompt engineering best practices into fill-in-the-blank structures you can memorize and reuse. Once you know 5-10 of these frameworks, you'll never stare at a blank ChatGPT input again.

10x
Users who follow structured frameworks report up to 10x improvement in AI output quality versus unstructured prompting

Every framework below works with ChatGPT, Claude, Gemini, and any other LLM. Copy them. Customize them. Make them yours.

Writing & Content Frameworks

1. The Expert Writer

code
You are an expert [TYPE OF WRITER] with 15 years of experience writing for [AUDIENCE].

Write a [FORMAT] about [TOPIC].

Requirements:
- Tone: [TONE]
- Length: [WORD COUNT] words
- Include: [SPECIFIC ELEMENTS]
- Avoid: [WHAT TO EXCLUDE]

Structure the piece with a compelling hook, clear sections, and an actionable conclusion.

When to use: Blog posts, articles, newsletters, any long-form content.

2. The Rewriter

code
Rewrite the following text to be [DESIRED QUALITY — more concise / more persuasive / simpler / more professional].

Keep the core message intact. Target audience: [AUDIENCE].
Output length: [SHORTER/SAME/LONGER] than the original.

Text to rewrite:
[PASTE TEXT]

When to use: Editing drafts, adapting content for different audiences, improving clarity.

3. The Social Media Post

code
Write a [PLATFORM] post about [TOPIC].

Audience: [WHO]
Goal: [ENGAGEMENT/AWARENESS/CLICKS]
Tone: [TONE]
Include: [HASHTAGS/CTA/EMOJI PREFERENCE]
Length: [CHARACTER LIMIT]

Start with a hook that stops the scroll. End with a clear call-to-action.

When to use: LinkedIn, X/Twitter, Instagram captions, Facebook posts.

4. The Email Composer

code
Write a [TYPE — cold outreach / follow-up / newsletter / internal] email.

From: [YOUR ROLE]
To: [RECIPIENT AND THEIR ROLE]
Goal: [WHAT YOU WANT THEM TO DO]
Context: [RELEVANT BACKGROUND]
Tone: [PROFESSIONAL/FRIENDLY/URGENT]
Length: Under [NUMBER] sentences.

Subject line options: Provide 3.

When to use: Any professional email where you need the right tone and structure.

Analysis & Research Frameworks

5. The Analyst

code
Analyze [TOPIC/DATA/SITUATION] from the perspective of a [SPECIFIC EXPERT ROLE].

Consider these dimensions:
1. [DIMENSION 1]
2. [DIMENSION 2]
3. [DIMENSION 3]

For each dimension, provide:
- Current state assessment
- Key risks or opportunities
- One specific recommendation

Conclude with a prioritized action plan.

When to use: Business analysis, strategy evaluation, market assessment, data interpretation.

6. The Comparison Table

code
Create a detailed comparison of [OPTION A] vs [OPTION B] vs [OPTION C].

Compare on these criteria:
- [CRITERION 1]
- [CRITERION 2]
- [CRITERION 3]
- [CRITERION 4]
- [CRITERION 5]

Format as a table. Add a "Best For" row at the bottom with a one-sentence recommendation for each option.

When to use: Product comparisons, tool evaluations, decision-making.

7. The Research Synthesizer

code
Synthesize information about [TOPIC] for someone who is a [EXPERTISE LEVEL — beginner / intermediate / expert] in [FIELD].

Cover:
1. What it is (2-3 sentences)
2. Why it matters right now
3. How it works (practical explanation)
4. Key advantages and limitations
5. Practical next steps

Use concrete examples. Avoid jargon unless you define it first.

When to use: Understanding new topics, preparing briefings, learning efficiently.

Business & Strategy Frameworks

8. The Decision Maker

code
Help me decide between [OPTION A] and [OPTION B].

Context: [YOUR SITUATION]
Goals: [WHAT YOU'RE OPTIMIZING FOR]
Constraints: [BUDGET/TIME/RESOURCES]
Risk tolerance: [LOW/MEDIUM/HIGH]

For each option, analyze:
- Pros (at least 3)
- Cons (at least 3)
- Hidden risks
- 12-month projected outcome

End with a clear recommendation and the single strongest reason for it.

When to use: Any business decision with multiple viable options.

9. The Meeting Prep

code
I have a [TYPE OF MEETING] with [WHO] about [TOPIC] in [TIME FRAME].

My goal: [WHAT I WANT TO ACHIEVE]
Their likely priorities: [WHAT THEY CARE ABOUT]
Potential objections: [WHAT THEY MIGHT PUSH BACK ON]

Prepare:
1. Opening statement (30 seconds)
2. 3 key points with supporting evidence
3. Responses to likely objections
4. Specific ask / next steps proposal
5. Fallback position if they say no

When to use: Client meetings, pitches, negotiations, difficult conversations.

10. The SWOT+

code
Perform a SWOT analysis of [COMPANY/PRODUCT/STRATEGY].

For each quadrant (Strengths, Weaknesses, Opportunities, Threats):
- List 3-5 items
- Rate each as HIGH/MEDIUM/LOW impact
- Add one specific action item

Then identify the single most important strategic insight from the analysis and explain why it should drive the next 90 days of decisions.

When to use: Strategic planning, competitive analysis, business reviews.

Problem-Solving Frameworks

11. The Debugger

code
I'm experiencing this problem: [DESCRIBE THE ISSUE]

What I expected: [EXPECTED BEHAVIOR]
What actually happens: [ACTUAL BEHAVIOR]
What I've already tried: [PREVIOUS ATTEMPTS]
Environment: [RELEVANT CONTEXT — tool versions, OS, settings]

Walk me through a systematic diagnosis:
1. Most likely root causes (ranked by probability)
2. How to verify each one
3. Fix for the most likely cause
4. How to prevent recurrence

When to use: Technical debugging, troubleshooting, process issues.

12. The Root Cause Finder

code
[PROBLEM STATEMENT]

Apply the "5 Whys" technique to find the root cause:

Start with the surface problem and ask "why" iteratively until you reach the fundamental cause. For each level, explain the causal mechanism.

Then suggest fixes at both the root cause level (permanent fix) and the symptom level (immediate relief).

When to use: Recurring issues, post-mortems, quality problems.

13. The Devil's Advocate

code
I'm planning to [DECISION/STRATEGY].

My reasoning: [WHY I THINK THIS IS RIGHT]

Challenge this decision aggressively:
1. What are the 3 strongest arguments against it?
2. What am I probably not seeing?
3. What could go catastrophically wrong?
4. Who would disagree with this and why?
5. Is there a simpler alternative I'm overlooking?

Be direct and specific. I need honest pushback, not validation.

When to use: Before major decisions, strategy validation, avoiding confirmation bias.

Creative & Brainstorming Frameworks

14. The Idea Generator

code
Generate [NUMBER] ideas for [WHAT] related to [TOPIC/INDUSTRY].

Constraints:
- Target audience: [WHO]
- Budget level: [LOW/MEDIUM/HIGH]
- Timeline: [TIME FRAME]
- Must include: [REQUIREMENT]

For each idea:
- One-line description
- Why it would work
- Biggest risk
- First step to test it

Sort by feasibility, with the most actionable idea first.

When to use: Brainstorming sessions, content ideation, product features, marketing campaigns.

15. The Perspective Shifter

code
[TOPIC OR SITUATION]

Analyze this from 5 different perspectives:
1. [STAKEHOLDER 1 — e.g., the customer]
2. [STAKEHOLDER 2 — e.g., the engineer]
3. [STAKEHOLDER 3 — e.g., the CFO]
4. [STAKEHOLDER 4 — e.g., a competitor]
5. [STAKEHOLDER 5 — e.g., a new employee]

For each perspective, explain:
- What they care about most
- What worries them
- What they would change

Then identify the insight that only emerges when you consider all perspectives together.

When to use: Product design, conflict resolution, strategy development.

Technical & Data Frameworks

16. The Code Generator

code
Write [LANGUAGE] code that [WHAT IT DOES].

Requirements:
- Input: [INPUT FORMAT]
- Output: [OUTPUT FORMAT]
- Edge cases to handle: [LIST]
- Performance requirement: [IF ANY]

Include:
- Brief comments explaining non-obvious logic
- Error handling for common failure modes
- One usage example

Do not include: [UNNECESSARY COMPLEXITY]

When to use: Any coding task — scripts, functions, components, utilities.

17. The Data Interpreter

code
Here is my data: [PASTE DATA OR DESCRIBE DATASET]

Analyze this data and tell me:
1. What patterns are immediately visible?
2. What's surprising or unexpected?
3. What questions should I be asking about this data?
4. What additional data would I need to draw stronger conclusions?
5. What action should I take based on what we can see?

Present key findings as bullet points, not paragraphs. Include specific numbers.

When to use: Spreadsheet analysis, survey results, performance metrics, financial data.

18. The Documentation Writer

code
Write documentation for [WHAT — API endpoint / function / feature / process].

Audience: [WHO WILL READ THIS — developers / end users / new team members]

Include:
- Purpose (what and why, one paragraph)
- Quick start (get running in under 2 minutes)
- Parameters/inputs (table format)
- Expected outputs
- Common errors and fixes
- One complete example

Style: [CONCISE/COMPREHENSIVE] — avoid jargon unless the audience expects it.

When to use: API docs, README files, internal wikis, user guides.

Learning & Education Frameworks

19. The Teacher

code
Explain [CONCEPT] to someone who [CURRENT KNOWLEDGE LEVEL].

Use:
- An analogy from [FAMILIAR DOMAIN]
- A concrete, real-world example
- A simple diagram described in text (if helpful)

Structure:
1. What it is (2 sentences, no jargon)
2. Why it matters (real-world impact)
3. How it works (step by step)
4. Common misconceptions
5. How to learn more (specific next steps)

When to use: Learning new topics, explaining to colleagues, creating training materials.

20. The Study Guide

code
Create a study guide for [TOPIC/EXAM/SKILL].

My current level: [BEGINNER/INTERMEDIATE/ADVANCED]
Time available: [TIME FRAME]
Goal: [WHAT I NEED TO BE ABLE TO DO]

Include:
1. Key concepts ranked by importance
2. Common exam/interview questions with concise answers
3. Memory aids or mnemonics for complex topics
4. Practice problems (with answers)
5. One-page "night before" cheat sheet

When to use: Exam prep, certification study, skill development, interview preparation.

Productivity & Workflow Frameworks

21. The Task Breaker

code
Break this project into actionable tasks: [PROJECT DESCRIPTION]

For each task:
- Clear, specific description (starts with a verb)
- Estimated time
- Dependencies (what needs to happen first)
- Definition of done

Group tasks into phases. Identify the critical path — which tasks, if delayed, delay everything.

When to use: Project planning, sprint planning, personal productivity.

22. The Template Creator

code
Create a reusable template for [WHAT — weekly report / project proposal / client brief / etc.].

Context: I do this [FREQUENCY] for [AUDIENCE].
Currently takes me: [TIME]
Goal: Reduce to [TARGET TIME]

The template should:
- Have clear sections with placeholder instructions
- Include examples for each section
- Work as a checklist (nothing gets forgotten)
- Be adaptable for different [SCENARIOS]

When to use: Any repetitive task that would benefit from standardization.

23. The Summarizer

code
Summarize the following in [FORMAT — bullet points / executive summary / key takeaways]:

Length: [WORD COUNT OR NUMBER OF POINTS]
Audience: [WHO]
Focus on: [WHAT MATTERS MOST]
Omit: [WHAT TO SKIP]

Text to summarize:
[PASTE TEXT]

When to use: Long documents, meeting transcripts, research papers, reports.

Advanced Frameworks

24. The System Prompt Builder

code
Create a [system prompt](/glossary/system-prompt) for an AI assistant that [PURPOSE].

The assistant should:
- Role: [SPECIFIC EXPERT IDENTITY]
- Tone: [PERSONALITY DESCRIPTION]
- Always: [REQUIRED BEHAVIORS]
- Never: [PROHIBITED BEHAVIORS]
- Format: [DEFAULT OUTPUT FORMAT]
- When uncertain: [FALLBACK BEHAVIOR]

Test the system prompt with this example user message: "[EXAMPLE]"

When to use: Building custom GPTs, configuring AI assistants, chatbot design.

25. The Few-Shot Teacher

code
I want you to [TASK]. Here are examples of the input and desired output:

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

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

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

Now apply the same pattern to:
Input: [YOUR ACTUAL INPUT]

When to use: Classification, formatting, style matching, any task where examples define the pattern better than instructions. See few-shot prompting for more.

26. The Iterative Refiner

code
[INITIAL REQUEST]

After you respond, I'll give feedback. Apply each round of feedback while preserving what's working. Don't start over — refine.

Refinement rules:
- Keep changes surgical — modify only what I mention
- If my feedback contradicts a previous instruction, the latest feedback wins
- After each revision, briefly note what you changed and why

When to use: Writing, design briefs, strategy documents — anything that benefits from iteration.

27. The Prompt Evaluator

code
Evaluate this prompt and suggest improvements:

[PASTE PROMPT]

Score it on:
1. Clarity (is the task unambiguous?)
2. Specificity (are constraints defined?)
3. Context (does the AI have what it needs?)
4. Format (is the expected output clear?)
5. Efficiency (any unnecessary words?)

Rewrite the improved version below the evaluation.

When to use: Improving your own prompts, learning prompt engineering, quality checking.

28. The Persona Tester

code
Respond to the following question AS [SPECIFIC PERSONA]:

Persona details:
- Name: [NAME]
- Role: [JOB/POSITION]
- Experience: [YEARS AND DOMAIN]
- Communication style: [DIRECT/DIPLOMATIC/TECHNICAL/CASUAL]
- Key priorities: [WHAT THEY CARE ABOUT]
- Blind spots: [WHAT THEY MIGHT MISS]

Question: [YOUR QUESTION]

Stay fully in character. If the persona wouldn't know something, say so.

When to use: User research simulation, stakeholder analysis, preparing for presentations, product testing.

29. The Constraint Optimizer

code
I need to [GOAL] with these constraints:
- Budget: [AMOUNT]
- Timeline: [DEADLINE]
- Resources: [WHAT'S AVAILABLE]
- Must have: [NON-NEGOTIABLE REQUIREMENTS]
- Nice to have: [OPTIONAL REQUIREMENTS]

Propose 3 approaches:
1. Best quality (maximize output, may push constraints)
2. Most efficient (minimize resource usage)
3. Balanced (best trade-off)

For each, specify exactly what you'd sacrifice and what you'd gain.

When to use: Resource-constrained projects, budget planning, prioritization.

30. The Agentic Task

code
# Goal
[CLEAR, MEASURABLE OUTCOME]

# Context
[RELEVANT BACKGROUND]

# Steps
1. [FIRST ACTION]
2. [SECOND ACTION]
3. [THIRD ACTION — include decision point]

# Constraints
- [SCOPE LIMIT]
- [QUALITY REQUIREMENT]
- [SAFETY BOUNDARY]

# Output
[EXACT FORMAT AND LENGTH]

# If something goes wrong
- [FALLBACK FOR COMMON FAILURES]

When to use: AI agents, autonomous workflows, multi-step tasks. See our full agentic AI prompting guide for details.

How to Use This Cheat Sheet

Don't try to memorize all 30. Start with these 5:

  • The Expert Writer (#1) — for any content creation
  • The Analyst (#5) — for any analysis task
  • The Decision Maker (#8) — for any decision
  • The Debugger (#11) — for any problem
  • The Summarizer (#23) — for processing information

Master those five and you'll handle 80% of AI tasks better than most people. Then add frameworks as you need them.

Every framework above is available as a template in the SurePrompts builder — fill in the fields, get a polished prompt in seconds, and copy it with one click.

47s
Average time to create a production-ready prompt using SurePrompts templates — vs 5-10 minutes writing from scratch

Ready to Level Up Your Prompts?

Stop struggling with AI outputs. Use SurePrompts to create professional, optimized prompts in under 60 seconds.

Try SurePrompts Free