Coding Prompts
Code prompts with the constraints filled in — reviews, tests, refactors and debugging requests that come back runnable instead of chatty.
The strict review
Review this code like a strict but kind senior engineer: [CODE]. List issues as: blocker / smell / nit. Show the fixed version of each blocker. Do not rewrite what works.
Tests that actually bite
Write unit tests for: [CODE]. Cover the happy path, two edge cases, and one adversarial input. Use [FRAMEWORK]. Name each test after the behavior it pins.
Debug with hypotheses
I get this error: [ERROR] from this code: [CODE]. List three ranked hypotheses with the cheapest check for each, then the fix for the most likely one.
Refactor, behavior-locked
Refactor for readability without changing behavior: [CODE]. First list the behaviors you are preserving as bullet points, then the refactored code.
The migration plan
I need to migrate [SYSTEM A] to [SYSTEM B]. Ask me up to five questions about scale and constraints, then write a phased migration plan with a rollback point per phase.
Explain like a code walk
Walk me through this code as if pair-programming: [CODE]. One paragraph per block, plain words, flag the two lines a newcomer would trip on.
SQL under load
Write a PostgreSQL query for: [GOAL]. The table has [N] million rows — include the index you would add and explain the plan briefly.
API contract first
Design the API for [FEATURE]. Endpoints, methods, request/response shapes, error codes, and the one rate-limit rule that protects it. REST, JSON, no versioning debate.
The regex, decoded
Write a regex for [PATTERN], then decode it piece by piece in a table, then give three inputs it fails on.
Make it typed
Add full type hints/JSDoc to: [CODE]. Where a type is genuinely ambiguous, pick the safest and note it in a comment.
Performance triage
This is slow: [CODE]. Profile it by inspection: list where the time likely goes, ranked. Then the smallest change with the biggest win, and the version worth scaling later.
On-call handoff
Summarize this service for an on-call engineer: [CODE/README]. What breaks loudly, what breaks silently, where the logs live, and the first three commands to run.
Prefer to build your own?
The Coding Prompt Generator assembles a prompt from your subject and dropdown picks — same four-part structure, your brief.
Frequently asked questions
How do I use these prompts?
Copy one, swap everything in [BRACKETS] for your specifics, and paste it into your AI tool. The brackets are the only part you need to touch — the structure around them is the prompt.
Are these free to use?
Yes — copy them, edit them, use them at work, ship the outputs. No attribution, no license, no sign-up.