Better words. Better starting points.

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

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 "

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.