Prompt Engineering: Complete Guide to Techniques, Templates, and Examples (2026)

Most people use one prompting style for everything: one paragraph of instructions and hope for the best. The AI community has tested and documented eight distinct techniques that each unlock different model capabilities. Knowing when to use each one is the core skill.

Chain-of-thought is the single most impactful technique for any task involving logic, steps, or calculations. Adding "think through this step by step before answering" to a reasoning question typically improves accuracy by 20-40% in community tests, because it forces the model to surface its reasoning rather than jumping to a conclusion.

Role prompting works because AI models have internalized vast amounts of domain-specific writing. Assigning a persona activates that domain knowledge and shifts the vocabulary, tone, and depth of the response automatically.

"I spent three months trying to figure out why some prompts worked better than others. The answer was almost always: did I give it a role and a format, or did I just ask the question?" — r/PromptEngineering, u/systematic_prompts (1,240 upvotes, 2025)

System prompts are the highest-leverage investment you can make. Spending 20 minutes writing a good system prompt for a recurring task type saves hours of re-prompting every session. The best system prompts define: persona, constraints, output format, tone, and examples of good vs bad output.

Writing prompts follow a consistent structure that the r/ChatGPT community has refined over two years. The template is: role + context + specific task + output format + constraints.

These are the most upvoted and copied writing prompt formats in the community:

Role-assigned email writer:

"You are a professional business writer. Write a follow-up email to [client name] after our meeting about [topic]. Tone: direct and friendly. Length: 3 paragraphs max. Include: a specific next step and a clear call-to-action. Do not use filler phrases like 'I hope this email finds you well'."

Blog post outline generator:

"You are an SEO content strategist. Create a blog post outline for the topic: [topic]. Target audience: [describe audience]. Include: H1 title, 5-7 H2 sections with 2-3 bullet points each, and a meta description under 160 characters. Focus on practical advice over theory."

Social media caption batch:

"Write 5 Instagram captions for a [product/service] post. Each caption: 2-3 sentences, one clear call-to-action, 3-5 relevant hashtags. Tone: [casual/professional/inspirational]. Vary the opening line of each caption."

Long-form article first draft:

"Write a 1,200-word article on [topic]. Structure: introduction (hook + thesis), 3 main sections with 2 supporting points each, practical examples in each section, conclusion with key takeaway. Tone: authoritative but accessible. No jargon. Write for someone with no prior knowledge of the topic."

The negative constraint that most improves writing outputs is this addition at the end of any writing prompt:

"Do not start with 'In today's', 'In the world of', or 'Whether you are'. Do not use em dashes. Do not use the words: leverage, streamline, delve, or unlock. Write in active voice throughout."

"The single prompt that transformed my email workflow: 'You are a direct communicator. Write this email. Max 150 words. One ask per email. No pleasantries.' My reply rate went up 30%." — r/ChatGPT, u/email_efficiency (890 upvotes, 2025)

Coding prompts work best when you specify the language, context, constraints, and expected output format together. Vague coding prompts produce vague code. The developer communities in r/programming (6M+ members) and r/learnprogramming (5M+ members) have settled on these templates.

Code generation with context:

"You are a senior [Python/JavaScript/TypeScript] developer. Write a function that [specific task]. Requirements: [list requirements]. Constraints: no external libraries, must handle edge cases for [X], include error handling. Return: the function with inline comments explaining non-obvious logic. Do not include example usage."

Code review:

"Review this [language] code for: 1. Security vulnerabilities, 2. Performance issues, 3. Code style and readability, 4. Missing error handling. Format your response as a numbered list sorted by severity (critical, moderate, minor). For each issue: describe the problem, explain why it matters, and provide the fixed code snippet."

Bug debugging:

"I have a bug in my [language] code. Error message: [paste error]. Code: [paste code]. Expected behavior: [describe]. Actual behavior: [describe]. Explain the root cause in plain language, then provide the corrected code."

SQL query writing:

"Write a SQL query to [specific task]. Table structure: [describe tables and columns]. Return: only rows where [condition]. Sort by [column]. Limit to [N] results. Explain the JOIN logic in one sentence before the query."

The chain-of-thought pattern for debugging is particularly effective:

