B. Quality, Speed & Resilience · Prompt 24

Why it matters

The failures that hurt are often quiet: the user leaves, and nobody is alerted.

Modeled on

Structured logging and error tracking of the kind Sentry's open-source core is built around.

How to run this prompt

1. Switch to a mode that does not edit files. In Cursor that is Ask or Plan. In Claude Code that is Plan mode.
2. Paste the audit prompt. Wait for the report. It must stop and ask which IDs to fix.
3. Read the report. Keep the IDs you agree with.
4. Switch to a mode that can edit. Paste the fix prompt and the IDs you chose.
5. Switch back to the read-only mode and paste the same audit prompt again. Confirm those IDs are gone.

• Cursor: audit in Ask mode or Plan mode. Fix in Agent mode.
• Claude Code: audit in Plan mode (Shift+Tab cycles to it). Fix in Normal mode, which can edit.
• Any other tool: audit in Chat, Discuss, or Plan mode, whichever answers without editing files. If the tool has no such mode, the prompt itself forbids edits. Fix in the mode that is allowed to edit files.

MODE: AUDIT ONLY. Do not create, edit, or delete any file. Do not run commands
that change anything: no installs, migrations, git commits, deploys, or "--fix" flags.
If your tool has an Ask, Plan, Chat, or Discuss mode, use it for this prompt.

Before you start:
- Tell me the stack you detect (framework, language, database, auth, hosting,
  payment provider) and which folders you will review.
- If a check below does not apply to this stack, write "Not applicable" and why.
- If you can run read-only commands, run the ones listed. If you cannot, list them
  so I can run them and paste the output.

Error Handling & Observability: what to check
Review error handling. Do not add a vendor SDK in this pass.
1. Find async calls and request handlers with no try/catch and no .catch, where a failure would be swallowed or crash the process. Cite the file.
2. Say whether errors are logged with a request id and what was attempted. A log of the word "error" with no id is weak.
3. Say whether the user sees a message and a retry, or a blank screen or a spinner that never ends.
4. Say whether logging is one module or scattered console.log calls.
5. Flag a payment or data-loss failure that is only logged, with no alert path in code (email, webhook, or error-tracker capture).
6. If alerting is configured only in a dashboard, mark Needs manual check and say what I should look for.
7. List the 5 most dangerous silent failures, ordered by damage, with the file and the missing signal.
8. Do not print personal data from sample logs. Describe the fields.

Evidence rules:
- Every finding cites a file path and line number, or the exact command output used.
- Mark each finding Confirmed (seen in the code) or Needs manual check (depends on
  something outside the repo, such as a dashboard setting or production data).
- Never print a full secret. Show the first 4 characters and the location only.
- If you are not sure, say so. Do not invent files, settings, or results.

Severity: Critical = exploitable now, or leaks real data or money. High = serious
with little effort. Medium = weakens defenses or needs a second bug. Low = hygiene.

Report:
- Summary: count of findings by severity.
- Table: ID | Severity | Confirmed? | Finding | Evidence | Why it matters | Suggested fix | Effort
  (IDs for this prompt use the prefix P24, for example P24-1, P24-2.)
- Checked and fine: what you verified is already OK.
- Could not check: what I need to look at myself, and where.

Then stop. Do not fix anything. Ask me which IDs I want fixed.

Related prompts

• 23. Cost & Resource Efficiency

Share this prompt