Support for excluding AI guidelines

[tmannherz]

It will be useful if Boost allowed for excluding certain AI guidelines.

As a use case, we use Laravel Nova which has Inertia as a dependency. We don't use Inertia in our frontend and don't want the Inertia guidelines included in the output of the .md files that Boost creates, yet there's no way to exclude them.

Perhaps config/boost.php could be configured with excludes?

return [
    ...

    'excluded_guidelines' => [
        'inertia-laravel/core',
        'inertia-laravel/v2',
    ],
];

Alternatively, it would allow for better customization of guidelines if Boost allowed for overriding an individual guideline file entirely. Boost could prefer the file located in ./.ai if it existed over the package-supplied version.

For example, if I had .ai/php/core.blade.php in my project root, the contents of that file would take precedence over vendor/laravel/boost/.ai/php/core.blade.php in the generated .md files.

[ncphillips]

+1 from us

A slightly different scenario from my team: we've decided to not use FormRequest objects at all. Instead, we use laravel-data for validation and define the authorization checks inside the constructors of Controllers. We like this approach because of how easily it lets us generate Typescript definitions. This is counter to the Controllers and Validation guidelines that boost provides. The rest of the guidelines in that file fit just fine.

[Slund]

+1 from us

We use a modular structure approach, so customizing e.g. the Testing guidelines would be beneficial.

[Plytas]

+1 here too.

I'm also curious if there's a way for 3rd party packages to hook into this? I know we can add blade files to .ai/guidelines/*, and also 3rd party packages could provide their own MCP servers, but it would be nice to hook into this and expose tools through artisan boost:mcp command.

For example a good tool would be docs search for all spatie packages.

[kamilkozak]

Confirming this need. In my case we primarily use classic Livewire components and only sprinkle in Volt, yet the generated guideline states: “This project uses Livewire Volt… New pages requiring interactivity must also use Livewire Volt,” and even promotes the functional API, which is controversial for our team. New interactive pages shouldn’t be forced into Volt; the guidance should follow the project’s existing conventions.

In another codebase we use Inertia.js for the admin panel but keep a few Livewire components on the marketing/landing side, so we also don’t want the AI to default to Livewire there. An excluded_guidelines option and/or per-project .ai overrides (preferred over vendor files) would solve both scenarios.