status-page

Conventions for building authenticated admin API routes in this status-page app (app/api/admin/*). Use this skill whenever adding or editing admin endpoints for monitors or settings, validating request bodies, generating monitor slugs, or wiring API writes to the monitor manager. Trigger on phrases like "add an admin endpoint", "CRUD for monitors", "update settings API", "validate the request body", "admin route", or anything under app/api/admin. Apply automatically when building admin server routes.

Single-password admin authentication for this status-page app. Use this skill whenever working on login, sessions, the session cookie, middleware route protection, or the Node-vs-Edge runtime split for auth. Trigger on phrases like "protect the admin", "login", "session cookie", "middleware auth", "verify the session", "admin password", or anything touching lib/auth.ts, lib/auth-edge.ts, or middleware.ts. Apply automatically when building or changing authentication here.

Conventions for the SQLite data layer in this status-page app (lib/db.ts). Use this skill whenever adding tables, columns, queries, or dbOps methods, writing migrations, or persisting configuration (monitors, settings, checks). Trigger on phrases like "add a table", "add a column", "store a setting", "query the database", "add a dbOps method", "migrate the schema", or any change touching lib/db.ts, lib/seed.ts, or SQLite persistence. Apply automatically when working with data persistence here.

How the runtime monitor manager and check executors work in this status-page app. Use this skill whenever adding a monitor check type, changing how monitors are scheduled/pinged, working with the background monitoring loop, retention cleanup, or anything in features/status/server/*. Trigger on phrases like "add a check type", "schedule a monitor", "ping logic", "background job", "reschedule monitors live", "monitor manager", or "retention cleanup". Apply automatically when touching the monitoring runtime.

Enforces a consistent, scalable Next.js App Router folder and file structure for full-stack projects. Use this skill whenever the user asks to create, scaffold, add, move, or refactor files in a Next.js project — including adding new pages, features, API routes, components, hooks, providers, or lib utilities. Trigger on phrases like "add a new page", "create a feature", "add an API route", "scaffold a component", "where should I put this file", "create a new Next.js project", or any time code is being placed in or moved within a Next.js app. Apply this structure even if the user doesn't explicitly ask about structure — if they're building something in Next.js, follow these conventions automatically.