Coding prompts

Ship better code, faster

15 prompts · Build

• Catch the problems in a PR before they reach productionA code review checklist covering correctness, security, performance, readability, and edge cases — so reviews are thorough, not a rubber stamp.
• Choose the right stack for what you're actually buildingA technology comparison that evaluates options against your specific constraints — team experience, scale requirements, ecosystem, and long-term maintenance cost.
• Clean up the code you're embarrassed byRefactoring guidance for messy functions — naming, structure, side effects, and testability — that makes the code easier to read, change, and trust.
• Document the technical decision so future-you understands whyAn Architecture Decision Record that captures context, options considered, the decision made, and the trade-offs — so the next person doesn't relitigate it from scratch.
• Find the bottleneck before your users find it for youA performance optimisation brief that profiles, identifies the real constraint, and prioritises the changes with the best effort-to-improvement ratio.
• Find the vulnerability before someone finds it for youA security review checklist covering input validation, authentication, authorisation, secrets management, and the OWASP top 10 — before the audit does.
• Handle failures in a way that doesn't leave users or systems strandedError handling design that covers the user experience, the logging, the alerting, and the recovery path — for every failure mode that matters.
• Plan the database migration that doesn't take the site downA migration planning brief with the steps, the rollback plan, the test strategy, and the monitoring that tells you it worked — before you run it in production.
• Set up the branching strategy that doesn't create merge hellA Git workflow and branching strategy designed for your team size and release cadence — with the conventions that keep the history clean and deployments predictable.
• Stop guessing at what's broken and find it systematicallyA debug methodology that works from symptoms to hypotheses to evidence — so you spend less time guessing and more time closing in on the actual cause.
• Test the thing you shipped without tests and stop losing sleepA test-writing process for untested code that starts with the highest-risk paths and gives you coverage you can rely on without rewriting everything.
• Walk into the system design interview knowing what they're actually testingSystem design interview prep that covers the canonical problems, the evaluation criteria interviewers use, and how to structure your answer to show both breadth and depth.
• Walk into the technical interview having already solved the hard problemsTechnical interview preparation covering data structures, algorithms, system design, and behavioural questions — with the framework for thinking out loud under pressure.
• Write the docs developers actually want to readAPI documentation that covers endpoints, parameters, errors, and examples — written the way developers use docs, which is nothing like how they're usually written.
• Write the README that makes people want to use your projectREADME writing that covers setup, usage, contribution, and the 'why this exists' — clear enough that a new user can get started without asking you anything.

All prompt categories · Prompt libraries you can download