Every coding prompt in the collection, most liked first. Each one is free to copy and shows an example of what it produces.
Paste the commands and their real output, and get an HTML file that replays them as a typed terminal session, ready to screen record for a README or a landing page, with no typos and no waiting for the real thing to run.
Give Claude the facts about your project and get a README in Markdown that starts with install and first run, explains how it works in five sentences, and says honestly when not to use it.
What it does. Once a night, it finds every subscription that renewed in the last 24 hours, builds a PDF invoice for each one, emails it, and records that the invoice was sent. If anything fails for one customer, it moves on to...
Paste a function or file you didn't write and get a plain explanation of what it does, why it's built that way, and where it's likely to break.
Six lightweight loading indicators in pure CSS. Each has a reduced motion fallback, and one variable changes the colour of all of them.
What the error means. Cannot read properties of undefined (reading 'map') means orders was undefined at the moment the component rendered. The array never arrived, or it arrived under a different name. Most likely causes 1...
Stops Claude from patching symptoms. It ranks the likely causes, tells you what to check first, and only then writes the fix.
In one paragraph. This is a bookings app for small gyms. A React front end talks to an Express API in /server. Data lives in Postgres and is accessed through Prisma. Anything slow (emails, PDF invoices) goes through a job...
Paste a file tree and a few key files and get the tour a senior engineer would give you: how a request flows, where things live, what to avoid.