メニュー
Evaluates error responses for actionable context and verifies that user-facing errors guide next steps while service-layer errors remain technical and reusable. Use when designing error responses, reviewing API output quality, building user-facing error handling, or evaluating support burden from poor error messages.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Evaluates and enforces layered middleware architecture for authentication, authorization, and usage enforcement on API routes. Use when building request middleware, enforcing plans or feature access, or attaching request context to downstream handlers.
Selects Cloudflare infrastructure services and LLM providers for a feature set based on dependency chains, storage needs, and settled policy. Use when assigning services (D1, KV, R2, Durable Objects, Queues, Workflows, Workers AI, Hyperdrive), evaluating whether a feature needs Workflows or Durable Objects, choosing between LLM providers, or confirming a build follows the Workers-first topology.
Audits request handling pipelines for explicit data flow, visible transformations, and traceability through logs. Use when designing request handling pipelines, reviewing code for debuggability, tracing production issues, or evaluating whether a new developer could follow the flow.
Audits stateful logic and error handling to verify single sources of truth, boundary-layer error handling, and explicit recovery paths. Use when designing APIs or workflows, refactoring stateful logic, or reviewing retries, fallback behavior, or recovery flows.
Traces feature implementation from UI through handlers, middleware, and storage to identify broken wiring, dead paths, and coverage gaps. Use when reviewing implementation completeness, validating frontend-to-backend wiring, or checking route/handler/middleware/storage consistency.
Audits authentication, authorization, and input validation boundaries to verify trust is established once at entry and not re-checked ad hoc throughout business logic. Use when building or reviewing auth, designing middleware, handling user/webhook/third-party input, or performing security-oriented review.
| name | enrich-error-context |
| description | Evaluates error responses for actionable context and verifies that user-facing errors guide next steps while service-layer errors remain technical and reusable. Use when designing error responses, reviewing API output quality, building user-facing error handling, or evaluating support burden from poor error messages. |
Primary roles: architect, engineer
Audits error responses across the system to ensure user-facing errors are actionable (not just descriptive), service-layer errors return technical data (not UX copy), and the right context reaches the right audience. Flags useless, generic, or misplaced error messages.
{ "error": "Invalid request" } — tells nothing.{ "error": "Usage limit exceeded" } — names the problem.Always aim for Level 4 on user-facing errors.
throw new Error("Invalid input") — what input? what's invalid?"Payment failed. Please contact support at support@example.com" in a reusable service — tightly coupled to one application.Produce the following: