Prompt library
Start with a useful brief. Make it yours.
Fill in the variables, copy the prompt, and review the expected output. These are editable starting points.
Inspect a project before editing
Inspect {{project_area}} to understand {{behavior}}. Identify the relevant files, existing conventions, and documented validation commands. Explain what you found and what information is missing before proposing changes.Expected output: A short map of relevant files, an explanation of current behavior, and a bounded next step.
If the result misses the mark
If the answer is generic, identify an actual route, component, or file and ask for evidence from that location.
Make a focused change
Change {{current_behavior}} to {{desired_behavior}} in {{project_area}}. Preserve {{constraints}}. Use the repository conventions. Validate with {{acceptance_checks}} and report actual results and remaining limits.Expected output: A focused change, the checks actually run, and a clear description of what a reviewer should inspect.
If the result misses the mark
If the scope expands, restate the acceptance checks and separate unrelated improvements into follow-ups.
Review a proposed patch
Review {{change}} against {{requirement}}. Inspect affected callers and likely failure paths. For each supported finding, give the file location, concrete trigger, and consequence. State checks run and uncertainty. Do not edit files during this review.Expected output: Supported findings ordered by impact, or an explicit no-findings result with the review limits.
If the result misses the mark
If findings lack evidence, request the precise trigger and the code path that produces the consequence.