57 prompts · Free prompts for ChatGPT, Claude and Gemini
These prompts help you debug code, review changes, explain errors, write tests and document your work, in whatever language or framework you use.
Every prompt has [brackets] for your own details. Copy one, paste it into ChatGPT, Claude or Gemini, and refine the answer in the same conversation.
No prompts match your search. Try a different keyword.
Coding & Tech
Create an accessibility checklist for a [WEBSITE/APP TYPE], based on WCAG principles. Cover color contrast, keyboard navigation, screen readers, forms, and images. For each item, explain how to test it quickly.
Coding & Tech
Explain the time and space complexity of this code or algorithm, step by step: [CODE/ALGORITHM DESCRIPTION].
Coding & Tech
Write comprehensive API documentation for the following endpoint/function: [DESCRIPTION OR CODE]. Include: description, parameters (name, type, required, description), request/response examples, error codes, and usage notes.
Coding & Tech
Design REST API endpoints for [FEATURE], including method, path, request body, and response shape for each.
Coding & Tech
I want to connect [APP A] to [APP B] using their APIs. Outline the steps: authentication, the endpoints I will likely need, how to handle rate limits and errors, and a simple example request. Tell me to check the official docs for current details.
Coding & Tech
Write an architecture decision record for this decision: [DECISION]. Include context, options considered with pros and cons, the decision, and consequences, both good and bad. Keep it under one page.
Coding & Tech
Turn this bug description into clear, numbered reproduction steps a developer can follow: [DESCRIPTION]. Include expected vs actual behavior.
Coding & Tech
Design a CI/CD pipeline for a [LANGUAGE/FRAMEWORK] project hosted on [PLATFORM]. List the stages (build, test, lint, deploy), what runs on pull requests versus merges, how to handle secrets, and a simple example configuration.
Coding & Tech
Give me the exact [BASH/GIT/DOCKER/etc.] command(s) to [TASK], and explain what each flag does.
Coding & Tech
Add clear, concise comments to this code without over-commenting the obvious: [CODE].
Coding & Tech
Debug the following [LANGUAGE] code. Identify all bugs, explain why each one is a problem, provide the corrected code, and suggest any improvements to make it cleaner or more efficient. Code: [PASTE CODE]
Coding & Tech
Explain the following [LANGUAGE] code to someone with [LEVEL] programming experience. Go line by line, explain what each section does, highlight any clever or non-obvious parts, and describe the overall purpose. Code: [PASTE CODE]
Coding & Tech
Review the following [LANGUAGE] code for: (1) bugs or logic errors, (2) performance issues, (3) security vulnerabilities, (4) readability and maintainability. For each issue, explain why it's a problem and how to fix it. Also tell me what the code does well. Code: [PASTE]
Coding & Tech
Create a code review checklist for [LANGUAGE/FRAMEWORK] pull requests, covering correctness, security, performance, and style.
Coding & Tech
Review the following [LANGUAGE] code as a senior engineer. Evaluate: code quality and readability, potential bugs, security vulnerabilities, performance issues, and adherence to best practices. Provide actionable line-by-line feedback. Code: [PASTE CODE]
Coding & Tech
Review this [LANGUAGE] code for security issues: [CODE]. Check for injection, unsafe input handling, exposed secrets, and weak authentication. For each issue, explain the risk in one sentence and show a safer version.
Coding & Tech
Review this code for code smells: [CODE]. Identify duplication, long functions, unclear names, and tight coupling. For each, say why it hurts maintainability and suggest the smallest change that would improve it.
Coding & Tech
Convert the following [SOURCE LANGUAGE] code to [TARGET LANGUAGE]. Preserve the exact logic and functionality. After the conversion, note any differences in behavior, syntax, or conventions between the two languages that are relevant to understanding the converted code. [PASTE CODE]
Coding & Tech
Write a cron expression that runs [TASK] at [SCHEDULE IN PLAIN WORDS]. Explain each field, show the next 3 run times as an example, and mention time zone and overlap issues to watch for.
Coding & Tech
Design a database schema for [APP/FEATURE], given these requirements: [REQUIREMENTS]. List tables, key columns, types, and relationships.
Coding & Tech
You are a senior [LANGUAGE] developer. Here is a function that isn't working: [PASTE CODE]. Expected behavior: [DESCRIBE]. Actual behavior: [DESCRIBE]. Identify the bug(s), explain what's causing each issue in plain language, and provide a corrected version with comments explaining each fix.
Coding & Tech
Given this problem: [PROBLEM DESCRIPTION], recommend an appropriate design pattern, explain why it fits, and sketch the structure.
Coding & Tech
Write a Dockerfile for a [LANGUAGE/FRAMEWORK] app that [KEY REQUIREMENTS, e.g. needs Node 20, exposes port 3000]. Keep the image small.
Coding & Tech
List the environment variables and config values a [TYPE OF APP] typically needs, grouped by purpose (auth, database, third-party APIs, etc.).
Coding & Tech
Explain this error message in plain language and suggest likely fixes: [ERROR MESSAGE + brief context].
Coding & Tech
Explain [TECHNICAL CONCEPT OR DECISION] to a non-technical audience of [AUDIENCE]. Use one everyday analogy, avoid jargon, say what it means for their goals or budget, and end with the one thing I need them to decide or understand.
Coding & Tech
Explain what this code does in plain English, as if explaining to a non-technical stakeholder. First give a one-sentence summary. Then walk through each major section — what it does and why. Highlight anything that could be a problem or deserves attention. Code: [PASTE]
Coding & Tech
Write a git commit message for the following code changes. Follow Conventional Commits format (type(scope): description). Include a short subject line under 72 chars, and a body explaining what changed and why. Diff: [PASTE DIFF]
Coding & Tech
Write a blameless postmortem from these notes: [INCIDENT NOTES]. Include a summary, timeline, impact, root cause, what went well, what did not, and 3-5 action items with owners. Focus on systems and process rather than individuals.
Coding & Tech
Explain what this legacy code does, section by section, and flag anything that looks risky or outdated: [CODE].
Coding & Tech
Analyze this log excerpt: [LOG LINES]. Identify errors and warnings, group repeated messages, find the most likely root cause, and suggest what additional logs or metrics I should look at next. Do not guess beyond what the log shows.
Coding & Tech
Plan a safe migration from [OLD STRUCTURE] to [NEW STRUCTURE] for [DATABASE/SYSTEM], including rollback steps.
Coding & Tech
Suggest clear, idiomatic names for these variables/functions based on what they do: [LIST WITH BRIEF DESCRIPTIONS].
Coding & Tech
I know [CURRENT LANGUAGES] and want to learn [NEW LANGUAGE] to build [GOAL]. Create a 6-week roadmap that highlights the differences from what I already know, the key concepts to learn first, one small project per two weeks, and good practice habits.
Coding & Tech
Review this code for likely performance bottlenecks: [CODE]. Explain why each is a problem and suggest a fix.
Coding & Tech
Convert this pseudocode into working [LANGUAGE] code: [PSEUDOCODE]. Add brief comments explaining non-obvious parts.
Coding & Tech
Write a pull request description for these changes: [SUMMARY OF CHANGES]. Include what changed, why, how it was tested, and any follow-ups.
Coding & Tech
Write a Python script that automates this task: [TASK, e.g. rename files, merge CSVs, send a daily report]. Use only the standard library if possible, add clear comments, handle common errors, and explain how to run it.
Coding & Tech
Create a professional README.md for my project: [PROJECT NAME]. It is a [DESCRIPTION]. Include: badges, overview, features, installation steps, usage examples with code, configuration options, contributing guidelines, and license section.
Coding & Tech
Refactor this [LANGUAGE] code for readability and maintainability without changing behavior: [CODE]. Explain each significant change.
Coding & Tech
Write a regular expression that matches [DESCRIBE THE PATTERN]. Provide: the regex itself, a plain-English explanation of how it works, 5 example strings it matches, 3 it should NOT match, and a code snippet showing how to use it in [LANGUAGE].
Coding & Tech
Act as a rubber duck. I will explain my bug and my code step by step. Do not give the answer right away. Ask me one short question at a time that helps me notice the problem myself, and only suggest a fix if I ask. The bug: [DESCRIPTION].
Coding & Tech
Write a [BASH/ZSH/POWERSHELL] script that [TASK]. Include input checks, helpful error messages, and comments. Add a short note on what could go wrong and how to test it safely before running it on real data.
Coding & Tech
I use [EXCEL/GOOGLE SHEETS]. My data is in [COLUMNS/LAYOUT]. Write a formula that [WHAT YOU NEED]. Explain how it works step by step and give one example with sample values.
Coding & Tech
Write an optimized SQL query to [DESCRIBE WHAT YOU WANT]. My database has these tables and schemas: [SCHEMA]. Include comments explaining each part of the query and suggest any indexes that would improve performance.
Coding & Tech
You are a database performance expert. Here is a SQL query that is running slowly: [PASTE QUERY]. Table sizes and indexes: [DESCRIBE]. Identify why it might be slow, suggest specific optimizations (indexes, query rewrites, etc.), and provide an optimized version. Explain each change and why it improves performance.
Coding & Tech
Here is a stack trace: [STACK TRACE]. Explain in plain language what happened, point to the most likely line or module at fault, and give 3 things to check in order, starting with the most likely cause.
Coding & Tech
Design a scalable system architecture for [APPLICATION TYPE] that needs to handle [SCALE]. Include: components and their responsibilities, data flow diagram description, database choices with justification, API design, and potential bottlenecks with solutions.
Coding & Tech
Compare [OPTION A] vs [OPTION B] for building [PROJECT TYPE]. Cover learning curve, performance, ecosystem, and long-term maintenance.
Coding & Tech
Here is a list of technical debt items: [LIST]. Score each by impact, effort, and risk if ignored, then recommend which 3 to tackle first and how to explain the case for fixing them to non-technical stakeholders.
Coding & Tech
Act as an interviewer for a [ROLE/LEVEL] position. Ask me one [LANGUAGE/TOPIC] question at a time, wait for my answer, then give feedback on correctness, clarity, and what a stronger answer would include before moving to the next question.
Coding & Tech
List edge cases and test scenarios I should cover for this function: [FUNCTION DESCRIPTION/CODE]. Include normal, boundary, and failure cases.
Coding & Tech
Generate TypeScript interfaces from this JSON: [JSON]. Mark fields that are likely optional or nullable, use clear names, and note any fields where the type is ambiguous so I can check the real API.
Coding & Tech
Write comprehensive unit tests for the following [LANGUAGE] function using [TESTING FRAMEWORK]. Cover: happy path, edge cases, null/empty inputs, and error conditions. Include descriptive test names. Code: [PASTE CODE]
Coding & Tech
My webhook from [SERVICE] to [MY ENDPOINT] is not working. Give me a step-by-step checklist to debug it: verifying delivery, checking signatures and status codes, handling retries and timeouts, and testing locally. Ask me for the details you would need.
Coding & Tech
Write a [LANGUAGE] function that [DESCRIBE WHAT IT SHOULD DO]. Requirements: [LIST INPUTS, OUTPUTS, EDGE CASES]. Include: the function with clear variable names, inline comments on non-obvious logic, and a docstring. Also write 3 unit tests: normal use, edge case, and expected failure.
Coding & Tech
Write a regular expression that matches [DESCRIBE WHAT IT SHOULD MATCH]. Give examples of strings it should match and strings it should NOT match. Explain the regex in plain language, breaking down each component. Flag any edge cases or limitations.
Yes. Paste the error message, the relevant code and what you expected to happen, then ask it to find the cause and suggest a fix. Test any suggested change yourself before you use it.
State the language and version, the goal, the constraints and a short example of the input and output. Small, specific requests give better code than one very large request.
Yes, every prompt is free to copy and needs no account. They are written in plain language, so they work in ChatGPT, Claude, Gemini and most other AI assistants.
