Better words. Better starting points.

Review this code change before it ships. The change (diff or new code): {{diff}} What it's for, and facts the code doesn't show (data types, how it's called, the rules it must follow): {{context}} 1. List each problem with the line or function, what goes wrong, and a concrete input or sequence of events that triggers it. Check correctness against the rules I gave, security (injection, access co

Write test cases for this feature from its requirements. Requirements: {{requirements}} What else I know (platform, account types, limits, existing behaviour): {{context}} 1. Group the cases: main path, limits and boundaries, invalid input, account types and permissions, timing (expiry, repeats, two things at once), and failures of services the feature depends on. 2. For each case give a short

Write the interface copy for every state of this screen. The screen and what users do on it: {{screen}} Product voice and any length limits: {{voice}} 1. First list the states this screen can be in: first-time empty, loading, each error that can happen, success, and any permission or plan limit. Add a state I didn't mention only when what I described implies it, and mark it as added. Don't add

Review this HTML for accessibility problems. Code (HTML, plus CSS or JavaScript where it matters): {{code}} What the component does, and what the code doesn't show (colours, behaviour): {{context}} 1. List each problem with the element, what goes wrong and for whom (screen reader users, keyboard users, people with low vision, voice control users), and the WCAG 2.2 success criterion it fails, by

Go through this draft and list every claim a careful editor would want a source for. Draft: {{draft}} Who will read it, and how careful it needs to be: {{context}} 1. Quote each claim exactly as written, in the order it appears. Include numbers, dates, firsts and superlatives ("the largest", "the first"), quotes attributed to people, cause-and-effect statements, and general statements presented

Help me understand why this metric changed. Data: {{data}} What else I know (releases, campaigns, tracking changes, seasons): {{context}} 1. Describe exactly what changed: which metric, how much, from when, and which segments moved and which did not. 2. Check measurement first: could tracking changes, bot traffic, definition changes, time zones or incomplete recent data explain it? 3. List up t

Write launch copy for this product. Product and what it does: {{product}} Who it is for: {{audience}} Proof I can point to (users, results, quotes), if any: {{proof}} Write: 1. Product Hunt tagline, under 60 characters, saying what it does for whom. 2. Product Hunt description, under 260 characters. 3. Maker's first comment: why I built it, what it does differently, what it does not do yet, an

Help me judge whether this study should change my decision. Study (abstract, excerpt or summary): {{study}} My decision and context: {{decision}} 1. The claim: what the study says it found, in one or two sentences, using its own measures. 2. The evidence: design (experiment, observational, survey…), who was studied, how many, for how long, and what was compared. Say what the text does not repor

Review this pricing page as a potential customer would read it. Pricing page text: {{pricing page}} Who usually buys: {{customers}} 1. In two or three sentences, say which plan a typical customer would pick and how sure they would be. 2. List the issues, most costly first. For each, quote the wording, say what a buyer would misunderstand or worry about, and give a rewrite or fix. 3. Check for m

Write an email announcing this change to existing customers. Product: {{product}} What changed, and anything customers must do: {{change}} Who receives it: {{audience}} 1. Give three subject lines, each under 60 characters, that say what changed. 2. Write the email in plain text: - If customers must act, put the action, the deadline and what happens if they don't in the first lines. - Ex

Design the database changes for this feature. Feature: {{feature}} Current database and stack: {{current schema}} Include: 1. The entities and how they relate, in a few lines. 2. Each new or changed table: columns with types, nullability, defaults, keys and constraints. Explain any choice that is not obvious. 3. Indexes for the queries the feature needs, naming each query. 4. How existing data

Write a guide for 30-minute customer interviews. What I am building or exploring: {{idea}} Who I will talk to: {{people}} What I most need to learn: {{learning goal}} Include: 1. Three or four assumptions these interviews should test, each stated so an answer could prove it wrong. 2. Questions in the order to ask them. Ask about specific past situations ("Tell me about the last time…"), what p

Help me find the cause of this error. Error and log lines: {{log}} What changed recently, and where it happens: {{context}} 1. Say in one sentence what the log shows for certain, separately from what it only suggests. 2. List up to three likely causes, most likely first. For each, give the evidence in the log or context that points to it, and what would rule it out. 3. For each cause, give the

Turn this request into a brief for a coding agent such as Claude Code, Cursor or Codex. Request: {{request}} What I know about the codebase: {{codebase}} Write the brief with these sections: 1. Goal: one or two sentences on the outcome for the user. 2. Context: only what the agent needs from what I said about the codebase. Do not name files, functions, libraries or APIs I did not mention; say "

Plan my week. Tasks (with any deadlines and estimates I have): {{tasks}} Fixed commitments and available hours: {{calendar}} What matters most this week: {{priorities}} 1. Add up my available focus hours and the estimated hours of the tasks. Where a task has no estimate, give one and mark it as yours. 2. If it does not fit, say by how much, and propose what to cut, shrink, delegate or move to

Find micro-SaaS opportunities for me in recent AI product launches. About me: {{builder profile}} Focus areas: {{focus areas}} Time window: the last {{days}} days Work in two rounds and use web search. Every fact about a product (pricing, traction, complaints) needs a source link. If you cannot find something, write "not found" instead of estimating. Label your own judgments as inference. Round

Help me decide between {{option A}} and {{option B}}. Goal: {{goal}} Constraints: {{constraints}} 1. Name the 2–4 criteria that actually separate these options for my goal, and rate each high, medium or low in importance given my constraints. Skip criteria that would not change the answer. 2. For each criterion, say which option is stronger and why. Write "unknown" where it depends on information

Turn the following notes into a clear brief for {{audience}}. Notes: {{notes}} Return: objective, context, scope, deliverables, and open questions. Preserve the original facts. Mark missing information as unknown; do not invent it.

Edit this draft for {{audience}}. Level of editing: {{edit level}}. {{draft}} Preserve my meaning and voice, and keep roughly the same length unless the edit level calls for cuts. Do not add new facts, claims or lines of your own. - Light: fix grammar, cut repetition and tighten sentences. Keep the structure. If the main point is buried, point it out instead of moving it. - Heavy: also restructu

Explain this code to a {{experience}} developer: {{code}} Start with its purpose, trace the data flow, then identify assumptions and edge cases. Separate definite behavior from things that depend on missing context. Suggest useful tests.

Review this landing page copy for {{audience}}. {{copy}} Assess clarity, relevance, evidence, and the call to action. For each issue, quote the original wording, explain the friction, and suggest a rewrite. Do not invent customer claims or metrics.

Summarize these meeting notes for everyone involved, including people who missed the meeting: {{notes}} Return four sections: 1. Decisions: what was decided, one line each. 2. Action items: a table with task, owner, deadline, and any dependencies the notes state. Write "unspecified" when the notes do not say, and mark owners or deadlines the notes leave uncertain as "tentative". 3. Open questions

Create a research plan for this question: {{question}} Break it into answerable subquestions. For each, suggest evidence to seek and a method to evaluate it. Identify likely biases and what would change the conclusion. Do not fabricate sources or findings.