laravel:writing-plans
Writing Plans (Laravel)
Turn a confirmed design into a sequence of small, testable steps. Include guardrails and validation before handoff.
Structure
- Scaffolding
- Runner: confirm Sail or host
- Branch & workspace prep (worktrees optional)
- Data Model
- Migrations and factories (one commit per change)
- Seeders if needed for demo flows
- Services & Interfaces
- Controllers/Requests/Resources (or actions)
- Ports & adapters for external systems
- Jobs/events/listeners as needed
- Tests (TDD)
- Feature tests for behavior; unit tests for pure logic
- Use factories; verify failure first, then pass
More from jpcaparas/superpowers-laravel
laravel:routes-best-practices
Keep routes clean and focused on mapping requests to controllers; avoid business logic, validation, or database operations in route files
97laravel:blade-components-and-layouts
Compose UIs with Blade components, slots, and layouts; keep templates pure and testable
96laravel:quality-checks
Unified quality gates for Laravel projects; Pint, static analysis (PHPStan/Psalm), Insights (optional), and JS linters; Sail and non-Sail pairs provided
87laravel:performance-caching
Use framework caches and value/query caching to reduce work; add tags, locks, and explicit invalidation strategies for correctness
84laravel:tdd-with-pest
Apply RED-GREEN-REFACTOR with Pest or PHPUnit; use factories, feature tests for HTTP, and parallel test runners; verify failures before implementation
83laravel:queues-and-horizon
Operate and verify queues with or without Horizon; safe worker flags, failure handling, and test strategies
83