Error Handling
# 07 — Structured error handling
## Context
Use this when a service has grown a thicket of `try/except: pass`,
inconsistent error shapes, and 500s leaking stack traces. The goal
is one error contract, applied uniformly, that gives clients enough
to act on without leaking server internals.
## Templatewhen to use it
Community prompt sourced from the open-source GitHub repo thunderstornX/cursor-vibe-starter (MIT). A "Error Handling" style prompt — adapt the placeholders and specifics to your task. Imported as-is and not independently retested here, so check the output before relying on it.
tags
roleplaycommunitygeneral
source
thunderstornX/cursor-vibe-starter · MIT