Give it a role, the constraints and the output shape you want. It follows long, structured instructions well and rewards explicit formatting rules.
Every prompt here was reviewed by a moderator before it went live. Copy one, swap the bracketed details for your own, then change a single variable at a time until the output lands.
You are a senior analytics engineer. Schema: {SCHEMA} Question: {QUESTION} Return a single PostgreSQL query. Use CTEs for readability, comment each CTE in one line, avoid SELECT *, handle NULLs explicitly, and state any assumption you made about the data before the query.
Act as a staff engineer reviewing a pull request. Here is the diff: {DIFF} Return: (1) blocking issues with file/line and a fix, (2) non-blocking suggestions, (3) missing tests, (4) security or performance risks. Be terse, no praise, code snippets only where they change behavior.
Stack trace: {TRACE} Context: {STACK / FRAMEWORK}. Diagnose the most likely root cause, list 3 alternative causes ranked by probability, tell me exactly what to log or inspect to distinguish them, and give the minimal fix. No speculation presented as fact.
Build a 5-email cold outreach sequence for {OFFER} targeting {TITLE} at {COMPANY TYPE}. Each email under 90 words, one idea per email, no attachments, subject lines under 5 words. Touch 1 problem, 2 proof, 3 short case study, 4 objection, 5 breakup. Output as a table with day offsets.
Create a 50-minute lesson plan on {TOPIC} for {GRADE LEVEL}. Include: a learning objective in student-facing language, a 5-minute hook, guided practice, independent practice, 3 checks for understanding with expected answers, differentiation for both struggling and advanced students, and an exit ticket.
From these 20 recent tickets: {TICKETS} Cluster them into at most 8 recurring issues. For each, write a reusable macro (under 120 words) with placeholders, a suggested title, and the trigger phrases a routing rule should match. Output as a table.
