القائمة
Use when implementing health checks in a Stacks application — service monitoring, health endpoints, or diagnostic checks. Covers @stacksjs/health (currently WIP — Oh Dear integration planned).
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use for headless browser QA on Stacks applications — navigation, screenshots, responsive testing, console/network monitoring, and accessibility snapshots. Dependency-free: drives a system browser over the Chrome DevTools Protocol using only Bun (no Playwright/Puppeteer). Invoke with /stacks-browse.
Use when styling components in a Stacks application — utility-first CSS classes, theming, responsive design, variants, custom rules, or CSS generation. Crosswind is the CSS utility engine powering Stacks' Crosswind config.
Use when working with UI in a Stacks application — components, composables, reactivity (refs/watch/computed), Craft native components, Crosswind CSS, Crosswind utility framework, accessibility, or the STX templating engine. Covers @stacksjs/ui, @stacksjs/stx, and related UI tooling.
Use when building, modifying, or debugging API endpoints in a Stacks application — defining routes, handling requests, API middleware, working with the API server, HTTP client (fetcher), API resources, or OpenAPI generation. Covers both @stacksjs/api utilities and the stacks-api server implementation.
Use when working with routing in a Stacks application — defining routes, HTTP methods, route groups, middleware, named routes, URL generation, request enhancement (Laravel-style input/query/file helpers), response helpers, error responses, route model binding, or rate limiting. Covers @stacksjs/router, routes/, and app/Routes.ts.
Use when defining or organizing route files in a Stacks application — creating route files in routes/, registering them in app/Routes.ts, using route prefixes and middleware groups, or the default API routes structure. For the router API itself (request helpers, response helpers, middleware classes), see stacks-router.
| name | stacks-health |
| description | Use when implementing health checks in a Stacks application — service monitoring, health endpoints, or diagnostic checks. Covers @stacksjs/health (currently WIP — Oh Dear integration planned). |
| license | MIT |
| compatibility | Bun >= 1.3.0, TypeScript |
| allowed-tools | Read Edit Write Bash Grep Glob |
storage/framework/core/health/src/storage/framework/core/health/src/drivers/storage/framework/core/health/src/notifications/@stacksjs/healthhealth/src/
├── index.ts # Re-exports drivers and notifications
├── drivers/
│ ├── index.ts # Driver exports
│ └── ohdear.ts # Oh Dear health check driver (WIP)
└── notifications/
└── index.ts # Health notifications (WIP)
This package is WIP. Current exports are placeholder markers:
export const ohdearWip = 1 // Oh Dear driver placeholder
export const healthNotificationsWip = 1 // Notifications placeholder
The health check functionality currently lives in the router, not this package:
GET /health
Returns:
{
"status": "ok",
"uptime": 12345,
"memory": { "rss": 1234567, "heapUsed": 987654 },
"pid": 1234,
"bunVersion": "1.3.0"
}
This endpoint is registered via route.health() in the router.
buddy doctor # Comprehensive system diagnostics
GET /health works via route.health(), not this packagebuddy doctor — system diagnostics are in the buddy CLI, not this health package