Merge branch 'feature/configure-sail-binary-path' of github.com:iWader/boost into feature/configure-sail-binary-path

Author: pushpak1300

.ai/foundation.blade.php

@@ -8,7 +8,7 @@
 ## Foundational Context
 This application is a Laravel application and its main Laravel ecosystems package & versions are below. You are an expert with them all. Ensure you abide by these specific packages & versions.
 
-- php - {{ PHP_VERSION }}
+- php - {{ PHP_MAJOR_VERSION }}.{{ PHP_MINOR_VERSION }}
 @foreach (app(\Laravel\Roster\Roster::class)->packages()->unique(fn ($package) => $package->rawName()) as $package)
 - {{ $package->rawName() }} ({{ $package->name() }}) - v{{ $package->majorVersion() }}
 @endforeach

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

@@ -4,27 +4,27 @@
 # Laravel 11
 
 - CRITICAL: ALWAYS use `search-docs` tool for version-specific Laravel documentation and updated code examples.
-@if (file_exists(base_path('app/Http/Kernel.php')))
+@if (file_exists(app_path('Http/Kernel.php')))
 - This project upgraded from Laravel 10 without migrating to the new streamlined Laravel 11 file structure.
 - This is perfectly fine and recommended by Laravel. Follow the existing structure from Laravel 10. We do not need to migrate to the Laravel 11 structure unless the user explicitly requests it.
 
 ## Laravel 10 Structure
-- Middleware typically lives in `app/Http/Middleware/` and service providers in `app/Providers/`.
+- Middleware typically lives in `{{ $assist->appPath('Http/Middleware/') }}` and service providers in `{{ $assist->appPath('Providers/') }}`.
 - There is no `bootstrap/app.php` application configuration in a Laravel 10 structure:
-    - Middleware registration is in `app/Http/Kernel.php`
-    - Exception handling is in `app/Exceptions/Handler.php`
-    - Console commands and schedule registration is in `app/Console/Kernel.php`
-    - Rate limits likely exist in `RouteServiceProvider` or `app/Http/Kernel.php`
+    - Middleware registration is in `{{ $assist->appPath('Http/Kernel.php') }}`
+    - Exception handling is in `{{ $assist->appPath('Exceptions/Handler.php') }}`
+    - Console commands and schedule registration is in `{{ $assist->appPath('Console/Kernel.php') }}`
+    - Rate limits likely exist in `RouteServiceProvider` or `{{ $assist->appPath('Http/Kernel.php') }}`
 @else
 - Laravel 11 brought a new streamlined file structure which this project now uses.
 
 ## Laravel 11 Structure
-- In Laravel 11, middleware are no longer registered in `app/Http/Kernel.php`.
+- In Laravel 11, middleware are no longer registered in `{{ $assist->appPath('Http/Kernel.php') }}`.
 - Middleware are configured declaratively in `bootstrap/app.php` using `Application::configure()->withMiddleware()`.
 - `bootstrap/app.php` is the file to register middleware, exceptions, and routing files.
 - `bootstrap/providers.php` contains application specific service providers.
 - No app\Console\Kernel.php - use `bootstrap/app.php` or `routes/console.php` for console configuration.
-- Commands auto-register - files in `app/Console/Commands/` are automatically available and do not require manual registration.
+- Commands auto-register - files in `{{ $assist->appPath('Console/Commands/') }}` are automatically available and do not require manual registration.
 @endif
 
 ## Database

.ai/laravel/12/core.blade.php

@@ -1,27 +1,27 @@
 # Laravel 12
 
 - CRITICAL: ALWAYS use `search-docs` tool for version-specific Laravel documentation and updated code examples.
-@if (file_exists(base_path('app/Http/Kernel.php')))
+@if (file_exists(app_path('Http/Kernel.php')))
 - This project upgraded from Laravel 10 without migrating to the new streamlined Laravel file structure.
 - This is perfectly fine and recommended by Laravel. Follow the existing structure from Laravel 10. We do not need to migrate to the new Laravel structure unless the user explicitly requests it.
 
 ## Laravel 10 Structure
-- Middleware typically lives in `app/Http/Middleware/` and service providers in `app/Providers/`.
+- Middleware typically lives in `{{ $assist->appPath('Http/Middleware/') }}` and service providers in `{{ $assist->appPath('Providers/') }}`.
 - There is no `bootstrap/app.php` application configuration in a Laravel 10 structure:
