I use ChatGPT almost every day as part of my coding workflow. Over time, I’ve learned that how you ask is just as important as what you ask. If you're only typing vague prompts like “fix this code” or “write a Python function,” you're not really tapping into what ChatGPT can do.
With the right kind of prompt, ChatGPT becomes way more useful it can help you break down bugs, understand tricky codebases, write better tests, or even brainstorm full-stack solutions.
In this post, I’m sharing 20 prompts that I personally use. They’re not basic or generic. These are the kinds of prompts that actually help me work faster, debug smarter, and build with more confidence.
How I Get the Most Out of These Prompts
To really make these prompts work, I’ve found a few simple habits that help:
- Swap out placeholders like
[insert code here]
or[framework]
with your actual code or tools. - Be clear about what you want — whether it’s to fix, explain, clean up, or improve something.
- Give some context when it helps: what language you’re using, what framework, or what the code is for.
- Don’t be afraid to go back and forth. Sometimes a second or third prompt gives a way better answer.
If you treat ChatGPT like a code partner (not just a search engine), you’ll get way more useful results. For me, these prompts work best when:
- I share real code or describe the problem clearly
- I ask follow-up questions if the first answer isn’t quite right
- I mention things like frameworks, version numbers, or expected output
Each prompt below is ready to copy and use. Just plug in your code or idea, and adjust it as needed.
I. Code Generation & Scaffolding
1. Generate an Auth System Boilerplate
Prompt:
Build a basic authentication system in [framework] using [language]. It should support login, logout, session/token management, and user registration. Use secure password hashing and include input validation.
2. Create a CLI Tool Scaffold
Prompt:
Generate a command-line interface tool in [language] that accepts flags for [flag1], [flag2], and performs [task]. Add helpful error messages and usage hints.
3. API Endpoint with Validation
Prompt:
Write a REST API endpoint using [framework] that accepts a POST request with [fields]. Validate input, handle errors, and respond with appropriate status codes.
4. Code Generator for CRUD Operations
Prompt:
Generate the full CRUD logic for managing a [resource] in [framework]. Include model definition, controller methods, and route setup.
5. React Component with Props and State
Prompt:
Create a React component named [ComponentName] that receives props [prop1, prop2], maintains local state [state1], and updates state based on user input. Include type annotations if using TypeScript.
II. Code Debugging & Fix Suggestions
6. Spot and Fix a Bug
Prompt:
Here’s a snippet that isn’t working as expected:
[insert code]
Identify the bug, explain why it fails, and suggest a corrected version.
7. Error Message Explanation
Prompt:
I’m getting this error in [language/framework]:
[paste error message]
Based on this error and my stack, what’s likely causing it? Suggest at least one way to resolve it.
8. Unexpected Output Diagnosis
Prompt:
This function returns incorrect output:
[insert function code]
The expected result for input
[example input]
is[expected output]
, but I get[actual output]
. What might be wrong?
III. Code Review & Refactoring
9. Refactor for Readability and Best Practices
Prompt:
Refactor the following code to be more readable, modular, and aligned with [language] best practices. Avoid redundant code and suggest naming improvements:
[insert code]
10. Apply Design Patterns
Prompt:
Rewrite this code using the [pattern name] design pattern. Explain the benefits of this pattern in this context:
[insert code]
11. Convert Nested Logic into Smaller Functions
Prompt:
Break this deeply nested logic into separate reusable functions, while preserving functionality and reducing cyclomatic complexity:
[insert code]
IV. Learning & Documentation
12. Explain What This Code Does
Prompt:
Explain what this code does line-by-line. Include details on edge cases, performance bottlenecks, and suggest any improvements:
[insert code]
13. Create Developer Documentation
Prompt:
Document the following function with clear purpose, parameter details, return types, and usage example in Markdown format:
[insert function]
14. Explain a Concept With Examples
Prompt:
Explain the concept of [e.g. memoization, currying, event loop] in [language]. Include a short code example and discuss when and why to use it.
V. Testing & Test Writing
15. Generate Unit Tests
Prompt:
Write unit tests in [testing framework] for this function:
[insert function]
Cover edge cases, invalid input, and normal operation.
16. Convert Manual Test to Automated Test
Prompt:
I currently test this manually:
- Step 1: Open the app
- Step 2: Enter user input
- Step 3: Verify result
Convert this into an automated test in [framework].
VI. System Design & Architecture
17. Suggest a Scalable Architecture
Prompt:
I’m building a [type of app: e.g. real-time chat, e-commerce store]. Suggest a scalable architecture including frontend, backend, database, and any caching or queuing solutions. Use [cloud provider] as infrastructure.
18. Evaluate My Architecture
Prompt:
Here’s the current system design for my application:
[Describe the architecture]
Evaluate it for scalability, redundancy, and performance. Suggest improvements.
VII. DevOps & Scripting
19. Create a CI/CD Workflow
Prompt:
Generate a GitHub Actions workflow that:
- Runs tests on push
- Builds a Docker image
- Deploys to [hosting provider] on success
20. Bash Script for Environment Setup
Prompt:
Write a Bash script that installs [tools], sets up environment variables, and configures Git for a new developer machine.
Final Thoughts
These prompts are more than shortcuts they’re frameworks for thinking. Each one encourages you to give ChatGPT the right structure and context so you get code that actually works in production, not just toy examples.
Whether you’re generating, reviewing, or debugging code, mastering prompt engineering can dramatically accelerate your workflow. If you're serious about coding with AI tools, these 20 prompts are a solid foundation.
Top comments (12)
I think that you can make the prompts more structural, by the end of the day, we are already living in the post-Cursor era, we know the how-tos of AI Coding, we just need to calibrate our existing workflows.
Anyway, still good information!
Thats really true, We keep learning . The Cursor era
Absolutely, you're right. We’re past the “how to use AI” phase now it's about fine-tuning for real workflows. More structured, modular prompts make sense. Appreciate the feedback.
All right, I think for tasks like generating a Boilerplate, don't we prefer Cursor more these days? I think ChatGPT and other chat-based AI are fundamentally not that good at this. I use them for quickly do some edits, but eventually find the AI coding IDE to be more fitting for my tasks.
Thanks for the info, OP. Hope next time, we can read more about tips for Cursor/Claude Code.... etc.
Absolutely agree with you. For tasks like generating boilerplates or working across an entire codebase, Cursor really does a better job it understands the project structure and context much more deeply than a chat window ever could.
I still use ChatGPT for quick edits, refactoring ideas, or when I’m stuck on how to approach something. But yeah, when it comes to bigger coding tasks, an AI-powered IDE like Cursor or Claude Code is just more practical.
Appreciate the suggestion might actually do a follow-up piece diving into tools like Cursor, Claude CLI, and others that go beyond just prompting. Thanks for reading
Nice Tips, Emmanuel!
Some comments may only be visible to logged-in visitors. Sign in to view all comments.