laravel-livewire-superpowers

Dispatch a Pilot 2.0 Phase-N audit using the active plan-doc's per-phase scope. Reads the active plan, extracts Phase N's audit prompt, dispatches laravel-best-practices in parallel.

Generate a sprint retrospective report from plan-doc + git history + audit reports. Outputs Pilot 2.0 contract compliance per phase, skill-invocation count vs expected, drift instances, test-suite delta, screenshot artifacts list.

Show current sprint state, Pilot 2.0 obligations, hook compliance, and open follow-ups for the active Laravel project. Read-only.

Use in Laravel projects before/during any plan-phase that touches Eloquent models, migrations, queries, or architectural placement (Actions vs Services vs Form Objects vs Controllers). Audits for N+1 queries, missing eager-loading, preventLazyLoading status, migration safety, performance smells, and architectural-pattern drift. Reads existing app/Actions/, app/Services/, app/Http/Requests/, app/Data/ for sibling-canon check — recommends consistency with what's already in the codebase, not generic best practices. Trigger on any plan-phase that touches models, migrations, queries, or layering decisions.

Use in Laravel projects whenever you need to know the current best practice for implementing any feature, pattern, or architectural decision. Does extensive web research across official docs, core team blogs, and trusted community sources (Spatie, Laracasts, Laravel News) to find the most up-to-date 2025/2026 approach. Spawn whenever someone asks: 'how should I implement X?', 'what is the best way to do Y in Laravel?', 'should I use X or Y?', 'is there a package for Z?', 'is my current approach still best practice?'. Also great for validating existing implementation against current standards.

Use in Laravel projects with Echo + Reverb (or Echo + Pusher) when designing any realtime feature, broadcasting event, presence/private channel, or notification fan-out. Default-scans routes/channels.php + app/Notifications/ + existing Echo client callbacks to surface reuse-vs-new-channel decisions BEFORE the brainstorm proposes a redundant broadcast. Catches the canonical 'we already have App.Models.User.{id} broadcasting both forum notifications AND private_message_received — sound playback is pure client-side' insight. Trigger on any 'realtime', 'broadcast', 'Echo', 'Reverb', 'WebSocket', 'live update', 'presence', or 'notification fan-out' work.

Use in Laravel+Flux Pro projects before/during any Flux-component-touching implementation phase. Audits double-tooltip wrapping (<flux:tooltip> around components that self-tooltip), position/align convention drift, slot vs string-prop trade-offs, wire:ignore-zone reactive-descendant issues on Flux components, and editor.spacer placement. Reads vendor/livewire/flux-pro/stubs/resources/views/flux/ as ground truth, cites file:line refs in findings. Trigger before any <flux:*> write/edit.

Use in Laravel+Livewire projects before/during any Livewire-touching implementation phase. Audits API existence (catches fabricated methods like $this->hasLoading), wire:ignore zones, Form-Object patterns, Echo/broadcasting integration, and lifecycle-hook usage. Verifies via PHP reflection against vendor/livewire/livewire/src/Component.php — ground truth, not docs. Trigger automatically before any plan-phase that mentions Livewire components, $this->X() methods, wire:* directives, or #[On]/#[Computed]/#[Locked] attributes.

Use in Laravel + Livewire 4 + Flux Pro v2 projects when building any UI surface that has dynamic content, loading states, animations, audio, or user-perceptible state changes. Surfaces WCAG 2.2 + ARIA + reduced-motion patterns systematically (role/aria-live/aria-busy/wire:loading.attr/prefers-reduced-motion/Page-Visibility) instead of leaving them to per-phase audit discovery. In Livewire codebases, use this alongside superpowers:frontend-design (if available) for stack-specific depth. Trigger on any 'AI panel', 'streaming', 'loading state', 'notification', 'modal', 'animation', 'sound', 'toast', or any UI with perceivable state changes.

Use in Laravel projects BEFORE designing or implementing any feature, endpoint, or architectural change. Guides Laravel-specific design decisions: which layer owns the logic, Eloquent relationships, Event/Listener patterns, Policy/Gate design, queuing decisions. In Laravel codebases, invoke this alongside superpowers:brainstorming for the framework-specific layer. ALWAYS trigger when adding new functionality, designing a new endpoint, planning a new model relationship, or choosing between architectural patterns in Laravel.

Use in Laravel projects when completing a feature, reviewing code, or preparing for merge. Checks Laravel-specific concerns: N+1 queries, mass assignment protection, authorization coverage, validation completeness, security, performance. In Laravel codebases, invoke this alongside superpowers:requesting-code-review. Trigger on any 'review', 'check', 'PR', 'done with feature', 'ready to merge' in a Laravel project.

Use in Laravel projects when encountering any bug, test failure, unexpected behavior, N+1 queries, queue issues, or cache problems. Provides Laravel-specific debugging tools and workflows. In Laravel codebases, invoke this instead of superpowers:systematic-debugging. Trigger on any error, 500, unexpected output, slow query, or 'why is X not working' in a Laravel project.

Use in Laravel projects when writing a merge-request / pull-request body at sprint close-out. Generates the canonical MR shape (Summary / Decisions / Pilot 2.0 contract / Spec + Plan link / Test plan with file paths + assertion counts / Scope changes / Deferred items / Follow-up issues / Screenshots) from the project's plan-doc, /laravel-livewire-superpowers:status output, and git history. Standardizes the 15-minute manual close-out task. Trigger on 'write MR body', 'PR description', 'sprint close-out', 'ready to merge', or before pushing a feature branch.

14 hooks across 3 events