Home / Resources / Prompt library / AI coding & development
Prompt library · By AI task
12 detailed, ready-to-use prompts: code, debugging, reviews and documentation with AI assistants. Each prompt explains when to use it, what to replace and an expert tip. They work with ChatGPT, Claude, Gemini, Copilot and other assistants.
When to use it: Plan a feature before coding.
Write a technical specification for [feature] in [stack]. Include user stories, acceptance criteria, data model changes, API endpoints, edge cases, security considerations and a step-by-step implementation plan. Ask me questions if requirements are unclear.
When to use it: Find the cause of a bug.
Help me debug this issue. Expected behaviour: [expected]. Actual behaviour: [actual]. Error message: [paste]. Relevant code: [paste]. What I tried: [list]. List the most likely causes in order, how to confirm each, and the fix.
When to use it: Review code before merging.
Review this code for correctness, security, performance, readability and tests: [paste]. List issues by severity with line references and suggested fixes. Then list what is done well.
When to use it: Add tests to existing code.
Write unit tests for this function in [test framework]: [paste]. Cover normal cases, edge cases and error handling. Explain what each test checks.
When to use it: Improve code without changing behaviour.
Refactor this code to improve readability and maintainability without changing behaviour: [paste]. Explain each change. Keep the public interface unchanged.
When to use it: Understand a codebase quickly.
Explain what this code does, step by step, for a developer new to the project: [paste]. Include the data flow, key functions, dependencies, and anything risky or unclear.
When to use it: Write and optimise queries.
Using this database schema [paste], write a SQL query that [goal]. Explain the query, add indexes that would help, and note any performance concerns.
When to use it: Document endpoints clearly.
Write API documentation for these endpoints: [paste code or routes]. For each: purpose, method, URL, parameters, request example, response example, errors and authentication.
When to use it: Build and test a regular expression.
Write a regular expression in [language] that matches [pattern]. Should match: [examples]. Should not match: [examples]. Explain each part and give test cases.
When to use it: Communicate changes clearly.
Write a commit message and a pull request description for these changes: [diff or summary]. Include context, what changed, how to test and any risks.
When to use it: Upgrade a library or framework.
Create a migration plan from [old version/tool] to [new]. List breaking changes to check, steps in order, tests to run, rollback plan and estimated effort.
When to use it: Check common vulnerabilities.
Review this code or design for common security issues (input validation, authentication, authorisation, secrets, injection, data exposure): [paste]. List risks and fixes. Do not output any secrets.
No prompt matches. Try another word.
More prompt categories
Go further
The Business Launch System helps you test it and set it up. The Self-Funding Client System helps you find clients. Both are fill-in Word systems.
