Api Error Design

samber/developer-platform-skills/skills/api-error-design

作者 samber594cf70d343eMIT3 个星标收录于 2026年10月8日更新于 2026年10月8日仓库10天前更新

Design the error surface of a public API so integrators self-serve fixes - a machine-readable error-code taxonomy (flat catalog, code/subcode, Google-style domain/reason), the RFC 9457 problem-details envelope with extension members, actionable error messages, retryability signaling (retryable flag, Retry-After), and per-endpoint error documentation with request-ID tracking. Use whenever the user mentions API error codes, an error taxonomy, RFC 9457, application/problem+json, 4xx/5xx response bodies, or confusing API error messages - even if they never say "error design". Do NOT use for client-side retry mechanics - use samber/developer-platform-skills@api-idempotency-retry - nor for incident and status-page communication - use samber/developer-platform-skills@api-status-communication instead.

  1. 594cf70d343e当前提交 594cf70发布于 2026年10月8日

来源与署名

来源:samber/developer-platform-skills位于skills/api-error-design提交594cf70

许可证: MIT

内容归原作者所有。SourceWeft 从公开仓库中收录这些内容。

举报或申请下架