Best AI Prompts for Laravel: Eloquent, Controllers & Alpine.js Hooks

The best AI prompts for Laravel developers: 15 copyable templates built on real framework conventions — service classes, Eloquent scopes, observers, queued jobs, Form Requests, middleware, Cashier billing, and Vite — for Laravel 11 apps.

Building Modern Laravel 11 Apps with AI Assistance

Laravel developer workflows thrive when prompts follow standard framework conventions: Thin Controllers, Dedicated Service Layers, and Eloquent model scopes.

15 Copyable Laravel Prompts

• 1. Service Class Extraction Prompt: Act as a Laravel software architect. Refactor this heavy controller method into a dedicated Service Class and Action pattern. Implement proper DB transactions, dependency injection, and throw custom exceptions.
• 2. Eloquent Query Optimization Scope: Act as a Senior Laravel Engineer. Refactor this complex Eloquent query with multiple nested relations and aggregate functions into reusable model scopes, implementing efficient eager loading.
• 3. Custom Model Observer Hooks: Act as a Laravel developer. Write a custom Eloquent Observer class that triggers user audits, logs changes, updates cache states, and dispatches event notifications when database rows change.
• 4. Artisan Command CLI Progress: Act as a Laravel developer. Write a custom Artisan command that imports data from a CSV file. Implement CLI progress bars, table report summaries, log file output, and exception captures.
• 5. Database Seeder Configuration: Act as a database engineer. Write a Laravel DatabaseSeeder script using factory relationships, state states, and transaction safeguards to seed complex user-post-comment relationships.
• 6. Middleware Policy Gate Guard: Act as a Laravel security engineer. Write a custom HTTP Middleware class and matching Policy gate to restrict admin route accesses to users with specific roles and authenticated IP addresses.
• 7. Job Queue Queueable Worker: Act as a backend developer. Write a queueable Laravel Job class that processes massive PDF report compilations, handles job failures, implements retry backoffs, and logs errors.
• 8. API Resource Formatter: Act as an API designer. Design a Laravel JsonResource class structure that formats user profiles, nests relationship links, customizes payload outputs, and formats metadata tags.
• 9. Eloquent Polymorphic Relation: Act as a database architect. Define Eloquent model relationships, migrations, and database seeders for a polymorphic comment system that can belong to both Posts and Products.
• 10. Blade Component with Alpine: Act as a frontend Laravel developer. Create a reusable Blade component for a dropdown select menu. Utilize Alpine.js logic to support search filtering, keyboard navigation, and transitions.
• 11. Custom Form Request Validation: Act as a security auditor. Write a custom Laravel FormRequest class validating a complex multi-field payload. Implement custom rules, sanitization steps, and localized error messages.
• 12. Laravel Cashier Subscription Setup: Act as a billing specialist. Write a Laravel controller method implementing Stripe subscription purchases using Laravel Cashier, handling customer registration, cards, and webhooks.
• 13. Custom Exception Handler Mapping: Act as a systems engineer. Configure custom exception mapping rules in Laravel 11. Catch specific API authentication failures and return clean, standardized JSON response envelopes.
• 14. Artisan Scheduler Cron Setup: Act as a systems administrator. Write scheduling entries inside console kernel scheduling definitions to trigger database backups, clean temporary files, and email reports.
• 15. Laravel Vite Asset compilation: Act as a frontend assets specialist. Set up Vite integration in Laravel 11. Configure CSS/JS paths, hot module reloading, code-splitting modules, and asset optimization pipelines.

Context Rules for Laravel Prompts

• Pin the version: "Laravel 11" — the structure changed significantly vs Laravel 8/9 (no `Kernel.php`, new middleware config in `bootstrap/app.php`).
• Name the layer: "put it in a Service class" vs "in the controller" — Laravel has a clear architectural home for everything.
• Specify the Artisan pattern: Service, Action, Job, Observer, Scope, FormRequest, Resource, Middleware — the model knows these names.
• Ask for queue/transaction handling: Laravel's superpower is `dispatch()` + `DB::transaction()` — mention them or get sync code.
• Paste the migration/schema: for any model/relationship prompt, the actual column list prevents guessing.

$response = Http::withHeaders(["X-API-Key" => config("services.rsflowhub.key")])
    ->post("https://rsflowhub.com/api/v1/ai/chat", ["message" => "Hello AI"]);

Frequently Asked Questions