SQL Query Optimizer

Example Input

Goal: create a optimized sql + analysis for backend developers & data engineers
Audience: [describe who will read or use it]
Tone: [clear, practical, persuasive, friendly, formal]
Constraints: [word count, format, platform, examples, must-include points]

Example Output

Sample output:
- Problem summary: restate the bug or build goal in plain language
- Recommended approach: list the safest implementation steps
- Code or checklist: provide the draft solution with edge cases and testing notes

Useful Variations

• Make the output shorter and more actionable for backend developers & data engineers.
• Rewrite the answer for a beginner audience and include concrete examples.
• Turn the result into a checklist, table, or step-by-step workflow.

Customization Tips

• Add real names, examples, target platform, and desired length before running the prompt.
• Tell the model what a bad answer looks like so it avoids generic output.
• Ask for one revision focused only on accuracy, clarity, or conversion depending on your goal.

Best Model to Use

Use Claude, ChatGPT, or Gemini with a clear code context and expected output format.

Expected Output

• A structured optimized sql + analysis tailored to backend developers & data engineers.
• Clear sections, bullets, or steps that are easy to edit.
• A final answer that can be shortened, expanded, reformatted, or adapted for a specific platform.

Common Mistakes

• Running the prompt without replacing placeholders with real context.
• Asking for a final answer before defining audience, goal, tone, and constraints.
• Publishing the output without checking facts, examples, links, claims, or brand voice.