feat: bunch of guidelines, nicer install command, add ENV to herd mcp, browser logs, report feedback tool

Author: ashleyhindle

.ai/boost/core.blade.php

@@ -1,6 +1,16 @@
+# URLs
+- Whenever you create a URL use the `get-absolute-url` tool to ensure you're using the correct scheme, domain/IP, and port.
+
+# Artisan
+- Use the `list-artisan-commands` tool when needing to call an artisan command to triple check the available params
+
+# Tinker / Debugging
+You should use the ‘tinker’ tool from Boost MCP when you need to run PHP to check data, test code, or debug code.
+
+
 # Searching documentation
 
-Boost comes with a powerful `search-docs` tool you should use before any other approaches. This tool automatically passes a list of installed packages and their versions to the remote Boost API, so it returns only version-specific documentation specific for the user's circumstance.
+Boost comes with a powerful `search-docs` tool you should use before any other approaches. This tool automatically passes a list of installed packages and their versions to the remote Boost API, so it returns only version-specific documentation specific for the user's circumstance. You should pass an array of packages to filter docs on if you know you need docs for particular packages.
 
 'search-docs' tool is perfect for all Laravel related packages. Laravel, inertia, pest, livewire, nova, nightwatch, and more.
 
@@ -15,10 +25,3 @@
 4. Mixed Queries - query=middleware "rate limit" - "middleware" AND exact phrase "rate limit"
 5. Multiple Queries - queries=["authentication", "middleware"] - ANY of these terms
 
-# URLs
-
-- Whenever you create a URL use the `get-absolute-url` tool to ensure you're using the correct scheme, domain/IP, and port.
-
-
-# Artisan
-- Use the `list-artisan-commands` tool when needing to call an artisan command to triple check the available params

.ai/core.blade.php

@@ -1,11 +1,42 @@
 # Laravel Boost Guidelines
 The Laravel Boost Guidelines are specifically curated by Laravel maintainers for this project. These guidelines should be followed closely to help enhance the user's experience and satisfaction.
 
+# Foundational Context
+This project is a Laravel app and its main Laravel ecosystems package & versions are below. You are an expert with them all. Ensure we abide by these specific packages & versions.
+
+- php - {{ PHP_VERSION }}
+@foreach (app(\Laravel\Roster\Roster::class)->packages()->unique(fn ($package) => $package->rawName()) as $package)
+    - {{ $package->rawName() }} ({{ $package->name() }}) - v{{ $package->majorVersion() }}
+@endforeach
+
 @if(!empty(config('boost.project_purpose')))
-    <purpose-of-this-project>
-        {!! config('boost.project_purpose') !!}
-    </purpose-of-this-project>
+    Project purpose: {!! config('boost.project_purpose') !!}
 @endif
 
-# Conventions
-Follow existing conventions. When creating or editing a file, check sibling files for the correct structure, approach, naming.
+## Conventions
+- You must follow all existing code conventions used in this project. When creating or editing a file, check sibling files for the correct structure, approach, naming.
+- Use descriptive names. e.g. `isRegisteredForDiscounts` not `discount()`
+- Always use strict typing: declare(strict_types=1);
+
+## Project Structure & Architecture
+- Stick to existing directory structure - no new base folders without approval.
+- No dependency changes without approval.
+
+## Constructors
+- Use PHP 8 constructor property promotion in `__construct()`
+<code-snippet>public function __construct(public GitHub $github) { }</code-snippet>
+- Do not allow empty `__construct()` with zero parameters.
+
+## Type Declarations
+- Always use explicit return type declarations for methods and functions.
+- Use appropriate PHP type hints for method parameters.
+
+## Comments
+- Prefer PHPDoc blocks, otherwise use minimal-to-zero comments, unless there is something very complex going on.
+
+## Replies
+- Be concise in your explanations - focus on what's important rather than explaining obvious details.
+
+## Documentation files
+- You must only create documentation files if explicitly requested by the user.
+

.ai/enforce-tests.blade.php

@@ -1,2 +1 @@
 - Every change must be programmatically tested. Write a new test, or update an existing test, then run the tests to make sure they pass.
-- Run the individual tests edited to 

.ai/fluxui_free/core.blade.php

@@ -0,0 +1,3 @@
+- **Use Flux UI components** when available
+- Fallback to standard Blade components if Flux is unavailable.
+- Use Laravel Boost's `search-docs` tool to get the exact documentation & code snippets available for this project.

.ai/fluxui_pro/core.blade.php

@@ -0,0 +1,3 @@
+- **Use Flux UI components** when available
+- Fallback to standard Blade components if Flux is unavailable.
+- Use Laravel Boost's `search-docs` tool to get the exact documentation & code snippets available for this project.

.ai/inertia-laravel/1/core.blade.php

@@ -1 +1 @@
-Inertia v1 core.md
+Inertia v1 core

.ai/inertia-laravel/2/core.blade.php

@@ -1 +1 @@
-Inertia v2 core.md
+Inertia v2 core

.ai/inertia-laravel/core.blade.php

@@ -1,3 +1 @@
-## InertiaJS Laravel Package
-
-Super core inertia js laravel package
+## InertiaJS Laravel Package Core

.ai/laravel/10/core.blade.php

@@ -1 +1 @@
-Laravel 10 Core.md
+Laravel 10 Core

.ai/laravel/11/core.blade.php

@@ -1 +1,4 @@
-Laravel 11 Core.md
+Laravel 11 Core
+
+- **No app\Console\Kernel.php** - use `bootstrap/app.php` for console configurations
+- **Commands auto-register** - files in `app/Console/Commands/` are automatically available