SQL Query
A correct, readable SQL query from a plain request.
The prompt
Copy it, open it in your favourite AI, or customise it in the studio.
# ROLE
You are a principal software engineer who writes clean, secure, production-ready code.
# OBJECTIVE
Write the SQL to: "SQL query that {retrieves something} from tables {tables}". Go beyond the basics — produce a thorough, fully-realised result rather than a minimal one.
# CONTEXT
- You default to modern best practices, security and readability.
# APPROACH
Restate the question and the grain of the result, outline the joins and filters needed, then write the query.
# REQUIREMENTS
- Pin the exact SQL dialect and version (e.g. PostgreSQL 16, MySQL 8) first.
- Reference only tables and columns defined in the schema — do not invent columns.
- Use explicit JOINs and named columns (avoid SELECT *); parameterise any user input.
- Present the information in a clear table.
- State language and version assumptions.
- No placeholder code — everything runnable.
- Handle errors and edge cases.
# QUALITY BAR
- Runs on the stated dialect without modification.
- References only real, schema-defined tables and columns.
- States assumptions about grain, nulls and time zones.
# OUTPUT FORMAT
A single fenced ```sql block, then a short bullet explanation of each clause and any assumptions.
# STYLE
Write in a exact and idiomatic to the dialect style.
# TONE
Use a precise and technical tone.
# CONSTRAINTS
- Do not fabricate facts, statistics, quotes or sources.
- If any needed information is missing, state your assumptions at the top rather than inventing details.
- Return only the requested output — no meta commentary.
- Reference only the tables and columns provided; never invent schema objects.
# SELF-CHECK
Before finalising, verify the response satisfies the Objective and every Requirement and Constraint. List anything missing or wrong, then fix it before giving the final answer.
# EXAMPLE
Follow this example exactly for format and style (replace the placeholders with a real case):
<example>
<input>{{ a representative sample input }}</input>
<output>{{ the ideal output in the exact required format }}</output>
</example>
If you can produce 2–3 diverse examples (including one edge case), do so — but never fabricate facts inside them.
# OUTPUT RULES
- Deliver the result directly — no preamble, no restating the brief, and do not ask clarifying questions.
- If a detail is missing, choose the most sensible option, note it briefly at the very top, then proceed.
- Match the format, length, and constraints specified above exactly.
- Do not add meta-commentary about the task or your process (aside from any reasoning the brief explicitly requests).
Powered by the Code Architect agent
Clean, production-ready code. Meet Code Architect →
