メニュー
Meta-orchestrator — dispatches to the right skill for the task. Use before any non-trivial work.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Library-agnostic Flutter/Dart code review checklist covering widget best practices, state management patterns (BLoC, Riverpod, Provider, GetX, MobX, Signals), Dart idioms, performance, accessibility, security, and clean architecture.
Structured 6-phase debugging. Build feedback loop first, reproduce deterministically, hypothesize with ranked falsifiable theories, instrument one variable at a time, fix with regression test, cleanup. Use when a bug exists, tests fail unexpectedly, or behavior is wrong and cause is unknown.
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
Database migration best practices for schema changes, data migrations, rollbacks, and zero-downtime deployments across PostgreSQL, MySQL, and common ORMs (Prisma, Drizzle, Kysely, Django, TypeORM, golang-migrate).
Run integration and e2e tests after unit tests pass. Use after /supergraph:fix when unit tests are green.
Plan-aware graph-enhanced code review before merge. CRITICAL issues block merge. Use after fix/verify.
| name | supergraph |
| description | Meta-orchestrator — dispatches to the right skill for the task. Use before any non-trivial work. |
| mcp | codebase-memory-mcp |
Graph evidence uses codebase-memory-mcp scoped by CBM_PROJECT. Orientation
loads get_architecture aspects overview, layers, boundaries, clusters,
and hotspots, plus validated hubs, bridges, and test-gaps recipes. If
optional graph evidence is unavailable, label it unavailable and use Serena or
filesystem evidence.
Dispatch to the right skill. 1% rule: if it might apply, invoke it.
| User intent | Skill to invoke |
|---|---|
| "start", "begin", unclear scope | /supergraph:analyze |
| "plan", "lên kế hoạch", explicit plan request | /supergraph:plan |
| "implement", "build", "execute" (plan saved) | /supergraph:execute |
| "fix bug", "debug", "why failing" | /supergraph:fix |
| "test", "TDD", "add tests" | /supergraph:tdd |
| "refactor", "clean up", "reorganize" | /supergraph:plan (then execute) |
| integration/e2e tests, after unit green | /supergraph:integration |
| "done?", "verify", before commit/PR | /supergraph:verify |
| "review", "merge", "PR", before merge | /supergraph:review |
| Need project context | /supergraph:scan |
/supergraph:tdd directly/supergraph:plan with lightweight tasks/supergraph:analyze first, then plan"Add X" or "Fix Y" is the WHAT. Skills determine HOW. Never skip a skill because the task "feels simple."
All skills depend on /supergraph:scan being loaded first in the session.
When dispatching subagents (executor, code-reviewer, plan-writer, plan-reviewer):