Claude prompts

Review an API design or OpenAPI spec for naming, consistency, versioning, and future-proofing.

Stress-test an argument you want to make — find its holes before someone else does.

Edit a blog post to a specified voice and reading level while keeping the substance intact.

Develop a book or long-form project outline from a core idea, with chapters that carry the argument.

Audit code for injection, auth bypass, data exposure, and dependency risks with concrete fixes.

Map out how a codebase fits together — entry points, modules, data flow, and the risky parts.

Read through a contract draft and surface the risky clauses, missing protections, and fair questions to ask.

Design an analysis plan for a messy dataset before writing a line of code.

Turn a hard choice into a scored decision matrix with honest weights and sensitivity checks.

Fix the structure of a draft essay — thesis, argument flow, paragraph logic — before the prose polish.

Turn a meeting transcript or rough notes into a clean follow-up email with next steps.

Extract the decisions, arguments, and key facts from a long report without losing nuance.

Plan a safe refactor: what to change, in what order, and how to keep every step green.

Turn a vague feature request into specific questions and a crisp one-paragraph restatement.

Critically evaluate a paper's claims, method, and evidence — strengths first, then the real gaps.

Translate a SQL query into plain English and check whether it actually answers the question.

Turn working code or a feature into clear docs: overview, usage, and the trap to avoid.

Generate thorough unit test cases for a function or module, including the nasty edge cases.