laravel:brainstorming
Brainstorming (Laravel)
Use this when shaping features or refactors. Keep answers concise, then propose a design and gather confirmation before planning.
Ask (one at a time)
- Goal: What outcome should users achieve?
- Domain: Which bounded contexts or packages are involved?
- Data: New models/relations? Required queries and invariants?
- Interfaces: HTTP/API/CLI? Required inputs/outputs? Authz?
- Side‑effects: Email, storage, queues, external systems?
- Performance: Throughput, latency, pagination, N+1 risks?
- Observability: Logs, metrics, events, failure handling?
- Testing: TDD entry point, fixtures/factories, edge cases?
- Environment: Sail or host? DB/cache/mail/storage availability?
Propose
Present a design of 200–300 words, covering:
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