القائمة
Use for safety rails — warns on destructive commands (rm -rf, DROP TABLE, force-push, git reset --hard) and provides freeze mode for focused debugging. Invoke with /stacks-guard.
التثبيت باستخدام 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-guard |
| description | Use for safety rails — warns on destructive commands (rm -rf, DROP TABLE, force-push, git reset --hard) and provides freeze mode for focused debugging. Invoke with /stacks-guard. |
| license | MIT |
| compatibility | Bun >= 1.3.0, TypeScript |
| allowed-tools | Read Edit Write Bash Grep Glob |
Prevent destructive actions and enforce focus during debugging sessions.
| Pattern | Risk |
|---|---|
rm -rf /, rm -rf ~, rm -rf . | Catastrophic file deletion |
DROP TABLE, DROP DATABASE, TRUNCATE | Irreversible data loss |
git push --force to main/master | Overwrites shared history |
git reset --hard with uncommitted changes | Loses uncommitted work |
git clean -fd | Deletes untracked files permanently |
buddy migrate:fresh on production | Drops ALL tables |
buddy seed --fresh on production | Truncates all data |
Response:
🔴 GUARD: Destructive command detected
Command: [command]
Risk: [what will be destroyed]
Reversible: [yes/no]
| Pattern | Risk |
|---|---|
git push --force (non-main) | Overwrites remote branch |
rm -rf [specific dir] | Deletes directory tree |
bun remove [core dep] | May break build |
git checkout -- . | Discards all unstaged changes |
| Bulk file moves/renames | May break imports/aliases |
Modifying config/services.ts | Contains API keys |
Modifying storage/framework/core/*/src/index.ts | Public package API |
| Pattern | Note |
|---|---|
git rebase | History rewrite — ensure not shared |
bun update (major versions) | May introduce breaking changes |
| Modifying CI/CD config | Affects deployment pipeline |
| Changing auth/permissions code | Security-sensitive |
| Modifying migration files | Database schema change |
Restrict edits during focused debugging.
/stacks-guard freeze [file or directory pattern]
When active:
/stacks-guard thaw
Produces a summary of all changes.
Before commits, scan for:
console.log, debugger, TODO: removepackage.json changed → bun.lock should toostorage/framework/types/*.d.ts — these are auto-generatedstorage/framework/defaults/models/ without also generating migrationsconfig/services.ts in commits — contains API keysstorage/framework/core/*/package.json versions — workspace packages should stay in syncrm file.txt doesn't need a warning. rm -rf node_modules is fine — it's regenerable.