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…
Install
The individual skill folder is not confirmed. This command opens the repository’s skill selector; follow the upstream instructions.
skills CLI
npx skills add samber/developer-platform-skills