30 curated prompts for the coding workflow, each paired with the AI tools that run them best.
Pairs well with
30 prompts
Refactor the function below. Preserve behavior. After the rewrite, list the invariants the refactor relies on, and note any callers that might break. Do not change the public API. Code: <paste>
Refactor the function below. Preserve behavior. After the rewrite, list the invariants the refactor relies on, and note any callers that might break. Do not change the public API. Code: <paste> Audience: a startup codebase.
Refactor the function below. Preserve behavior. After the rewrite, list the invariants the refactor relies on, and note any callers that might break. Do not change the public API. Code: <paste> Audience: a regulated enterprise.
I want to add <feature>. Before writing code, produce: (1) the user story, (2) acceptance criteria, (3) data model deltas, (4) API contract, (5) edge cases, (6) test list. Stop. Wait for approval.
I want to add <feature>. Before writing code, produce: (1) the user story, (2) acceptance criteria, (3) data model deltas, (4) API contract, (5) edge cases, (6) test list. Stop. Wait for approval. Audience: a startup codebase.
I want to add <feature>. Before writing code, produce: (1) the user story, (2) acceptance criteria, (3) data model deltas, (4) API contract, (5) edge cases, (6) test list. Stop. Wait for approval. Audience: a regulated enterprise.
I am seeing <symptom> in <env>. Stack trace and repro below. Identify the root cause, propose the minimal fix, and explain why simpler hypotheses are wrong. Do not paper over the issue. Trace: <paste>
I am seeing <symptom> in <env>. Stack trace and repro below. Identify the root cause, propose the minimal fix, and explain why simpler hypotheses are wrong. Do not paper over the issue. Trace: <paste> Audience: a startup codebase.
I am seeing <symptom> in <env>. Stack trace and repro below. Identify the root cause, propose the minimal fix, and explain why simpler hypotheses are wrong. Do not paper over the issue. Trace: <paste> Audience: a regulated enterprise.
Write tests first for <feature> using <test framework>. Cover happy path, two failure modes, and an edge case. Then implement the smallest code that passes them. Show tests and code separately.
Write tests first for <feature> using <test framework>. Cover happy path, two failure modes, and an edge case. Then implement the smallest code that passes them. Show tests and code separately. Audience: a startup codebase.
Write tests first for <feature> using <test framework>. Cover happy path, two failure modes, and an edge case. Then implement the smallest code that passes them. Show tests and code separately. Audience: a regulated enterprise.
Review the diff below as a senior engineer. Output 3 sections: blockers, must-fix, nits. Be specific, cite line numbers, and propose a concrete change for every blocker. Diff: <paste>
Review the diff below as a senior engineer. Output 3 sections: blockers, must-fix, nits. Be specific, cite line numbers, and propose a concrete change for every blocker. Diff: <paste> Audience: a startup codebase.
Review the diff below as a senior engineer. Output 3 sections: blockers, must-fix, nits. Be specific, cite line numbers, and propose a concrete change for every blocker. Diff: <paste> Audience: a regulated enterprise.
Migrate the file from <legacy lib> to <new lib>. Preserve behavior, update types, replace deprecated calls, and add a brief migration note at the top. Flag anything that has no clean equivalent.
Migrate the file from <legacy lib> to <new lib>. Preserve behavior, update types, replace deprecated calls, and add a brief migration note at the top. Flag anything that has no clean equivalent. Audience: a startup codebase.
Migrate the file from <legacy lib> to <new lib>. Preserve behavior, update types, replace deprecated calls, and add a brief migration note at the top. Flag anything that has no clean equivalent. Audience: a regulated enterprise.
Explain what the code below does. Give: (1) a one-paragraph summary, (2) a function-by-function map, (3) the data flow, (4) two non-obvious gotchas a new contributor would miss. Code: <paste>
Explain what the code below does. Give: (1) a one-paragraph summary, (2) a function-by-function map, (3) the data flow, (4) two non-obvious gotchas a new contributor would miss. Code: <paste> Audience: a startup codebase.
Explain what the code below does. Give: (1) a one-paragraph summary, (2) a function-by-function map, (3) the data flow, (4) two non-obvious gotchas a new contributor would miss. Code: <paste> Audience: a regulated enterprise.
Generate a typed API client for <openapi spec / endpoints>. Include: typed responses, request validation, exponential backoff with jitter, idempotency keys for POSTs, structured logging, and a mock server for tests.
Generate a typed API client for <openapi spec / endpoints>. Include: typed responses, request validation, exponential backoff with jitter, idempotency keys for POSTs, structured logging, and a mock server for tests. Audience: a startup codebase.
Generate a typed API client for <openapi spec / endpoints>. Include: typed responses, request validation, exponential backoff with jitter, idempotency keys for POSTs, structured logging, and a mock server for tests. Audience: a regulated enterprise.
Profile the function below. List the top three suspected hot paths, what data would confirm each, and the smallest change for each. Do not micro-optimize without evidence. Code: <paste>
Profile the function below. List the top three suspected hot paths, what data would confirm each, and the smallest change for each. Do not micro-optimize without evidence. Code: <paste> Audience: a startup codebase.
Profile the function below. List the top three suspected hot paths, what data would confirm each, and the smallest change for each. Do not micro-optimize without evidence. Code: <paste> Audience: a regulated enterprise.
Audit the handler below for OWASP top-10 risks. For each finding: severity, exploit scenario in two sentences, and a concrete remediation. Do not invent vulnerabilities. Handler: <paste>
Audit the handler below for OWASP top-10 risks. For each finding: severity, exploit scenario in two sentences, and a concrete remediation. Do not invent vulnerabilities. Handler: <paste> Audience: a startup codebase.
Audit the handler below for OWASP top-10 risks. For each finding: severity, exploit scenario in two sentences, and a concrete remediation. Do not invent vulnerabilities. Handler: <paste> Audience: a regulated enterprise.
GDPR Β· Privacy & cookies
We use strictly necessary cookies to run this site and, with your consent, anonymous analytics to improve it. You can change your mind at any time. Read more in our Privacy notice and Cookie policy.