AI Prompts for ChatGPT for Coding

Before writing any code, I want to make sure we understand the problem fully. Here is what I am trying to build: [DESCRIBE THE FEATURE OR SYSTEM]. Ask me up to five clarifying questions about requirements, constraints, and edge cases before proposing any solution. I want to have a clear spec before we touch code.

I need to implement [DESCRIBE FEATURE] in [LANGUAGE/FRAMEWORK]. Give me three different implementation approaches, ranging from simplest to most robust. For each approach, describe: the core technique, the trade-offs, which scenarios it is best suited for, and an estimated complexity. I will choose one before you write any code.

Before writing any functions or logic, help me design the data model for [DESCRIBE SYSTEM]. Propose the types, interfaces, or schema I will need. Flag any design decisions that will be hard to change later. Do not write implementation code yet, just the data structures and types.

I want to build [DESCRIBE FEATURE]. Before writing real code, write the implementation as a series of inline comments that describe exactly what each section will do. No actual code yet, just the skeleton with comments. Once I approve the plan, we will fill in each section.

I am about to build [DESCRIBE FEATURE]. Before I start, list the ten most common failure modes, gotchas, and edge cases for this type of implementation in [LANGUAGE/FRAMEWORK]. For each one, suggest how to handle it. This will inform how I structure the code.

Write a function to [DESCRIBE WHAT IT SHOULD DO]. Constraints: language is [LANGUAGE], version [VERSION]. Framework is [FRAMEWORK]. Existing code it needs to integrate with: [PASTE RELEVANT CODE OR DESCRIBE INTERFACES]. Follow these style conventions: [CONVENTIONS]. Include error handling for [SPECIFIC CASES].

Write only the [FUNCTION NAME] function. It should: take [INPUTS] and return [OUTPUTS]. It will be called by [CALLING CONTEXT]. Edge cases to handle: [LIST]. Do not write the full module, just this one function with its type signatures and inline comments for non-obvious logic.

Write a complete, runnable example of [DESCRIBE FEATURE] using [LANGUAGE/FRAMEWORK]. Include: all imports, realistic sample data, and a main function or entry point I can run immediately. Do not use placeholder comments like "// add your logic here". Every section should be real, working code.

Convert this pseudocode into working [LANGUAGE] code. Keep the same logical structure but write idiomatic, production-quality code. Add proper error handling, type annotations, and comments for any non-obvious parts: [PASTE PSEUDOCODE].

Translate this [SOURCE LANGUAGE] code to [TARGET LANGUAGE/FRAMEWORK]. Preserve the logic exactly but use idiomatic patterns for the target language. Flag any places where a direct translation would be unidiomatic and explain what you changed and why: [PASTE CODE].

I have a bug I cannot track down. Here is the relevant code: [PASTE CODE]. Here is the error message in full: [PASTE ERROR]. Here is what I expected to happen: [DESCRIBE]. Here is what actually happened: [DESCRIBE]. I have already tried: [LIST WHAT YOU TRIED]. What is causing this and how do I fix it?

Explain this error message in plain language and tell me exactly what I need to do to fix it. Also tell me what kind of mistake usually causes it so I can avoid it in future: [PASTE ERROR MESSAGE AND STACK TRACE].

Read this code carefully and identify any bugs, logic errors, or edge cases that would cause incorrect behavior. Do not fix anything yet, just list what you find with the line numbers and a brief explanation of each issue. I will decide which ones to fix: [PASTE CODE].

Review this code for: (1) security vulnerabilities like injection, exposed secrets, or unsafe inputs; (2) performance issues like unnecessary loops, missing indexes, or memory leaks; (3) correctness issues like off-by-one errors, null handling, or race conditions. List findings with severity ratings: [PASTE CODE].

I applied this fix to my code and it worked, but I do not fully understand why. Explain exactly what was wrong before and why this change resolves it. I want to understand the underlying concept, not just copy the fix: [PASTE ORIGINAL CODE AND FIX].

Add inline comments and documentation to this code. Comment any logic that is not immediately obvious, add JSDoc or equivalent docstrings for each function, and add a brief header comment explaining what the module does. Do not over-comment obvious lines: [PASTE CODE].

Refactor this code to improve readability without changing its behavior. Rename variables and functions to be more descriptive, extract repeated logic into helper functions, simplify any overly complex conditionals, and break long functions into smaller ones. Show a diff of before and after: [PASTE CODE].

Write a README section for this module or function. Include: what it does, when to use it, the function signatures with parameter descriptions, return values, a usage example, and any important caveats or limitations: [PASTE CODE].

Write a comprehensive test suite for this function using [TEST FRAMEWORK, e.g. Jest / pytest / go test]. Include tests for: the happy path, each edge case, invalid inputs, and boundary conditions. Use descriptive test names that read like specifications: [PASTE FUNCTION CODE].

I am about to submit this code for review. Write a short summary I can include in the pull request description: what the code does, why it is structured this way, what trade-offs were made, and what a reviewer should focus on: [PASTE CODE].