Prompt Engineering Cheatsheet

Quick-reference prompt patterns for clear tasks, context, constraints, output formats, revision, and verification.

By Chat Overview Published Updated
Reusable prompt
Context
Task
Limits
Format
Use the pattern
  • Copy
  • Adapt
  • Check

How to use this sheet

Copy a pattern, replace its subject and constraints, then check the response. Start with Prompting 101 for the basic method and Prompting 102 for revision and verification.

General strategies

  • Be specific: Define the task, length, and format.
  • Provide context: Assign roles or background.
  • Structure the output: Request bullet points, steps, or JSON.
  • Iterate: Refine prompts based on results.

Prompt patterns

Role prompting

  • "Act as a cybersecurity analyst. Summarize the top 3 risks in this report."

Format control

  • "List the steps as bullet points."
  • "Return the answer in JSON: {title, summary, tags}."

Assumptions and key steps

  • "State all assumptions and summarize the important steps before the final answer."

Few-shot examples

  • "Translate the following sentences to French. Example: 'Hello' -> 'Bonjour'. Now: 'Good night' -> ?"

Constraints

  • "Write a 150-word summary, professional tone, suitable for executives."

Reusable templates

Summarization

"Summarize the following text in 5 bullet points, each under 15 words."

Comparison

"Compare technology A and B in a table with columns: Feature, A, B."

Explanation

"Explain [concept] as if to a beginner, using analogies and a simple example."

Brainstorming

"Generate 10 creative ideas for [topic], grouped into categories."

Editing

"Rewrite the following paragraph in a more concise, persuasive style."

Common fixes

  • Too vague? -> Add role, context, or output format.
  • Too long? -> Set a word limit.
  • Disorganized? -> Request numbered lists or sections.
  • Unsupported facts? -> Require primary sources or mark the claims as unverified.

Quick checks

  • The task and intended audience are explicit.
  • Context contains only facts relevant to the answer.
  • Constraints do not conflict.
  • The output format can be checked.
  • Important claims have an independent verification method.