AI Prompts for Developers

Write a [LANGUAGE] function that does the following: [DESCRIBE BEHAVIOR IN PLAIN ENGLISH]. Requirements: [LIST ANY CONSTRAINTS, E.G. MUST HANDLE NULL INPUT, MUST NOT USE LIBRARY X, MUST RUN IN O(N) TIME]. Include the function, a brief explanation of the approach, and three test cases covering the happy path and two edge cases.

Refactor this code to be cleaner and more readable without changing its behavior. Improve variable and function names, break up long functions, remove duplication, and add comments only where the logic is genuinely non-obvious. Show me the refactored version and explain the three most significant changes you made: [PASTE CODE]

Convert this pseudocode or description into working [LANGUAGE] code: [PASTE PSEUDOCODE OR DESCRIPTION]. The code should handle edge cases including [LIST EDGE CASES], follow the conventions of [FRAMEWORK OR CODEBASE STYLE IF KNOWN], and include inline comments for any logic that is not immediately obvious.

Write a [LANGUAGE/FRAMEWORK] API endpoint for [DESCRIBE THE ENDPOINT PURPOSE]. It should: accept [DESCRIBE INPUT FORMAT AND VALIDATION], perform [DESCRIBE BUSINESS LOGIC], return [DESCRIBE RESPONSE FORMAT], and handle [DESCRIBE ERROR CASES]. Include the route handler, input validation, error handling, and a brief description of the response schema.

Write unit tests for the following function in [LANGUAGE/TESTING FRAMEWORK]: [PASTE FUNCTION]. Cover: the happy path with typical inputs, edge cases including [LIST SPECIFIC CASES], error cases where the function should throw or return an error, and any boundary conditions. Each test should have a clear, descriptive name.

Here is an error and stack trace: [PASTE ERROR AND STACK TRACE]. Explain what this error means in plain language, where it is originating, and the most likely causes ranked by probability. For the top two causes, tell me exactly what to check first.

My code is supposed to [DESCRIBE EXPECTED BEHAVIOR]. Instead it is [DESCRIBE ACTUAL BEHAVIOR]. Here is the relevant code: [PASTE CODE]. Walk through what the code actually does step by step and identify the exact point where the behavior diverges from my intention.

Here is a bug in my code: [DESCRIBE THE BUG]. Here is the current code: [PASTE CODE]. Write a fix that addresses the root cause without breaking other functionality. Explain what was wrong, why your fix addresses it, and what other code paths I should test to confirm nothing else broke.

I have an intermittent bug that does not reproduce consistently. What I know: [DESCRIBE SYMPTOMS, FREQUENCY, AND CONDITIONS]. The code in the area I suspect: [PASTE CODE]. What are the most common causes of intermittent bugs like this? What logging or assertions should I add to capture more information the next time it occurs?

I keep fixing this bug but it comes back in different forms. The symptom is: [DESCRIBE SYMPTOM]. The fixes I have tried: [LIST FIXES]. Help me identify the root cause rather than the symptom. What structural issue in the code keeps producing this class of bug, and how do I eliminate it at the source?

Review this code for security vulnerabilities including SQL injection, XSS, CSRF, insecure direct object references, hardcoded credentials, and missing input validation. For each issue, explain the attack vector, the severity, and the specific fix: [PASTE CODE]

Review this code for performance issues: unnecessary loops, repeated computations, N+1 queries, blocking operations, or memory leaks. For each issue, estimate the impact at scale and write the optimized version: [PASTE CODE]

Review this code for maintainability problems: unclear naming, functions doing too much, excessive coupling, missing abstractions, and anything that will make this hard to modify in six months. Suggest specific refactors with reasoning: [PASTE CODE]

I am about to submit a pull request for [DESCRIBE CHANGES]. Run a pre-submission checklist covering: correctness and edge cases, security implications, performance at scale, test coverage, documentation, and anything a reviewer is likely to flag. Tell me what I should fix before submitting.

I need to flag this issue in a code review: [DESCRIBE ISSUE]. The code is: [PASTE CODE]. Write a review comment that explains the problem, the reason it matters, and suggests the fix. The developer is [JUNIOR/SENIOR/PEER]. The comment should be specific and constructive, not vague or harsh.

Write clear documentation for the following code. Include: a plain-language description of what it does, the parameters with types and valid values, the return value and structure, error cases and what triggers them, and one usage example: [PASTE FUNCTION OR API ENDPOINT]

Write a technical onboarding explanation for a new developer joining this project. Based on this code section: [PASTE CODE]. Explain: what this module or service does, how data flows through it, the key design decisions and why they were made, and the most important things a new developer needs to understand before making changes.

I need to add [DESCRIBE FEATURE] to an existing [DESCRIBE SYSTEM]. The current architecture is: [DESCRIBE OR PASTE RELEVANT PARTS]. Propose an architecture for this feature covering: where the logic should live, what new components or tables are needed, how it integrates with existing code, and what the main technical risks are.

Write a technical design document for [DESCRIBE FEATURE OR SYSTEM]. Include: problem statement, proposed solution overview, data model or schema changes, API or interface design, key technical decisions and alternatives considered, risks and mitigations, and a rough implementation plan. Audience is the engineering team.

Write a clear commit message and pull request description for the following change: [DESCRIBE WHAT YOU CHANGED AND WHY]. The PR description should cover: what changed, why it was needed, how to test it, and any migration steps or breaking changes. The commit message should follow [CONVENTIONAL COMMITS / YOUR PROJECT'S CONVENTION].