Menu
Use when an API needs consistent error responses: catch unhandled errors centrally and return consistent JSON error envelopes.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | backend-error-handling |
| description | Use when an API needs consistent error responses: catch unhandled errors centrally and return consistent JSON error envelopes. |
| slipstream | {"category":"backend","requires":["backend-hono-api"],"verification":{"kind":"test","description":"Error handling tests pass.","command":"pnpm --dir {{apiDir}} test"},"tags":["api"]} |
Catch unhandled errors centrally and return consistent JSON error envelopes.
app.onError handler that maps known error types to HTTP status codes.{ error: { code, message } } shape.Run the API tests including a route that throws, and confirm the response is a clean JSON envelope with the right status.
Use when several pieces of work are genuinely independent and can run at once, to fan them out across parallel agents instead of doing them in sequence. Cuts wall-clock time and keeps each strand in its own clean context.
Use when a written plan exists and you are about to build it in the current session, to work it task by task with a checkpoint after each. Keeps execution honest against the plan instead of drifting into a freehand build.
Use when work needs its own isolated checkout — parallel strands that would fight over files, or a risky change you want quarantined from the main tree. Gives each strand a real working directory on its own branch without re-cloning.
Use whenever the user says "use slipstream", "use superpowers", or starts any task in a project that has slipstream. A hard, always-on discipline that forces scoped reads over whole-file reads to save tokens, recalls memory before acting, and records what is durable every turn so memory grows constantly.
Use when a site needs to look designed rather than defaulted, before building sections: establish a cohesive design system of type scale, spacing, colour, radius and shadow tokens so every component shares one premium visual language.
Use when building the top of a landing page, to produce a high-impact hero with confident display type, a clear single call to action and balanced composition, the kind of opening a polished marketing site leads with.