agent-creatorUse when creating expert agents. Generates agent.toml (model tier, sandbox_mode, developer_instructions with required sections) and wires skill references.
apex-methodologyUse when starting ANY development task -- feature, bug fix, refactor, hotfix (triggers: implement, create, build, fix, add feature, refactor, develop).
brainstormingUse when creating a feature/component or adding functionality. Fires BEFORE APEX Analyze to refine requirements via structured questioning.
challengeUse before a root-cause, a done/verified claim on a consequential change, an irreversible action, or a 2nd-time fix reaches the owner (APEX or plain conversation); also fires at every eLicit/Verify gate of full APEX. Not for code correctness (use sniper), nor for a trivial 1-3 line apex-quick change
code-qualityUse when validating code quality after modifications -- SOLID compliance, DRY duplication, linter errors, architecture violations. Do NOT use for functional verification (run verification FIRST, then code-quality).
elicitationUse when an expert agent self-reviews and self-corrects code after the Execute phase, before sniper validation (BMAD-METHOD elicitation techniques).
explorationUse when exploring an unfamiliar codebase -- architecture analysis, pattern detection, dependency mapping, rapid discovery.
fuse-browser-usageUse when about to call any mcp__fuse-browser__* tool. Routes fetch/crawl/SERP vs live browser session vs screenshot capture, and enforces the 4 ZERO-TOLERANCE rules -- read BEFORE the tool call.
lead-orchestrationCoordinate lead delegation safely, from owner request to verified report: the detailed version of the AGENTS.md COORDINATOR PATH (receive, check the place is free, analyze, decompose, distribute, brief, launch, follow, verify, control, report). Use before any lead delegation, subagent, or team actio
modularizeUse when converting existing code to modular architecture (Laravel, Next.js, React). Triggers: \"modularize\", \"convert to modules\", \"migrate to modular\", \"restructure modules\".
pr-summarySummarize current pull request with diff, comments, and changed files. Use when reviewing PRs or before merging.
react-effects-auditUse when auditing React or Next.js components for unnecessary or unsafe useEffect usage -- detects 9 anti-patterns from \"You Might Not Need an Effect\".
researchUse when researching documentation, best practices, or complex technical investigations -- Context7 + Exa + Sequential Thinking methodology.
skill-creatorUse when creating new skills, restructuring existing skills, or improving skill documentation.
sniper-checkUse when validating code quality after modifications. Runs sniper agent in isolated forked context for clean, fast validation.
tddUse when writing production code that needs tests -- new features, bug fixes, refactoring. Enforces RED-GREEN-REFACTOR before implementation.
think-in-codeUse when analyzing multiple files, auditing a codebase, scanning dependencies, or counting lines -- one Bash pipeline beats N sequential Read calls.
verificationUse when marking a task complete, finishing a feature, or claiming a bug fixed -- verifies functional resolution before closing. Do NOT use for lint/quality checks (use sniper AFTER this).
web-performanceUse when writing or changing web app code (front, backend, DB) to apply performance defaults, or when asked to audit performance (\"audit perf\", \"why is it slow\") -- 31 rules across front, backend+DB and infra, each with status, evidence and user cost. Advisory: audits and recommends, never edits