💡 How to use these prompts:
Replace everything in [BRACKETS] with your specific details before sending.
Click Copy to copy any prompt to your clipboard instantly.
[QWEN3.7-MAX OR QWEN3.8-MAX — 1M CONTEXT WINDOW]
I am pasting a large codebase below. Read it in full before answering. Do not summarise what you have read — just confirm you have processed it, then answer my questions.
Questions:
1. [QUESTION 1 — e.g. Where is authentication handled and what library does it use?]
2. [QUESTION 2 — e.g. What happens when a database write fails?]
3. [QUESTION 3 — e.g. Which functions lack error handling?]
For each answer: cite the specific file and function. Do not guess — only answer from what you can see in the code.
Codebase: [PASTE ENTIRE CODEBASE — up to 1M tokens]
Write complete, production-ready code for the following specification. No stubs, no TODOs, no placeholder comments.
Spec: [DESCRIBE WHAT THE CODE SHOULD DO IN PLAIN ENGLISH]
Language / framework: [SPECIFY]
Dependencies already available: [LIST EXISTING LIBRARIES]
Error handling requirement: [DESCRIBE — e.g. log and retry / throw and let caller handle / return null on failure]
Tests required: [YES / NO — if yes, include them in the output]
Write the complete implementation. If you make assumptions about unspecified details, list them at the end.
[QWEN3.8-MAX-PREVIEW — multimodal, use for codebases with design docs or diagrams]
I am providing both a design document and the code that implements it. Identify where the implementation diverges from the design, and refactor the code to match.
Design document: [PASTE DOCUMENT OR UPLOAD IMAGE/PDF IF USING MULTIMODAL]
Current implementation: [PASTE CODE]
What must not change: [ANY BEHAVIOUR OR INTERFACE TO PRESERVE]
Output:
1. List of divergences found (design says X, code does Y)
2. The refactored code that matches the design
3. Any design document sections that are ambiguous or contradictory
Act as a debugging agent. Work through the following bug autonomously. Do not stop to ask for confirmation unless you reach a point where you genuinely need information I have not provided.
Bug report: [DESCRIBE WHAT IS FAILING AND HOW]
Error message: [PASTE FULL ERROR AND STACK TRACE IF AVAILABLE]
Code: [PASTE RELEVANT CODE]
Environment: [LANGUAGE, FRAMEWORK, OS, RELEVANT VERSIONS]
What I have already tried: [LIST WHAT HAS NOT WORKED]
Work through it step by step:
1. Diagnose the root cause
2. Implement the fix
3. Explain why the bug occurred
4. Add a test that would catch this class of bug in future
[QWEN3.8-MAX-PREVIEW — use multimodal input for architecture diagrams or design docs]
Review the following code against its specification and flag anything that does not match, could break, or introduces risk.
Specification / design doc: [PASTE OR UPLOAD]
Code to review: [PASTE CODE]
Focus areas: [E.G. — security / performance / correctness / maintainability — pick 1-2]
For each issue:
- What is wrong
- Why it matters
- The specific fix
Skip style preferences. Only flag things that will break, introduce risk, or contradict the specification.
Write the SQL query to answer the following question about my database. Output only the query and a brief explanation of what each part does.
Database type: [POSTGRESQL / MYSQL / MSSQL / SQLITE]
Schema: [PASTE RELEVANT TABLE DEFINITIONS OR DESCRIBE]
Question: [DESCRIBE WHAT YOU NEED THE QUERY TO RETURN IN PLAIN ENGLISH]
Performance requirement: [FAST RESPONSE ON X ROWS / BATCH OK / REAL-TIME]
Existing indexes: [LIST OR "UNKNOWN"]
After the query: tell me if any index would significantly improve performance and does not currently exist.