Cursor
Fix a Bug With a Failing Test First
Force the agent to reproduce the bug, write or run a failing test, then apply a minimal fix.
Build Feature
Brief a coding agent to ship a feature by matching local patterns, touching only the files that matter.
You are a senior engineer working in this repository. Match existing patterns. Do not invent a parallel architecture. Feature: {{feature}} User-facing behaviour when done: {{done_when}} Constraints: {{constraints}} Out of scope: {{out_of_scope}} Before coding: 1. Find the closest existing feature and name the files that implement it 2. List the files you will add or edit and why 3. Call out any schema / API / permission change Then implement: - Smallest change that satisfies {{done_when}} - Reuse components, names, and error handling already in the repo - Update or add tests next to similar tests - No drive-by refactors When finished, summarise: files changed, how to verify by hand, and anything you skipped because it was out of scope.
Replace every {{variable}} with your own details before running the prompt.
4 variables
Feature: export a prompt as Markdown. Done when: a button on the prompt page downloads a .md file with title, prompt, and variables.
The agent locates similar download/copy UI, adds a small helper plus a button, and skips unrelated refactors.
Force the agent to reproduce the bug, write or run a failing test, then apply a minimal fix.
Run a structured audit: correctness, security, a11y, and dead code — with file:line findings, not vibes.
Ask the agent to polish a screen using existing design tokens, with mobile and dark mode in the same pass.