-    - Middleware registration happens in `app/Http/Kernel.php`
-    - Exception handling is in `app/Exceptions/Handler.php`
-    - Console commands and schedule register in `app/Console/Kernel.php`
-    - Rate limits likely exist in `RouteServiceProvider` or `app/Http/Kernel.php`
+    - Middleware registration happens in `{{ $assist->appPath('Http/Kernel.php') }}`
+    - Exception handling is in `{{ $assist->appPath('Exceptions/Handler.php') }}`
+    - Console commands and schedule register in `{{ $assist->appPath('Console/Kernel.php') }}`
+    - Rate limits likely exist in `RouteServiceProvider` or `{{ $assist->appPath('Http/Kernel.php') }}`
 @else
 - Since Laravel 11, Laravel has a new streamlined file structure which this project uses.
 
 ## Laravel 12 Structure
-- In Laravel 12, middleware are no longer registered in `app/Http/Kernel.php`.
+- In Laravel 12, middleware are no longer registered in `{{ $assist->appPath('Http/Kernel.php') }}`.
 - Middleware are configured declaratively in `bootstrap/app.php` using `Application::configure()->withMiddleware()`.
 - `bootstrap/app.php` is the file to register middleware, exceptions, and routing files.
 - `bootstrap/providers.php` contains application specific service providers.
-- The `app\Console\Kernel.php` file no longer exists; use `bootstrap/app.php` or `routes/console.php` for console configuration.
-- Console commands in `app/Console/Commands/` are automatically available and do not require manual registration.
+- The `{{ $assist->appPath('Console/Kernel.php') }}` file no longer exists; use `bootstrap/app.php` or `routes/console.php` for console configuration.
+- Console commands in `{{ $assist->appPath('Console/Commands/') }}` are automatically available and do not require manual registration.
 @endif
 
 ## Database

.ai/livewire/4/skill/livewire-development/SKILL.blade.php

@@ -47,18 +47,18 @@
 
 ### Choosing a Component Format
 
-Before creating a component, check `config/livewire.php` for directory overrides, which change where files are stored. Then, look at existing files in those directories (defaulting to `app/Livewire/` and `resources/views/livewire/`) to match the established convention.
+Before creating a component, check `config/livewire.php` for directory overrides, which change where files are stored. Then, look at existing files in those directories (defaulting to `{{ $assist->appPath('Livewire/') }}` and `resources/views/livewire/`) to match the established convention.
 
 ### Component Format Reference
 
 | Format | Flag | Class Path | View Path |
 |--------|------|------------|-----------|
 | Single-file (SFC) | default | — | `resources/views/livewire/create-post.blade.php` (PHP + Blade in one file) |
-| Multi-file (MFC) | `--mfc` | `app/Livewire/CreatePost.php` | `resources/views/livewire/create-post.blade.php` |
-| Class-based | `--class` | `app/Livewire/CreatePost.php` | `resources/views/livewire/create-post.blade.php` |
+| Multi-file (MFC) | `--mfc` | `{{ $assist->appPath('Livewire/CreatePost.php') }}` | `resources/views/livewire/create-post.blade.php` |
+| Class-based | `--class` | `{{ $assist->appPath('Livewire/CreatePost.php') }}` | `resources/views/livewire/create-post.blade.php` |
 | View-based | ⚡ prefix | — | `resources/views/livewire/create-post.blade.php` (Blade-only with functional state) |
 
-Namespaced components map to subdirectories: `make:livewire Posts/CreatePost` creates files at `app/Livewire/Posts/CreatePost.php` and `resources/views/livewire/posts/create-post.blade.php`.
+Namespaced components map to subdirectories: `make:livewire Posts/CreatePost` creates files at `{{ $assist->appPath('Livewire/Posts/CreatePost.php') }}` and `resources/views/livewire/posts/create-post.blade.php`.
 
 ### Single-File Component Example
 

