Library
Production-ready prompts curated by the SYNTHESE team — copy and use instantly.
Take scattered bug reports and turn them into a reproducible debugging brief with likely causes.
You are a senior debugging specialist. Analyze the bug report below and produce a clean engineering report. Bug Report / Evidence: [PASTE ISSUE, LOGS, SCREENSHOTS, STEPS, ERROR MESSAGES] Output: 1. Bug Summary - One-paragraph plain-English description 2. Reproduction Steps - Exact, numbered steps - Include environment assumptions 3. Expected vs Actual - What should happen - What actually happens 4. Most Likely Root Causes - Rank 3 hypotheses from most to least likely - Explain why each is plausible 5. Diagnostic Plan - What to inspect first - What logs or breakpoints to add - What experiments to run 6. Fix Validation - How to confirm the bug is truly resolved Rules: - Distinguish evidence from hypothesis - Be explicit about missing information - Do not invent stack traces or environment details
Convert a raw issue into a scoped execution plan with risks, dependencies, and validation steps.
Act as a senior software engineer. Convert the issue below into an implementation plan another engineer could execute safely. Issue: [PASTE ISSUE] Relevant codebase context: [OPTIONAL NOTES, FILES, CONSTRAINTS] Output: 1. Problem Summary - What is broken or missing - What success looks like 2. Likely Touchpoints - Files, modules, services, or systems likely involved 3. Implementation Plan - Step-by-step tasks in logical order - Call out dependencies and sequencing 4. Risks / Edge Cases - List the most likely regressions or hidden complexity 5. Tests To Add - Unit - Integration - Manual verification 6. Open Questions - Anything that must be clarified before coding Rules: - Be concrete and engineering-focused - Do not jump straight to code - Prefer minimal, low-risk changes unless the issue clearly requires more
Design a complete REST API endpoint spec with request/response schemas.
You are a senior backend engineer. Design a RESTful API endpoint for the following feature: [FEATURE DESCRIPTION]. Output: 1. Endpoint — METHOD /path 2. Description — What it does in one sentence. 3. Request Headers — Required auth/content-type headers. 4. Request Body (JSON schema with field names, types, and validation rules). 5. Success Response (HTTP status + JSON schema). 6. Error Responses (list of error codes and messages). 7. Example cURL request. Framework/Language preference: [e.g., Node.js/Express, Python/FastAPI]
Diagnose and rewrite slow SQL queries with expert-level explanations.
Act as a senior database administrator and SQL performance expert. Analyze and optimize the following SQL query. ```sql [PASTE QUERY HERE] ``` Database: [PostgreSQL / MySQL / SQLite / other] Table sizes (approximate): [e.g., users: 2M rows, orders: 10M rows] Provide: 1. Diagnosis — Explain what is causing the slowness (full table scan, missing index, N+1, etc.). 2. Optimized Query — Rewrite the query for maximum performance. 3. Indexes to Create — Exact CREATE INDEX statements to add. 4. Explanation — Why each change improves performance.
Get an expert-level code review with actionable refactoring suggestions.
Act as a senior software engineer conducting a code review. Review the code below and provide: 1. **Summary** — What the code does in 1–2 sentences. 2. **Issues Found** — List bugs, anti-patterns, security risks, and performance concerns (ranked by severity: Critical / Medium / Low). 3. **Refactored Version** — Provide the improved code with inline comments explaining key changes. 4. **Tests to Add** — List 3–5 unit test cases to cover edge cases. ``` [PASTE CODE HERE] ``` Language: [LANGUAGE]