Back to Blog
AI Development9 min read

How to Write Good Prompts: The Ultimate Guide

ByFirstVoid Team
How to Write Good Prompts: The Ultimate Guide

Introduction

The difference between a mediocre AI output and an exceptional one often comes down to one thing: the prompt. Good prompts are a skill, and like any skill, they can be learned.

Let's master prompt engineering together.

Prompt Engineering

The Prompt Formula

Every great prompt follows this structure:

Role + Task + Context + Output Format + Constraints

Let's break it down:

1. Role

Tell the AI who to be:
  • "You are a senior React developer"
  • "Act as a marketing copywriter"
  • "You are a helpful coding assistant"

2. Task

What you want done:
  • "Build a responsive navbar"
  • "Write a product description"
  • "Debug this function"

3. Context

Background information:
  • "This is for an e-commerce site"
  • "The target audience is developers"
  • "We're using Next.js 15"

4. Output Format

How you want the response:
  • "Return only code, no explanations"
  • "Use bullet points"
  • "Provide a step-by-step guide"

5. Constraints

Limitations and requirements:
  • "Keep it under 100 words"
  • "Use TypeScript"
  • "Don't use external libraries"

Formula in Action

Example 1: Code Generation

Bad Prompt:
Make a navbar
Good Prompt:
You are a senior React developer.

Build a responsive navigation bar with the following requirements:

  • Logo on the left
  • Navigation links in the center (Home, About, Services, Contact)
  • CTA button on the right
  • Mobile hamburger menu for screens under 768px
  • Use Tailwind CSS for styling
  • Add smooth hover animations
Return only the code, no explanations.

Example 2: Content Writing

Bad Prompt:
Write about AI
Good Prompt:
You are a tech journalist writing for a developer audience.

Write a 300-word introduction about AI agents in 2026. Cover:

  • What AI agents are
  • Why they matter now
  • One real-world example
Tone: Professional but accessible Format: Start with a hook, use short paragraphs Avoid: Jargon without explanation, hype language

Example 3: Code Review

Bad Prompt:
Review this code
Good Prompt:
You are a senior software engineer conducting a code review.

Review the following code for:

  • Bugs and potential errors
  • Performance issues
  • Security vulnerabilities
  • Code style and readability
  • For each issue found:

    • Describe the problem
    • Explain why it matters
    • Provide the fixed code
    Code to review: [paste code here]

    Writing Prompts

    Advanced Techniques

    Chain of Thought

    Ask the AI to think step by step:

    Solve this problem step by step, showing your reasoning at each stage:
    [problem]
    

    Few-Shot Learning

    Provide examples of what you want:

    Convert these sentences to formal English:
    
    

    Input: "gonna grab some coffee" Output: "I am going to get some coffee"

    Input: "wanna help me out?" Output: "Would you be willing to assist me?"

    Input: "this is kinda cool" Output:

    Self-Consistency

    Ask for multiple approaches:

    Provide 3 different solutions to this problem, then recommend the best one with reasoning.
    

    Structured Output

    Request specific formats:

    Return your response as JSON with this structure:
    {
      "summary": "brief overview",
      "pros": ["list of advantages"],
      "cons": ["list of disadvantages"],
      "recommendation": "final suggestion"
    }
    

    Common Mistakes to Avoid

    1. Being Too Vague

    ❌ "Make it better" ✅ "Improve the readability by adding comments and breaking down the large function into smaller ones"

    2. Overloading the Prompt

    ❌ Asking for 10 things at once ✅ Break into multiple focused prompts

    3. Forgetting Context

    ❌ "Add authentication" ✅ "Add JWT authentication to this Express.js API. We're using MongoDB for the database."

    4. Not Specifying Format

    ❌ "Explain React hooks" ✅ "Explain React hooks in 5 bullet points, each with a code example"

    Quick Reference Cheat Sheet

    ElementPurposeExample
    RoleSets expertise level"You are a senior developer"
    TaskDefines the goal"Create a login form"
    ContextProvides background"For a banking app"
    FormatStructures output"Return as TypeScript"
    ConstraintsSets limits"Under 50 lines"

    Templates You Can Use

    For Code:

    You are a [role].
    [Task description]
    Tech stack: [technologies]
    Requirements: [list]
    Return: [format]
    

    For Writing:

    You are a [role] writing for [audience].
    Write a [type] about [topic].
    Length: [word count]
    Tone: [style]
    Include: [elements]
    Avoid: [restrictions]
    

    For Analysis:

    Analyze the following [thing] for:
    
  • [Aspect 1]
  • [Aspect 2]
  • [Aspect 3]
  • For each finding, provide:

    • The issue
    • Why it matters
    • Suggested improvement
    [Content to analyze]

    Conclusion

    Great prompts are:

    • Specific: Say exactly what you want
    • Structured: Use the formula
    • Contextual: Provide background
    • Formatted: Define the output
    Practice with the templates, iterate on your prompts, and watch your AI outputs improve dramatically.


    What prompt techniques work best for you? Share in the comments!

    Tags

    Prompt EngineeringAIChatGPTClaudeBest Practices
    Share this article