Cursor

The Fix-with-AI prompt PulseLight generates is calibrated for Cursor's chat surface — restraint-engineered so the agent doesn't sweep-refactor or brick unrelated files.

Two ways to use PulseLight with Cursor: paste a generated prompt into Cursor chat (works today), or wire up the PulseLight MCP server so Cursor can pull verdicts and fix prompts itself (Studio tier, opt-in).

Option A: Paste-into-chat (the fast path)

01

Open the blocker on the Fix Queue.

Click the blocker on your Fix Queue. The card expands.

02

Click Fix with Cursor.

PulseLight generates the prompt and copies it to your clipboard. You’ll see a small toast confirming the copy.

03

Paste into Cursor chat (Cmd-L / Ctrl-L).

Open Cursor’s chat panel, paste the prompt. The restraint-engineered shape (Goal → Affected files → Working rules → Do NOT → Validation steps) means Cursor stays focused on the one fix and doesn’t sweep-refactor.

04

Apply the diff, run validation, re-scan.

Cursor returns a unified diff. Apply it, run the validation steps embedded in the prompt, push, and PulseLight re-scans when your CI build completes. The blocker should drop off the Fix Queue.

Anatomy of a Cursor-tuned prompt

Same v2 shape as every Fix-with-AI prompt, but the “Working rules” section is calibrated for Cursor’s defaults. Specifically:

<!-- pulselight prompt v2 (cursor) -->

Goal:
<plain-English description>

Affected files:
- <path>:<line>

Working rules (Cursor-specific):
- Use the project's existing pnpm/npm script, do NOT switch
  package managers.
- Match existing code style; don't reformat the file.
- Don't open new chat threads for sub-tasks; do this in one
  pass.

Do NOT:
- Refactor unrelated functions or rename variables.
- Upgrade dependencies unless the fix specifically requires it.
- Edit files outside the 'Affected files' list.

Validation steps:
- pnpm test <relevant-test>
- Re-scan: `pulselight scan` from the project root

Output a unified diff. Summarise changes in 3 bullets.

Option B: MCP server (Studio tier — early access)

The @pulselight/mcp package is a Cursor-compatible Model Context Protocol server. It’s in early access — npm publish is in flight; track shipping at /changelog. Once configured, you can ask Cursor things like:

  • “What’s my current PulseLight verdict?”
  • “Show me the Top 3 blockers and pick one to fix.”
  • “Apply the Fix-with-AI prompt for STRIPE-WEBHOOK-001.”

The MCP server exposes three tools: pulse_status, pulse_top_blockers, pulse_fix_prompt. Cursor calls them on your behalf when the conversation warrants. No paste step.

What restraint-engineering means in practice

Without the “Do NOT” section, Cursor (like every AI agent) tends to sweep-refactor: reformat the file, swap a package manager, upgrade an unrelated dependency, rename a variable across the codebase. The PulseLight prompt explicitly constrains that behaviour. The result is a small, reviewable diff that fixes the one thing.

See also: Fix-with-AI overview for the prompt structure across all eight supported tools.