Api Status Communication

samber/developer-platform-skills/skills/api-status-communication

作者 samber594cf70d343eMIT3 個星標收錄於 2026年10月8日更新於 2026年10月8日儲存庫10 天前更新

Design how an API platform communicates status and incidents to external consumers - status-page modeling (the four-stage incident lifecycle, degraded/partial/major component semantics, component granularity), monitoring-driven status instead of a hand-flipped green light, pull and push channels, incident-update cadence and templates, public postmortems for a developer audience, public SLA/SLO reporting, and maintenance-window notices. Use whenever the user mentions a status page, Statuspage, incident updates, uptime or SLA reporting, postmortems, or scheduled maintenance - even if they never say "status communication". Do NOT use for deprecation and breaking-change notices - use samber/developer-platform-skills@api-versioning-policy instead.

  1. 594cf70d343e目前提交 594cf70發布於 2026年10月8日

來源與署名

來源:samber/developer-platform-skills位於skills/api-status-communication提交594cf70

授權條款: MIT

內容歸原作者所有。SourceWeft 從公開儲存庫中收錄這些內容。

檢舉或申請下架