Prompt Engineering

Prompt Engineering

Write prompts that get reliable, high-quality output from LLMs.

Core Principles

1. Be specific — vague prompts get vague results 2. Show, don't tell — examples beat instructions 3. Structure the output — tell the model exactly what format you want 4. Iterate — prompts are code; test and refine them

Techniques

System Prompts

Set the model's role and constraints:

You are a senior code reviewer. Review the provided code for:
1. Security vulnerabilities
2. Performance issues
3. Readability problems

For each issue found, provide:
- Severity (critical/warning/info)
- Line number
- Description
- Suggested fix

If no issues are found, respond with "No issues found."

Few-Shot Examples

Provide 2-3 examples of input → output:

Convert the user's natural language query to a SQL query.

Example 1:
Input: "How many users signed up last month?"
Output: SELECT COUNT(*) FROM users WHERE created_at >= DATE_TRUNC('month', NOW() - INTERVAL '1 month') AND created_at < DATE_TRUNC('month', NOW());

Example 2:
Input: "Show me the top 5 products by revenue"
Output: SELECT p.name, SUM(o.amount) as revenue FROM products p JOIN orders o ON o.product_id = p.id GROUP BY p.name ORDER BY revenue DESC LIMIT 5;

Now convert this query:
Input: "{user_query}"
Output:

Chain-of-Thought

Ask the model to reason step by step:

Analyze this error and suggest a fix. Think step by step:
1. What does the error message mean?
2. What could cause this error?
3. What is the most likely root cause given the code context?
4. What is the fix?

Structured Output

Request JSON or a specific format:

Respond with a JSON object matching this schema:
{
  "summary": "string - one sentence summary",
  "sentiment": "positive | negative | neutral",
  "key_topics": ["string"],
  "confidence": 0.0-1.0
}

Constraints and Guardrails

Rules:
- Only use information from the provided context
- If you don't know the answer, say "I don't know" — do not guess
- Keep responses under 200 words
- Do not include any PII in your response

Patterns for Code

Code generation:

Write a TypeScript function that {description}.

Requirements:
- {requirement 1}
- {requirement 2}

Use these libraries: {libraries}
Follow this pattern from the codebase: {example}

Code transformation:

Refactor this code to {goal}. Keep the same behavior.
Do not change the public API (function signatures, exports).

Bug fixing:

This code has a bug: {description of bug}

Error: {error message}

Fix the bug. Explain what caused it in a comment.

Anti-Patterns

• Too vague: "Make this better" → Be specific about what "better" means
• Too long: Giant prompts with everything → Split into focused prompts
• Contradictory: "Be concise but thorough" → Pick one or define the tradeoff
• No examples: Complex formatting without showing what you want → Add 1-2 examples
• Prompt injection risk: Including raw user input without delimiting → Use clear delimiters like <user_input>...</user_input>

Tips

• Temperature 0 for deterministic tasks (code, classification), 0.7+ for creative tasks
• Test prompts with edge cases, not just the happy path
• Version control your prompts — they're as important as code
• Use structured output (JSON) when parsing the response programmatically
• Shorter prompts often outperform longer ones if they're precise enough