AI Coding Prompts: 500 tested prompts

What’s inside

• 500 prompts in 25 categoriesUnderstand and learn code; Plan and write new code; Debug and fix; Refactor; Review code; Unit tests; Integration and end-to-end tests; Performance; Secure coding; SQL and databases; APIs and integrations; HTML, CSS and accessibility; JavaScript, TypeScript and UI frameworks; Back-end services and concurrency; Errors, logging and monitoring; Data processing and analysis; DevOps, CI/CD and cloud; Shell, regex and automation; Git and teamwork; Documentation; Architecture and design; Upgrades, migrations and legacy code; Algorithms and data structures; Mobile apps; AI features in your app
• Every prompta role for the assistant, the task, one to six variables with what to put and an example, the steps to work through, the kind of answer, the rules it must meet, a checklist of what a good answer has, an example input, a shortened sample answer, a tip and what it needs beyond text where it does
• The library PDF, 694 pages (A4)start here, how variables work, contents, an opener for each category, one card per prompt with a copy box and the example code, a thumb-index tab on every category page, an index A to Z and a bookmark for every category and prompt
• The guide PDF, 13 pageshow variables work, getting good answers for coding work, safety and privacy with your code, using each file, the categories, how every prompt was checked, licence and credits
• CSV, JSON and Markdown copiesall 500 prompts with the same ids: a spreadsheet row each, a JSON record each for prompt managers and scripts, and one Markdown file per category
• Example code you may reusethe code in the examples and sample answers is ours, licensed for your own projects
• Licence and changelogas plain text

Works with

“Tested” means we opened and checked the file in that app and kept the record. “Made for” means it follows that app’s documented format. No DRM: the file is yours to keep.

Try a sample

You are a developer with a sharp eye for boundary errors.

This {{language}} code has an off-by-one bug. The symptom is that {{symptom}}.

The code:
```
{{code}}
```

Work through these steps:
1. Reproduce the symptom with the exact numbers it gives, showing the values the code computes at each step.
2. List every boundary in the code (loop limits, slices, comparisons, page numbers, the rounding of divisions), whether it is inclusive or exclusive, and check each one with the smallest inputs that reach it and with inputs one past it.
3. Point out each wrong boundary and show the fix.
4. Write tests for the boundary values.

Answer with a table of boundaries, the faulty ones with the fix in a code block and the boundary tests.

You are a careful analyst who writes SQL that answers exactly the question asked.

Write a {{engine}} query that answers this question, {{question}}. The tables are below.

The tables:
```
{{schema}}
```

Work through these steps:
1. Restate the question as precise rules (time range, what counts, ties, missing data).
2. Write the query, using common table expressions where they make it easier to read.
3. Explain how it treats edge cases such as NULLs, duplicates and empty periods.
4. Give a tiny example (a few rows per table) and the result it would produce.

Answer with the rules as a list, the query in one code block, notes on edge cases and a worked example. If the question is ambiguous, state the assumption you made.

You are a reviewer who makes code easier for the next person to read.

Review the {{language}} code below only for readability, as if a new team member had to change it next month.

The code:
```
{{code}}
```

Work through these steps:
1. Point out the three to five things that make it hardest to understand, in order of impact.
2. Suggest a concrete rewrite for each (a name, an extracted function, a comment that explains why).
3. Mark anything that is fine as it is, so that I do not over-correct.
4. Show the most improved part rewritten.

Answer with a numbered list of readability problems with suggestions, a short list of things that are fine, and the rewritten part in a code block.

How it helps

Refunds and your rights

Because the file is ready the moment you pay, we don’t refund a purchase once its download has started, unless the file is faulty or not as described: then we fix it, send you a corrected file or refund you. If you live in the EU, the EEA or the UK, you can withdraw from your purchase until your download starts, and you keep every right the law gives you.

Your legal guarantee: if a file is faulty or not as described, we repair it, replace it or refund you.

Refunds and withdrawal in the Digital Store terms

Delivery and paying

Download straight after paying, on this page and by e-mail. Nothing is shipped. Sold in the countries where a way to pay shows on this page.

You can download your files again from your order page whenever you need them. If we ever stop offering downloads, we’ll e-mail you at least 90 days before so you can save your copy.

• In rupees: UPI, cards or netbanking on Razorpay’s secure page. MySmartCoPilot sells the file to you.
• In US dollars: card or wallet with Dodo Payments, which sells the file to you as merchant of record and e-mails your receipt or invoice.
• In US dollars with PayPal, where it is offered. MySmartCoPilot sells the file to you.

Bought once, separately from passes. How the Digital Store and passes differ.

Questions

Versions

• Version 1.0: First edition.

Related

• AI Prompt Library: 1,500+ tested prompts Get a useful answer from any AI chat assistant the first time, with a finished, tested prompt for each everyday job. PDFCSVJSONZIP ₹199 / $4.99

Prefer it online?

• AI Prompt Generator & Prompt Improver: Build a clear prompt from a short form — or improve the one you already use.

More files in AI Libraries, Developer Kits.