Guidelines based on detected FormRequest preferences (Strengthen wording around using Form Requests?)

[ashleyhindle]

Cursor created me a new controller, but it uses regular requests:

    public function slideChanged(Request $request): \Illuminate\Http\JsonResponse
    {
        // Log the slide change event
        Log::info('Slide changed event received', [
            'slide' => $request->input('slide'),
            'previous_slide' => $request->input('previousSlide'),
            'timestamp' => now(),
        ]);

        return response()->json(['status' => 'success']);
    }

[isaackearl]

I use spatie/laravel-data and replace FormRequests with laravel-data Request DTOs. I like that I can give my own ai-guidelines and tell it to never use FormRequests. If you add stronger language to the base laravel-boost.mdc rules, I'm wondering if there will be a way to disable certain instructions?

[ashleyhindle]

Great point @isaackearl 🤔 You can easily override Boost's guidelines with your own now, instructions here: https://github.com/laravel/boost?tab=readme-ov-file#overriding-boost-ai-guidelines

But, I don't want people to have to do this.

What I'd actually prefer is for Boost to detect your preferences based on existing code, then align its rules to those.

So if you don't use FormRequests, we don't add that section, but if you do then we add and strengthen that section.