.ai/tailwindcss/3/skill/tailwindcss-development/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: tailwindcss-development
-description: "Styles applications using Tailwind CSS v3 utilities. Activates when adding styles, restyling components, working with gradients, spacing, layout, flex, grid, responsive design, dark mode, colors, typography, or borders; or when the user mentions CSS, styling, classes, Tailwind, restyle, hero section, cards, buttons, or any visual/UI changes."
+description: "Always invoke when the user's message includes 'tailwind' in any form. Also invoke for: building responsive grid layouts (multi-column card grids, product grids), flex/grid page structures (dashboards with sidebars, fixed topbars, mobile-toggle navs), styling UI components (cards, tables, navbars, pricing sections, forms, inputs, badges), adding dark mode variants, fixing spacing or typography, and Tailwind v3/v4 work. The core use case: writing or fixing Tailwind utility classes in HTML templates (Blade, JSX, Vue). Skip for backend PHP logic, database queries, API routes, JavaScript with no HTML/CSS component, CSS file audits, build tool configuration, and vanilla CSS."
 license: MIT
 metadata:
   author: laravel

.ai/tailwindcss/4/skill/tailwindcss-development/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: tailwindcss-development
-description: "Styles applications using Tailwind CSS v4 utilities. Activates when adding styles, restyling components, working with gradients, spacing, layout, flex, grid, responsive design, dark mode, colors, typography, or borders; or when the user mentions CSS, styling, classes, Tailwind, restyle, hero section, cards, buttons, or any visual/UI changes."
+description: "Always invoke when the user's message includes 'tailwind' in any form. Also invoke for: building responsive grid layouts (multi-column card grids, product grids), flex/grid page structures (dashboards with sidebars, fixed topbars, mobile-toggle navs), styling UI components (cards, tables, navbars, pricing sections, forms, inputs, badges), adding dark mode variants, fixing spacing or typography, and Tailwind v3/v4 work. The core use case: writing or fixing Tailwind utility classes in HTML templates (Blade, JSX, Vue). Skip for backend PHP logic, database queries, API routes, JavaScript with no HTML/CSS component, CSS file audits, build tool configuration, and vanilla CSS."
 license: MIT
 metadata:
   author: laravel

.ai/tailwindcss/core.blade.php

@@ -6,6 +6,7 @@
 
 use Illuminate\Database\Eloquent\Model;
 use Illuminate\Support\Collection;
+use Illuminate\Support\Str;
 use Laravel\Boost\Install\Assists\Inertia;
 use Laravel\Roster\Enums\NodePackageManager;
 use Laravel\Roster\Enums\Packages;
@@ -272,6 +273,11 @@ public function sailBinaryPath(): string
         return Sail::binaryPath();
     }
 
+    public function appPath(string $path = ''): string
+    {
+        return ltrim(Str::after(app_path($path), base_path()), DIRECTORY_SEPARATOR);
+    }
+
     /**
      * @return Collection<string, Skill>
      */

src/Install/GuidelineAssist.php

@@ -7,6 +7,7 @@
 use Laravel\Boost\Mcp\Methods\CallToolWithExecutor;
 use Laravel\Boost\Mcp\Prompts\LaravelCodeSimplifier\LaravelCodeSimplifier;
 use Laravel\Boost\Mcp\Prompts\UpgradeInertiav3\UpgradeInertiaV3;
+use Laravel\Boost\Mcp\Prompts\UpgradeLaravelv13\UpgradeLaravelV13;
 use Laravel\Boost\Mcp\Prompts\UpgradeLivewirev4\UpgradeLivewireV4;
 use Laravel\Boost\Mcp\Tools\ApplicationInfo;
 use Laravel\Boost\Mcp\Tools\BrowserLogs;
@@ -111,6 +112,7 @@ protected function discoverPrompts(): array
         return $this->filterPrimitives([
             LaravelCodeSimplifier::class,
             UpgradeInertiaV3::class,
+            UpgradeLaravelV13::class,
             UpgradeLivewireV4::class,
         ], 'prompts');
     }

src/Mcp/Boost.php

@@ -22,10 +22,19 @@ class UpgradeInertiaV3 extends Prompt
 
     public function shouldRegister(Roster $roster): bool
     {
-        return $roster->uses(Packages::INERTIA_LARAVEL)
-            || $roster->uses(Packages::INERTIA_REACT)
-            || $roster->uses(Packages::INERTIA_VUE)
-            || $roster->uses(Packages::INERTIA_SVELTE);
+        if ($roster->uses(Packages::INERTIA_LARAVEL)) {
+            return true;
+        }
+
+        if ($roster->uses(Packages::INERTIA_REACT)) {
+            return true;
+        }
+
+        if ($roster->uses(Packages::INERTIA_VUE)) {
+            return true;
+        }
+
+        return $roster->uses(Packages::INERTIA_SVELTE);
     }
 
     public function handle(): Response