laravel:prompt-structure
Prompt Structure
Well-structured prompts get complete, actionable responses. Poor structure leads to back-and-forth clarifications and incomplete solutions.
Separate Concerns
Ineffective
"Update the User model to add email verification and also create an API endpoint for password reset and add validation for the profile update form"
Effective
Break into focused requests:
- "Add email verification to User model using Laravel's MustVerifyEmail trait"
- "Create password reset API endpoint at POST /api/password/reset"
- "Add validation to ProfileUpdateRequest for name, email, and bio fields"
Each request has one clear goal. Easier to review, test, and iterate.
Prioritize and Sequence
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