Development

Use when doing ANY task involving Supabase. Triggers: Supabase products (Database, Auth, Edge Functions, Realtime, Storage, Vectors, Cron, Queues); client libraries and SSR integrations (supabase-js, @supabase/ssr) in Next.js, React, SvelteKit, Astro, Remix; auth issues (login, logout, sessions, JWT, cookies, getSession, getUser, getClaims, RLS); Supabase CLI or MCP server; schema changes, migrations, declarative schemas, security audits, Postgres extensions (pg_graphql, pg_cron, pg_vector); ...

將自然語言功能需求轉成本次迭代的 plan package，產出 `spec.md` 與 `checklists/requirements.md`；package 路徑與 truth delta 的落點依 `rules/Feature目錄命名與輸出定位判準.md` 決定。不得改寫舊 plan package，也不得寫入 `specs/truth/**`。

Use for review lifecycle work: human-gate checks or UI screenshot evidence. Not for archiving (retired), product code review, or Lighthouse analysis.

Use when writing Playwright tests, fixing flaky tests, debugging failures, implementing Page Object Model, configuring CI/CD, optimizing performance, mocking APIs, handling authentication or OAuth, testing accessibility (axe-core), file uploads/downloads, date/time mocking, WebSockets, geolocation, permissions, multi-tab/popup flows, mobile/responsive layouts, touch gestures, GraphQL, error handling, offline mode, multi-user collaboration, third-party services (payments, email verification), ...

Nuxt full-stack Vue framework with SSR, auto-imports, and file-based routing. Use when working with Nuxt apps, server routes, useFetch, middleware, or hybrid rendering.

Use when auditing Nuxt data-fetching, performance, or client-server pagination schema boundaries. NOT for 非 Nuxt 專案，NOT for general code review。

根據 plan package 的 `tasks.md`，以 don't stop until deliver / One-Shot 執行已解鎖 task。一輪恰好 1 個 task 或 Parallel Hint 批次；驗證後立刻回寫 `[X]` 再繼續，直到交付。不能跳步驟。

Use when the user wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt, animate, colorize, extract, or otherwise improve a frontend interface. Covers websites, landing pages, dashboards, product UI, app shells, components, forms, settings, onboarding, and empty states. Handles UX review, visual hierarchy, information architecture, cognitive load, accessibility, performance, responsive behavior, theming, anti-patterns, typography, fonts, spacing,...

Session 交接與 bounded delegation。Use when `/handoff` 要登記進度、在支援的 runtime 交給 successor，或由 Codex upstream 派 native bounded work。NOT for 單純 commit 收尾（走 `/commit`）。

Use immediately after a successful git push when the repo has GitHub Actions and CI / deploy completion must be watched — including slice draft PRs; also use when 查詢某 run 或某 SHA、撈 run log 證據、查 runner 佇列。CI 紅燈修回同一張 PR。NOT for 修 CI 紅燈本身的實作步驟（那是拿到結果後的除錯流程）。

Use when requirements are incomplete, ambiguous, conflicting, or require user decisions before implementation.

Verification, testing, review, screenshots, and evidence rules. Use when testing, reviewing, debugging, collecting evidence, or claiming completion.

Specification and requirements workflow rules. Use when work involves SDD, BDD, SpecFormula, decisions, or structured plans.

Session, delegation, handoff, work tracking, and follow-up rules. Use when planning work, delegating, opening worktrees, coordinating agents, or ending a session.

Authentication, secrets, production access, and security boundary rules. Use when changing identity, authorization, credentials, production MCP access, or user lifecycle behavior.

Runtime, deployment, local service, and infrastructure rules. Use when changing Cloudflare, Nitro, APIs, tunnels, ports, service URLs, or operational configuration.

Use for durable documentation, shared knowledge, decisions, onboarding, rule authoring, or technical debt.

Frontend, interaction, accessibility, localization, and UX integrity rules. Use when changing UI, forms, display values, interactions, translations, or visual completeness.

Commit, CI, release, and repository delivery rules. Use when committing, changing CI, preparing delivery, or handling repository state.

Database, schema, storage, logging, and data-path rules. Use when changing persistence, migrations, queries, RLS, database environments, or application logging.

Code quality, error handling, shell safety, language, and maintainability rules. Use when implementing or refactoring code, scripts, or language-specific components.

Reviews skill instructions, trigger boundaries and distribution contracts; not product code.

Audits queries, transactions, consistency and persistence resource lifetimes; read-only.

Audits implemented architecture boundaries, dependencies and ownership; not target design or plan review.