laravel-superpowers

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 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 implementing any feature or bugfix with Pest — BEFORE writing implementation code. Provides the complete Laravel TDD workflow: Pest syntax, factories, HTTP testing, facade faking, Feature vs Unit selection. In Laravel codebases, invoke this instead of superpowers:test-driven-development. Trigger on any 'add feature', 'fix bug', 'implement', 'build' request inside a Laravel project.