Prompt library

walk me through this codebase: what it does, the main folders, and how a request flows through it

explain what <src/sync/conflict-resolver.ts> does and where its inputs come from. present it as <a single HTML page with a sequence diagram, and open it in my browser>

where do we <decide whether a user can see another team's projects>?

if I removed <the legacyPriceFormatter function>, what would break? list every caller and test

read the git history for <lib/rate_limit.rb> and tell me how it got to its current shape and why

which files would need to change to <let users export reports as Excel files>? rough effort for each

I'm a <product designer>. explain in plain language what happens when a user <presses "Archive project">, from the button to the database and back

plan how to <split the notifications service out of the monolith>. list the files you'd change and in what order. don't edit anything yet

I want to build <team-level spending limits>. ask me questions one at a time about behaviour, UX, edge cases and trade-offs until nothing is left open, then write the spec to <docs/specs/spending-limits.md>

read <@notes/2026-10-02-planning.md>, pull out every action item, and create a ticket in <Linear> for each with acceptance criteria and an owner if one was named

list every empty, loading, error and edge-case state the design for <the invite-teammates flow> needs to handle

here's a mockup [paste image]. build a clickable prototype that matches the layout and shows each state

implement this design [paste image]. then screenshot your result, compare it with the original and fix the differences until they match

study how <the Stripe webhook handler> is built, then build <a GoCardless webhook handler> the same way, including tests

add a <GET /api/status> endpoint that returns <the deployed commit SHA and database connectivity>

read issue #<418>, implement a fix, run the relevant tests and tell me what you changed

build a <one-page tool that turns a CSV of timesheets into a weekly summary table> using plain HTML, CSS and JavaScript, then open it in my browser

find every occurrence of "<Book a demo>" or close variants, show me each in context, then change them to "<Talk to sales>". leave tests and the changelog untouched

read the <incident reports> in <docs/incidents/> to learn their structure and tone, then draft one for <yesterday's queue backlog outage>

find <exported functions in packages/core> without <TSDoc> comments and add them, matching the style already used in each file

write tests for <app/services/refunds.py>, run them, and fix any failures. tell me if a failure looks like a real bug rather than a bad test

write failing tests for <the password strength meter> first, then implement it until they pass

read <coverage/coverage-summary.json> and add tests to the least-covered files until each is above <85>%

migrate everything from <moment.js> to <date-fns>: find every usage first and show me the list, then make the changes and run the tests

port <this Go package> to <TypeScript>, keeping the same <public API and test cases>

get <the dashboard's initial load> from <3.4s> to under <1.5s>. measure before and after, and explain each change

on <a 390px wide screen>, the <price badge> overflows the <product card> by about <12px>. fix it without changing the desktop layout

review my uncommitted changes and flag anything risky, untested or inconsistent with the rest of the codebase

review PR #<1093>: summarise what it changes, then list concerns ordered by severity

here's my <terraform plan> output [paste]. explain in plain English what will change and flag anything destructive or surprising

use a subagent to review <services/auth/> for security problems and report only findings with a concrete exploit path

review <press-release.md> for <claims we can't back up, missing attributions and off-brand wording> and list what to fix before it goes to <legal>

that's not what I need: <the public method signatures must not change>. try a different approach

too much. keep only the changes to <the CSV parser> and revert everything else you edited

you keep <adding default exports when this project uses named exports>. add a rule to CLAUDE.md so it stops happening

resolve the merge conflicts on this branch and explain, file by file, what you kept from each side

commit this with a message that explains why the change was needed, not just what changed

find the ticket about <bulk-deleting archived invoices> in <Jira> and open a pull request that implements it

compare <v3.8.0> with <main> and draft release notes grouped into features, fixes and breaking changes, written for customers

write a GitHub Actions workflow that <runs lint, type checks and tests, then builds the Docker image> on every push to <main>

<test_invoice_totals_with_vat> is failing. find out why and fix the cause

customers are reporting <duplicate confirmation emails> on <the checkout flow>. investigate and tell me what's happening before changing anything

here's the build error [paste]. fix the root cause and confirm the build passes

<API error rate jumped to 8% at 14:20>. check the logs, recent deploys and config changes, then give me the most likely cause and how sure you are

this is a screenshot of <the AWS ECS console> [paste]. explain why <the worker service> keeps restarting and give me the exact commands to fix it

show me every <failed login> for <the acme tenant> over <the last 48 hours>. write the query, run it and tell me what looks unusual

read <@exports/churn-q3.csv>, summarise the main patterns and write the findings to <reports/churn-q3.md>

read <@ads/october.csv>, find the worst-performing <headlines> and write <8> new options under <40> characters each

create a /<prepare-release> skill for this project that <bumps the version, updates CHANGELOG.md from merged PRs and opens a release PR>

write a hook that <runs ruff format on the file> after every <edit or write>

connect <our Sentry project> through MCP so you can read <issues and stack traces> directly

summarise what we did this session and suggest what should go into CLAUDE.md

add request logging with correlation IDs to every API route and keep the existing tests green

write the migration, apply it to the local database and confirm the table looks right

build the billing settings page with the same layout and form components as the profile page

cut the JavaScript bundle below 250 KB and list what you removed

why did the deploy fail? @logs/deploy-2026-10-07.txt

explain how session refresh works as a one-page HTML explainer with a diagram, aimed at a new backend developer