"Before giving me the fix, explain step by step how this code executes, what should happen at each step, and where the execution deviates from expected behavior."

"Chain-of-thought changed debugging for me. 'Walk through what this function does line by line, then tell me where it breaks' finds bugs that 'fix this code' never catches." — r/learnprogramming, u/debug_flow (2,100 upvotes, 2024)

Business prompts need three things that generic prompts miss: a defined audience, a specific deliverable, and a use-case constraint. These templates are drawn from r/marketing (1.4M members), r/Entrepreneur (2M members), and r/SEO communities.

Competitor analysis:

"You are a senior marketing analyst. Analyze [competitor name] based on: their value proposition, target customer segment, main differentiators vs [your company], and potential weaknesses. Format as a 2-column comparison table: their strengths vs opportunities for us. Base your analysis on publicly observable information only."

Job description writer:

"Write a job description for a [role title] at [company type]. Required skills: [list]. Responsibilities: [list]. Tone: [professional/startup-casual]. Include: salary range placeholder, clear seniority level, 3 bullet points on company culture. Do not use the words: ninja, rockstar, guru, or passionate."

Marketing copy framework:

"Use the PAS framework (Problem, Agitate, Solution) to write marketing copy for [product/service]. Target customer: [describe]. Their main pain point: [describe]. Word count: 150 words max. Include a specific call-to-action. Avoid generic benefits. Focus on the specific outcome the customer achieves."

Research summary:

"Summarize this research for a non-specialist audience. Focus on: 1. The main finding in one sentence, 2. Why it matters practically, 3. What uncertainty remains, 4. What action it suggests. Avoid jargon. If you cannot explain a term simply, define it in parentheses."

SWOT analysis:

"Create a SWOT analysis for [business/project] in [industry]. Format as a 4-quadrant table. Each quadrant: 5 specific points, not generic statements. Strengths and weaknesses: internal factors only. Opportunities and threats: external market factors only."

"Adding 'your output will be presented to the CEO, so be concise and specific' to business prompts eliminates filler completely. The model adjusts its style based on the stated audience." — r/Entrepreneur, u/prompt_stack (740 upvotes, 2025)

Image AI prompts follow a completely different structure from text prompts. The r/midjourney (600K+ members) and r/StableDiffusion (600K+ members) communities have developed specific formulas for different image types. The core structure for Midjourney and DALL-E is: subject, style, technical specs, mood/atmosphere, negative elements.

The Midjourney formula that the community uses:

"[Subject description], [art style or medium], [lighting type], [mood], [camera/perspective], [color palette] -- ar [aspect ratio] --v 6.1"

Portraits and characters:

"Portrait of [character description], [age and features], photographed on [camera type], [lighting style] lighting, shallow depth of field, sharp eyes, [color palette], editorial photography style --ar 2:3 --v 6.1"

Product photography:

"[Product name] on [surface], [background description], soft studio lighting, commercial photography, clean white background, product shot, professional, 8k --ar 1:1 --v 6.1"

Architecture and spaces:

"Interior of [space type], [design style] architecture, natural daylight, warm tones, photographed by [famous architectural photographer style], editorial, sharp focus --ar 16:9 --v 6.1"

Logo and brand design:

"Minimalist logo for [company/brand], [industry], vector design, [primary color] palette, clean lines, modern, simple, white background --ar 1:1 --v 6.1 --style raw"

Negative prompting for Stable Diffusion (prevents common generation flaws):

"Negative: blurry, deformed, extra limbs, bad anatomy, watermark, text, low quality, grainy, oversaturated, distorted proportions, missing fingers, disfigured"

DALL-E 3 responds better to natural language than Midjourney. The best DALL-E 3 prompt structure is a detailed paragraph describing the scene rather than comma-separated terms:

"A photograph of [subject], in the style of [reference style], with [lighting description]. The scene shows [atmosphere/mood]. Shot on [camera style]. The [specific detail that matters most]."

"The single biggest improvement to Midjourney prompts: add the photographer or artist you want it to reference. 'In the style of Annie Leibovitz' does more than 50 technical words." — r/midjourney, u/prompt_lab (3,400 upvotes, 2025)