brainstorming
Beginner-first idea-to-plan workflow for Laravel projects. Use before writing implementation code when the user wants to brainstorm features, shape requirements, compare options, validate architecture, and create a reviewed high-level plan for writing-plans.
setup-wizard
First-time Laravel project setup. Use when the user says 'get started', 'set up a new project', 'install Laravel', or 'I am a beginner'. Installs Laravel Herd, creates a fresh project with Inertia + React, Pest, and Filament, and configures Laravel Boost for Claude Code. Runs once per project only.
interview
Conducts in-depth technical interviews about implementation plans. Use when the user wants to be interviewed about a plan, spec, or feature before implementation, or when they say "interview me" or "let's discuss the plan".
subagent-driven-development
Execute an approved implementation plan in the current session by dispatching one subagent per task, with spec and quality reviews after each task. Use after writing-plans when tasks are mostly independent.
debug-coach
Beginner-first Laravel debugging coach. Use when user reports an error, broken feature, failed command, or unexpected app behavior.
writing-plans
Beginner-first implementation planning from an approved design. Use after brainstorming, or when the user already approved requirements and wants a step-by-step Laravel implementation plan before coding.
prompt-router
Route beginners to the best VibeMastery prompt/skill for their current Laravel task. Use when user says things like 'what prompt should I use', 'help me ask this better', or 'what should I tell Claude/Codex/OpenCode'.
executing-plans
Execute an approved implementation plan in a separate session with checkpoint reviews. Use after writing-plans when the user wants batched progress updates before more work continues.