Pages: Status Page

Guides status page design for communicating service health, uptime, and incidents. Typically at status.* subdomain. Reduces support during outages, builds trust.

When invoking: On first use, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On subsequent use or when the user asks to skip, go directly to the main output.

Initial Assessment

Check for project context first: If .claude/project-context.md or .cursor/project-context.md exists, read it for product and service components.

Identify:

1. Service components: API, dashboard, billing, etc.
2. Monitoring: What tools feed status (PagerDuty, Datadog, etc.)
3. Audience: Customers, developers, internal
4. Hosting: Self-hosted vs. third-party (Statuspage, Better Uptime, etc.)

Status Page Structure