laravel/boost
54.9
Adequate · 19 September 2026
10.3k
lines of production code
PHP
primary language
1
measurement over time
What this system is
Laravel Boost is an AI-assisted development tool that configures and manages coding assistants for Laravel applications. It provides version-aware guidelines, skills, and Model Context Protocol (MCP) tools to help agents understand project conventions, execute safe database queries, and perform framework-specific upgrades. The system integrates with various IDE agents to enforce best practices and streamline development workflows.
How it got here
2025 — Laravel Boost initial release and AI integration
53 changes.
The project was rebranded from a generic Laravel package template to Laravel Boost, an AI-assisted development tool featuring an MCP server, agent management, and browser logging. This period established the core infrastructure for detecting AI coding assistants, installing skills and guidelines, and providing context-aware tools for database inspection and documentation search. Comprehensive test coverage was added to validate the new installation architecture, tool execution, and middleware behavior.
2026 — AI skill expansion and upgrade prompts
31 changes.
This period focused on expanding the AI assistant's capabilities by adding comprehensive development skills for Laravel ecosystem tools like Inertia, Livewire, Volt, and Folio, alongside new MCP prompts for framework upgrades. The work also introduced project rule management and enhanced security auditing for remote skills, supported by extensive test coverage for these new features and agent configurations.
Features
Add Inertia version and pages directory detection helper
The installation assistant now includes a new Inertia helper class that detects the installed Inertia version (checking for Laravel, React, Svelte, or Vue variants) and determines the correct pages directory path by scanning the project's resources/js folder. This enables the installer to make more accurate decisions about Inertia-specific features and file locations during project setup.
src/Install/Assists · high confidence
Add Laravel Code Simplifier Prompt
A new MCP prompt named 'laravel-code-simplifier' has been added to the system. This feature provides an automated code refinement capability that analyzes recently modified PHP/Laravel code and applies best practices for clarity, consistency, and maintainability while strictly preserving existing functionality. The prompt instructs the AI to simplify complex structures, enforce Laravel conventions, and optimize readability without altering behavior.
src/Mcp/Prompts/LaravelCodeSimplifier · high confidence
Add Livewire core guidelines
Introduces a new core guideline file for the Livewire framework, defining its primary purpose as building dynamic, reactive PHP interfaces without JavaScript and recommending the use of Alpine.js for client-side interactions. It establishes key behavioral expectations for users, specifically instructing them to keep state server-side to ensure UI reflection and to perform validation and authorization within actions, mirroring standard HTTP request handling patterns.
.ai/inertia-vue, .ai/livewire · high confidence
Add Wayfinder core guideline for TypeScript route generation
A new core guideline has been added to the Wayfinder configuration, instructing the AI assistant to use Wayfinder for generating TypeScript functions for Laravel routes. The guideline specifies that users should import these generated functions from \@/actions/\ for controllers or \@/routes/\ for named routes, and applies this rule to files within the \resources/js/\\\ directory.
.ai/wayfinder · high confidence
Added Folio routing skill with model binding and page content examples
A new Folio routing skill has been introduced to guide users through Laravel Folio file-based routing tasks. This skill provides specific instructions for creating pages using the \folio:page\ command, distinguishing between route parameters (e.g., \\[id\]\) and implicit Eloquent model binding (e.g., \\[User\]\), and defining named routes and middleware. It also includes practical examples for inline data loading and render hooks within Folio pages, along with a verification checklist to help debug common issues like 404 errors.
.ai/folio · high confidence
Added Inertia React core guidelines
A new core guideline file has been introduced for the Inertia React stack. It establishes a scoped rule for the \resources/js\ directory, specifically instructing developers to activate the \inertia-react-development\ mode when working with client-side patterns.
.ai/inertia-react · high confidence
Added Inertia.js v1 development guidelines for React and Svelte
New skill files have been added for Inertia.js v1 React and Svelte development, providing AI assistants with specific guidance on client-side patterns. These guidelines cover page component structure, client-side navigation using the \\<Link\>\ component and \router.visit\, and form handling via \router.post\ or the \useForm\ hook (React). They also explicitly list Inertia v1 limitations, warning against using v2 features such as deferred props, prefetching, and the \\<Form\>\ component, ensuring developers adhere to v1 constraints.
.ai/inertia-react/1, .ai/inertia-svelte/1 · high confidence
Added Inertia.js v2 development skills for React and Svelte
New AI skill files have been added for Inertia.js v2 development in both React and Svelte frameworks. These skills provide guidance on client-side navigation using the \<Link\> component, programmatic navigation via the router, and form handling with the \<Form\> component and useForm hook. The documentation includes examples for prefetching, error handling, and form reset props (resetOnError, resetOnSuccess, setDefaultsOnSuccess) where supported by the Inertia version.
.ai/inertia-react/2, .ai/inertia-svelte/2 · high confidence
Added Laravel Cloud deployment skill and guidelines
The system now includes a dedicated skill for deploying and managing Laravel applications on Laravel Cloud. This addition provides structured guidance for using the Cloud CLI, covering application setup, build and deploy workflows, resource configuration (databases, caches, object storage), secrets management, and troubleshooting. It also includes reference checklists for common multi-step operations like full environment setup and custom domain configuration, ensuring consistent and correct usage of Laravel Cloud features.
.ai/deployments · high confidence
Added Livewire 4 development skill and JavaScript hooks reference
This change introduces a new AI skill for Livewire 4 development, providing guidance on creating components (Single-File, Multi-File, Class-based), converting between formats, and leveraging v4-specific features like islands, async actions, and deferred loading. It also includes a reference document detailing the new JavaScript interceptor system (\interceptMessage\, \interceptRequest\) and magic properties (\$errors\, \$intercept\) available in Livewire 4.
.ai/livewire/4 · high confidence
Added Livewire v4 upgrade prompt
A new MCP prompt named 'upgrade-livewire-v4' has been added to provide step-by-step guidance for upgrading applications from Livewire v3 to v4. This prompt automatically registers for projects using the Livewire package and delivers a comprehensive guide covering installation, configuration key renames (such as layout and placeholder settings), breaking changes (like wire:scroll to wire:navigate:scroll), and testing strategies.
src/Mcp/Prompts/UpgradeLivewirev4 · high confidence
Added MCP Development Skill for Laravel
Introduced a new \mcp-development\ skill that provides comprehensive guidance for building Laravel Model Context Protocol (MCP) applications. This resource covers the full development lifecycle, including using Artisan generators (\make:mcp-\*\) to create servers, tools, resources, and prompts, as well as registering these primitives in \routes/ai.php\. It details implementation patterns for tools and resources using specific attributes and response shapes, explains how to build and integrate MCP Apps, and provides instructions for testing primitives directly or via the MCP Inspector. The skill also addresses authentication, authorization strategies, and connecting to external MCP servers using the included client.
.ai/mcp · high confidence
Added Volt Development skill for single-file Livewire components
A new skill file (.ai/volt/skill/volt-development/SKILL.blade.php) has been added to guide the development of single-file Livewire components using Volt. This entry provides documentation and examples for both functional and class-based Volt APIs, including instructions on using the \make:volt\ artisan command, writing tests with \Volt::test()\, and avoiding common pitfalls like mixing component styles or forgetting the \@volt\ directive.
.ai/volt/skill · high confidence
Added core guidelines for Livewire Volt single-file components
A new core guideline file has been introduced to standardize the use of Livewire Volt. It defines Volt as single-file components combining PHP logic and Blade templates, instructs developers to check existing components for style consistency (functional vs. class-based), and mandates the use of the \search-docs\ tool for version-specific documentation and the activation of the \volt-development\ context for related tasks.
.ai/volt · high confidence
Initial release of Laravel Boost with agent management and browser logging
This change introduces the initial v0.0.1 of Laravel Boost, replacing the previous \LaravelPackage\ scaffolding. It adds a \BoostManager\ facade and service provider to manage a registry of IDE agents (including Amp, Antigravity, Claude Code, Copilot, Cursor, Factory, Grok Build, Junie, Kiro, OpenCode, Pi, and Zed) and registers console commands for installation, updates, and skill management. Additionally, it implements a browser logs watcher that captures frontend logs via a dedicated route and Blade directive, storing them in a configurable \browser\ log channel.
src · high confidence
Introduce Laravel Boost MCP server with subprocess-based tool execution
The \src/Mcp\ location now contains the core implementation for the 'Laravel Boost' MCP server (v0.0.1), which registers a suite of tools (e.g., Tinker, DatabaseSchema), resources, and prompts (e.g., UpgradeInertiaV3, LaravelCodeSimplifier). Tool execution is handled via \ToolExecutor\, which runs commands in isolated subprocesses using a configurable PHP executable path and a default 180-second timeout, while \ToolRegistry\ manages tool allow-lists and discovery. The server also exposes custom SVG icon metadata and supports filtering tools, resources, and prompts via configuration includes/excludes.
src/Mcp · high confidence
Introduce browser-side console log capture service
A new BrowserLogger service has been added to inject a JavaScript helper into the browser, which intercepts standard console methods (log, debug, info, warn, error, table) and global uncaught errors. These logs are batched and sent to a backend endpoint, with support for configurable log levels via the boost.browser\_log\_levels configuration. The implementation includes safety measures to prevent crashes when serializing complex objects (such as Livewire's $wire proxy) by avoiding JSON.stringify on raw objects, and it supports Vite CSP nonces for secure script injection.
src/Services · high confidence
Introduce core Boost concern traits for UI, HTTP, logging, and Blade rendering
This change introduces five new traits in the \src/Concerns\ namespace that form the foundation of the Laravel Boost console and rendering experience. \DisplayHelper\ provides the visual interface, including a gradient ASCII logo, themed badges, and formatted output notes. \MakesHttpRequests\ standardizes HTTP client usage with a specific User-Agent and conditional SSL verification for local/testing environments. \ReadsLogs\ implements robust log file resolution (supporting stack and daily drivers) and chunked reading to retrieve recent entries, including JSON-formatted logs. \RendersBladeGuidelines\ handles the safe compilation of Blade templates within guidelines, protecting against PHP execution and escaping issues. Finally, \ReportsSkillParseFailures\ surfaces warnings when skills with invalid frontmatter are skipped during registration.
src/Concerns · high confidence
Introduce database schema introspection tool for MySQL, PostgreSQL, and SQLite
A new database schema tool has been added that allows users to inspect the structure of their database, including tables, views, stored procedures, functions, triggers, check constraints, and sequences. The implementation uses a driver-based architecture with specific drivers for MySQL/MariaDB, PostgreSQL, and SQLite, ensuring accurate metadata retrieval for each database type (e.g., joining TABLE\_CONSTRAINTS for MySQL check constraints, filtering pg\_catalog for PostgreSQL). A factory automatically selects the appropriate driver based on the configured database connection.
src/Mcp/Tools/DatabaseSchema · high confidence
Introduce isolated tool execution method
Added a new \CallToolWithExecutor\ method class that handles JSON-RPC tool/call requests by delegating execution to a \ToolExecutor\. This change introduces process isolation for tool execution, allowing tools to run in a separate context while properly handling missing parameters, unknown tool names, and execution errors via JSON-RPC responses.
src/Mcp/Methods · high confidence
Introduce new Boost console commands and UI themes
This change adds several new console commands to the \src/Console\ directory: \boost:add-skill\ for installing skills from remote GitHub repositories, \boost:list-skills\ to display available skills, \boost:execute-tool\ for internal tool execution, \boost:mcp\ to start the MCP server, and \boost:update\ to refresh guidelines and skills. It also introduces a \Theme\ enum in \src/Console/Enums\ that defines available UI themes (LaravelRed, Gray, Ocean, Vaporwave, Sunset) with associated gradient colors for the console interface.
src/Console · high confidence
Introduce project rule management with YAML frontmatter parsing and index generation
The system now supports recording and managing project-specific rules via a new \RuleRepository\ and \RuleFrontmatter\ class. Users can define rules using YAML frontmatter (e.g., \paths\ and \body\) in markdown files, which are parsed to associate rules with specific file globs. The repository handles writing these rules, maintaining a managed directory for Boost-generated rules, and automatically generating a \index.md\ file that maps file paths to their corresponding rule files, allowing users to quickly find applicable rules before planning or editing code.
src/Rules · high confidence
Introduction of DetectionStrategy interface for platform-agnostic detection
A new DetectionStrategy interface has been added to the Install/Contracts namespace, defining a contract for detecting whether an application is installed on a machine. This interface accepts configuration details and an optional Platform enum, allowing the installation logic to adapt its detection behavior based on the specific operating system or environment.
src/Install/Contracts · high confidence
Laravel 11 structural and convention guidelines added
The system now provides specific guidance for Laravel 11 projects, distinguishing between the new streamlined file structure (using \bootstrap/app.php\ for middleware and routing) and legacy Laravel 10 structures. It instructs developers on Laravel 11 conventions such as declarative middleware registration, native query limiting, model casts via methods, and new Artisan commands like \make:enum\ and \make:interface\.
.ai/laravel/11 · high confidence
New 'Infer Conventions' skill and updated core guidelines for Laravel Boost
Laravel Boost now includes a new 'Infer Conventions' skill that systematically analyzes an application's codebase to detect and record coding conventions as durable, path-scoped rules in \.ai/rules\. The core guidelines have been updated to support this by instructing the AI to check for existing rules before planning changes, and to use the new \record-rule\ MCP tool for committing decisions. Additionally, the guidelines now specify using \search-docs\ with a \packages\ array for scoping and advise against including package names in search queries, while also clarifying the usage of the \tinker\ tool and Artisan commands.
.ai/boost · high confidence
New Inertia v2 to v3 upgrade prompt
A new MCP prompt named 'upgrade-inertia-v3' has been added to provide step-by-step guidance for upgrading applications from Inertia v2 to v3. This feature automatically detects projects using Inertia (Laravel, React, Vue, or Svelte adapters) and offers a structured migration process, including identifying breaking changes like event renames and dependency removals, updating package versions, and verifying the upgrade.
src/Mcp/Prompts/UpgradeInertiav3 · high confidence
New Laravel core guidelines for AI-assisted development
A new core guideline file has been added to the Laravel skill, providing specific instructions for AI agents on how to follow Laravel best practices. This includes directives to use Artisan commands for creating files (with \--no-interaction\), prefer named routes for URL generation, default to Eloquent API Resources for APIs, and utilize factories and feature tests for testing. It also includes a troubleshooting tip for Vite manifest errors.
.ai/laravel · high confidence
New Laravel testing best practices skill for AI-assisted test generation
A new 'Testing Best Practices' skill has been added to the Laravel guidelines, providing comprehensive rules for designing, writing, and reviewing tests. The skill dynamically adapts its guidance based on whether the project uses Pest or PHPUnit, including specific instructions for assertions, naming conventions, and file layout. It covers key testing areas such as endpoint coverage, tenant isolation, security boundaries, test data management, and suite performance optimization. The skill also provides detailed guidance on isolating dependencies using fakes and mocks, and includes specific rules for browser testing with Pest's browser plugin or Laravel Dusk.
.ai/laravel/skill/testing-best-practices · high confidence
New MCP prompt for Laravel 12 to 13 upgrade guidance
Added a new Model Context Protocol (MCP) prompt that provides step-by-step guidance for upgrading applications from Laravel 12.x to 13.0. The prompt is automatically registered for projects using Laravel 12 and covers key breaking changes, including the renaming of CSRF middleware to \PreventRequestForgery\, updates to cache serialization settings (\serializable\_classes\), and changes to cache key prefixes and session cookie names. It also details updates to queue event properties and upsert behavior, helping developers systematically identify and fix compatibility issues during the upgrade process.
src/Mcp/Prompts/UpgradeLaravelv13 · high confidence
New MCP tools for application context, database inspection, and project rules
This update introduces several new Model Context Protocol (MCP) tools to enhance AI agent capabilities within Laravel applications. The new \ApplicationInfo\ tool provides a comprehensive overview of the environment, including PHP and Laravel versions, the database engine, and a list of installed PHP and JavaScript packages. Database management is improved with \DatabaseConnections\ to list available connections, \DatabaseQuery\ for executing read-only SQL queries with robust safety checks (including read-only transaction enforcement), and \DatabaseSchema\ for retrieving detailed table structures, views, and routines with caching support. Debugging is streamlined with \BrowserLogs\ and \ReadLogEntries\ for accessing frontend and backend logs, as well as \LastError\ for retrieving the most recent backend error. Additionally, \GetAbsoluteUrl\ simplifies URL generation, \SearchDocs\ allows querying version-specific Laravel ecosystem documentation, and \Tinker\ enables safe execution of PHP code within the application context. Finally, the \RecordRule\ tool allows agents to persist durable project rules to markdown files for long-term context.
src/Mcp/Tools · high confidence
New Wayfinder Development skill for Laravel frontend integration
Added a new 'wayfinder-development' skill that guides users in integrating Laravel Wayfinder with frontend frameworks like React, Vue, and Svelte (including Inertia). The skill provides documentation on generating typed route functions, importing actions, and using form helpers, with specific examples for Inertia's Form component and useForm hook.
.ai/wayfinder/skill · high confidence
Security
Security auditing and validation for remote skills
The remote skill system now includes a security audit step and stricter validation when adding skills from GitHub. A new \SkillAuditor\ class contacts an external audit service to assess the risk level of remote skills, and the \GitHubSkillProvider\ enforces path validation to prevent directory traversal attacks, rejects potentially dangerous file types (like PHP scripts), and ensures that only valid skill directories are discovered and downloaded.
src/Skills · high confidence
Behavioural changes
Application info is now served via a dedicated resource backed by the application tool
The ApplicationInfo resource has been introduced to expose comprehensive application details (PHP version, Laravel version, database engine, and installed packages) as a retrievable resource at file://instructions/application-info.md. Instead of returning static content, the resource dynamically executes the ApplicationInfo tool to fetch current data, ensuring the information remains up-to-date and avoiding redundancy with the tool itself.
src/Mcp/Resources · high confidence
Consolidated Inertia guidelines with version-specific support
The Inertia Laravel guidelines have been consolidated into a single core file that automatically adapts to the installed Inertia version. The system now detects whether Inertia React, Vue, or Svelte is active and provides specific instructions for each. For Inertia v3, the guidelines cover new features like standalone HTTP requests, optimistic updates, and the removal of Axios and \Inertia::lazy()\. For v2, it details deferred props and infinite scrolling, while v1 guidelines explicitly warn against using these newer features.
.ai/inertia-laravel · high confidence
Introduce Laravel Boost configuration and remove legacy package config
The application now includes a new \config/boost.php\ file that allows users to enable or disable the entire Boost feature set, manage project rules and scoped guidelines, exclude specific guidelines or skills, define custom executable paths for PHP, Composer, NPM, and vendor binaries, and configure the browser logs watcher along with specific log levels to capture. This new configuration replaces the deleted \config/laravel-package.php\, which previously handled domain, path, and middleware settings for a generic Laravel package, effectively consolidating configuration around the new Boost functionality.
config · high confidence
Introduction of installation strategy and platform enums
The installation logic now utilizes new strongly-typed enums to manage configuration and environment detection. The new McpInstallationStrategy enum defines specific modes for MCP installation (shell, file, or none), replacing previous loose string handling. Additionally, the Platform enum provides a standardized way to detect the current operating system (Darwin, Linux, or Windows) via a static current() method, ensuring consistent platform identification across the installer.
src/Install/Enums · high confidence
Laravel 12 core guidelines with version-aware structure detection
The Laravel 12 guidelines now include a new core file that automatically detects whether the project uses the legacy Laravel 10 structure (via \Http/Kernel.php\) or the modern Laravel 11/12 structure (via \bootstrap/app.php\). This allows the AI to provide accurate, version-specific advice on middleware registration, service providers, and console command handling. Additionally, the guidelines specify that Laravel 12 supports native query limiting and recommends using the \casts()\ method on models instead of the \$casts\ property.
.ai/laravel/12 · high confidence
Laravel Boost rebranded from package-template with upgraded tooling and configuration
The repository has been rebranded from a generic Laravel package template to Laravel Boost, an AI-assisted development tool. This change updates the project identity, including the README, CHANGELOG, and UPGRADE documentation, to reflect the new product name and purpose. The project now includes Pint and Rector configuration files to enforce code quality and style standards, replacing the previous minimal setup. Additionally, the Tailwind CSS and Vite configuration files have been removed, indicating a shift away from the default frontend asset pipeline provided by the template. The PHPStan configuration has been updated to level 5, and the PHPUnit configuration now includes an architecture test suite and specific environment variables for testing.
(repo-wide) · high confidence
New AI guidelines for test enforcement, Sail usage, and foundational conventions
The AI assistant now follows new, specific guidelines for testing, environment usage, and general conventions. It is instructed to enforce test coverage for logic changes while skipping tests for pure styling updates, and to consult the testing best practices skill. For projects using Laravel Sail, the assistant must prefix all commands with the Sail binary and use Sail-specific commands for starting services and running Artisan/Composer/Node tasks. Additionally, foundational rules now emphasize checking installed package versions before using APIs, adhering to existing code conventions, and reusing existing components.
.ai · high confidence
New extensible detection strategy system for installation prerequisites
The installation process now uses a new strategy-based architecture to detect environment prerequisites, replacing the previous implementation. Users can now define checks via configuration keys for files, directories (with wildcard and path expansion support), or shell commands. The system includes a factory that infers the detection type from the config structure and supports composite strategies for multiple checks, with robust handling for platform-specific path expansion and command execution signals.
src/Install/Detection · high confidence
New installation architecture for AI guidelines, skills, and MCP configuration
The installation process now uses a structured set of classes to manage AI coding assistant integration. The \GuidelineComposer\ and \GuidelineWriter\ handle the discovery, composition, and writing of AI guidelines to the agent's configuration file, while the \SkillComposer\ and \SkillWriter\ manage the installation of agent skills. Additionally, the \McpWriter\ and \AgentsDetector\ handle the detection of installed agents and the configuration of Model Context Protocol (MCP) servers. This replaces the previous installation logic with a more modular approach that supports third-party packages, conditional guidelines, and specific agent integrations like Herd and Sail.
src/Install · high confidence
New support utilities for command normalization, package detection, and configuration management
The \src/Support\ directory now includes several new helper classes that underpin the application's ability to manage third-party guidelines and skills. \CommandNormalizer\ handles splitting command strings into executable paths and arguments, while \Fences\ allows transformations on markdown content while preserving code blocks. \Config\ provides a structured interface for reading and writing the \boost.json\ configuration file, including settings for skills, MCP, and Cloud. \Composer\ and \Npm\ classes define first-party package scopes and detect whether a package belongs to the Laravel/Livewire ecosystem. \PackageRegistry\ maps these packages to specific guideline names and locates their resource paths. Finally, \RenderFailures\ and \SkillParseFailures\ track and report errors when loading external guidelines or skills, preventing crashes from malformed content.
src/Support · high confidence
Prevents script injection into non-HTML and Livewire navigate responses
The new InjectBoost middleware now safely skips injecting the Boost script when the response is not a standard HTML document. It explicitly excludes JSON, file downloads, redirects, and Livewire navigate requests (detected via the x-livewire-navigate header), ensuring that the browser logger script is only added to responses containing actual HTML structure.
src/Middleware · high confidence
Rebrand to Laravel Boost and removal of legacy frontend assets
The product has been rebranded to Laravel Boost, reflected by the addition of a new SVG icon in the resources/icons directory. As part of this transition, the previous frontend infrastructure has been removed; specifically, the Tailwind CSS configuration (app.css), the JavaScript entry point (app.js) handling Axios and timezone setup, and the Blade layout template (layout.blade.php) defining the base HTML structure and global JavaScript variables have all been deleted.
resources · high confidence
Refined package guideline discovery with priority and exclusion rules
The package guideline discovery process now intelligently filters which guidelines are loaded based on project dependencies. It excludes specific packages like Boost and Sail from automatic discovery, ensures that guidelines for MCP and Livewire are only included when they are direct dependencies (preventing noise from indirect imports), and implements a priority system where higher-priority packages (e.g., Pest over PHPUnit, FluxUI Pro over FluxUI Free) exclude their lower-priority counterparts. This results in a cleaner, more relevant set of guidelines presented to the user based on their actual project setup.
src/Install/Concerns · high confidence
Removal of legacy scaffolding and build artifacts
The package has removed its default database scaffolding, including the \ModelFactory\ class and the migration that created the \table\ entity, as well as the pre-built frontend assets (\app.css\ and \app.js\). This indicates a shift away from providing a pre-configured database schema and static build output, likely requiring users to generate their own models, migrations, and build their frontend assets independently.
(repo-wide) · high confidence
Robust MCP configuration file writer for JSON and TOML
The installation process now uses a dedicated, robust writer to inject MCP server configurations into both JSON/JSON5 and TOML config files. This new logic handles complex formatting requirements such as preserving indentation, managing trailing commas, stripping leading BOMs from TOML files, and correctly identifying existing servers to prevent duplicates. It also supports unquoted keys in JSON5, ignores commented-out entries, and ensures files end with a trailing newline, providing a more reliable and consistent configuration update experience across different file formats.
src/Install/Mcp · high confidence
Standardize Laravel Herd usage guidelines
The .ai/herd configuration now includes a core guideline file that instructs the AI to rely on the existing Laravel Herd installation for serving the application rather than running local server commands, and to use the \herd\ CLI for managing services and PHP versions.
.ai/herd · high confidence
Standardized Pest testing guidelines for AI assistants
The AI assistant now follows a unified set of instructions for Pest-based testing. It is instructed to create tests using the \make:test --pest\ command, adhere to specific naming conventions (e.g., \SomeFeatureTest\ instead of \Feature/SomeFeatureTest\), and avoid deleting test files without approval. The guidelines also specify how to run tests efficiently using the \--compact\ flag and direct the assistant to consult the \testing-best-practices\ skill for broader coverage and structure advice.
.ai/pest, .ai/phpunit · high confidence
Unified agent installation and detection system
The installation experience for AI coding agents (including Codex, Claude Code, Copilot, Cursor, Junie, and others) has been restructured around a new \Agent\ base class and specific implementations in \src/Install/Agents\. This change introduces a standardized, extensible framework for detecting agent presence on the system and within projects, configuring MCP server connections (supporting both file-based and shell strategies), and managing agent-specific guidelines and skills paths. Users benefit from more reliable agent detection, consistent configuration handling across different IDEs and tools, and the ability to customize paths and behaviors via configuration keys.
src/Install/Agents · high confidence
Updated Flux UI development skills to reflect free and Pro component availability
The AI skill definitions for Flux UI development have been updated to accurately distinguish between the free and Pro editions. The free edition skill now explicitly lists the available free components (such as button, modal, and table) and warns against using Pro-only features, while the Pro edition skill includes the full component list (adding items like accordion, chart, and kanban) and provides specific usage examples for Pro components like tables. This ensures the AI assistant applies the correct component set and patterns based on the installed Flux UI license.
.ai/fluxui-pro · high confidence
Updated Inertia Vue development guidelines for v2 features
The Inertia Vue skill documentation has been updated to support Inertia.js v2, introducing guidance for new client-side capabilities such as the \\<Form\>\ component, deferred props, and prefetching. The entry also clarifies that v1-specific limitations (like the lack of \\<Form\>\ support) no longer apply in this context, ensuring developers use the correct patterns for their Inertia version.
.ai/inertia-vue/2 · high confidence
Updated Laravel Pint formatting instructions to support agent formatter
The guidelines for using Laravel Pint have been updated to conditionally instruct users to run the \--format agent\ flag when the environment supports the Pint Agent Formatter. This ensures that code formatting commands are executed correctly based on the available tooling capabilities, while falling back to standard \--dirty\ usage for environments without agent support.
.ai/pint · high confidence
Updated Livewire development guidelines for version 3
The AI skill for Livewire development has been updated to reflect the changes in Livewire 3. Key behavioral shifts include \wire:model\ now being deferred by default (requiring \.live\ for real-time updates), components moving to the \App\\Livewire\ namespace, and Alpine.js being bundled with Livewire (removing the need for manual inclusion). The JavaScript hooks have also changed, replacing \livewire:load\ with \livewire:init\ and updating event dispatching to use \$this-\>dispatch()\. Users should verify their application setup against these new conventions.
.ai/livewire/3 · high confidence
Updated PHP guidelines with version-specific features and core style rules
The PHP AI guidelines have been refreshed to include specific recommendations for PHP 8.4 and PHP 8.5, such as using new array functions (\array\_find\, \array\_first\) and the pipe operator for chaining. A new core guideline file establishes baseline coding standards, including mandatory curly braces for control structures, constructor property promotion, explicit return types, and TitleCase for enum keys. These changes ensure the AI assistant provides accurate, modern PHP syntax advice across different language versions.
.ai/php · high confidence
Fixes
Preserved empty Prompts directory structure
The empty Prompts directory under src/Mcp is now preserved in the repository via a .gitkeep file, ensuring the directory structure remains intact even when no prompt files are present.
src/Mcp/Prompts · high confidence
Test coverage
Added architecture tests and expanded test infrastructure for Laravel Boost; Added test coverage for MCP tools; Added test fixtures for AI guidelines; Added test fixtures for MCP configuration parsing and tool error handling; Added test fixtures for enum guideline generation; Added test fixtures for skills with various frontmatter and template syntaxes; Added test fixtures for vendor guideline loading and compatibility; Added tests for Boost service provider, facade, and browser logs route; Added tests for CommandDetectionStrategy; Added tests for InjectBoost middleware behavior; Added tests for MCP CallToolWithExecutor method; Added tests for MCP tool execution and registry; Added tests for MCP upgrade and simplifier prompts; Added tests for agent executable path resolution; Added tests for console commands and skill management; Added tests for guideline, rule, and skill composition during installation; Added tests for managed rules and rule parsing fixtures; Added unit tests for Blade guideline rendering and snippet processing; Added unit tests for BoostManager agent registration; Added unit tests for Inertia pages directory detection; Added unit tests for MCP configuration file writers; Added unit tests for MySQL schema driver and schema driver factory; Added unit tests for Support helpers; Added unit tests for install detection strategies; Added unit tests for remote skill discovery, auditing, and security validation; Added unit tests for the Install module components; Unit tests for AI agent installation and configuration.
Dependencies
Rebrand to Laravel Boost and update dependencies
The package has been rebranded from 'laravel/package-template' to 'laravel/boost', with the namespace updated to 'Laravel\\Boost' and the description changed to reflect its role in accelerating AI-assisted development. Composer dependencies have been updated to support Laravel 13.x (via illuminate packages ^11.45.3\|^12.41.1\|^13.0), added support for Guzzle ^7.9\|^8.0, and updated laravel/mcp to ^0.7.1\|^0.8.0\|^0.9.0\|^1.0. Development dependencies now include rector/rector ^2.1 and updated versions of pint, mockery, testbench, pest, and phpstan. The package-lock.json and package.json files for Node.js dependencies have been removed.
(dependencies) · high confidence
Written by watchdog.canine.dev from the codebase's own history, inside the signed delivery this page is composed from.
How this codebase got here
Baseline
- First survey — no prior run to compare against. CAI 55.
Lenses
- Code Health 95
- Architecture 98
- Maturity 60
- Readiness 73
- Security 79
- Accessibility 37
Changes since last survey
- 300 commits — 251 feature/other, 49 fixes
By area
- (root) — 57 commits
- src/Install — 46 commits
- src/Mcp — 30 commits
- .ai/laravel — 29 commits
- src/Console — 16 commits
- tests/Unit — 15 commits
- .github/workflows — 10 commits
- src/Concerns — 10 commits
- tests/Feature — 9 commits
- .ai/livewire — 8 commits
- config/boost.php — 8 commits
- src/BoostServiceProvider.php — 6 commits
- .ai/boost — 5 commits
- src/Skills — 5 commits
- .ai/mcp — 4 commits
- tests/Fixtures — 4 commits
- .ai/deployments — 3 commits
- .ai/fluxui-free — 3 commits
- .ai/pest — 3 commits
- .ai/php — 3 commits
Notable commits
- fix: Fix Inertia v3 layout props API name (useLayoutProps -> setLayoutProps) (#823)
- fix: Fix Sail is incorrectly detected as active inside devcontainers (#614)
- fix: Fix SearchDocs crashing when MCP client passes array params as JSON strings (#604)
- fix: Fix TypeError when Blade::render returns an HtmlString (#796)
- fix: Fix blade skills with code before frontmatter are parsed correctly (#582)
- fix: Fix code snippet styling to use fenced code blocks (#555)
- fix: Fix code styling
- fix: Fix code styling
- fix: Fix crash in GuidelineAssist when app/ directory does not exist (#617)
- fix: Fix default value for browser_logs config in core guideline (#574)
- fix: Fix duplicate guidelines when using symlinked paths (#634)
- fix: Fix entity decoding in fenced code blocks (#997)
- fix: Fix inverted enum naming convention condition in PHP guideline (#732)
- fix: Fix issue with Codex not automatically triggering the login flow (#592)
- fix: Fix newline normalization corrupting multi-byte UTF-8 in rule files (#947)
- fix: Fix non-GitHub SSH remote validation (#986)
- fix: Fix normalizeCommand() splitting absolute paths containing spaces (#553)
- fix: Fix null bytes in laravel-best-practices style.md skill (#727)
- fix: Fix path separators and trailing newlines in install output (#790)
- fix: Fix post-install Next steps URL (#587)
- …and 280 more
Written by watchdog.canine.dev from the codebase's own history, inside the signed delivery this page is composed from.
Survey your own repository
laravel/boost was measured the same way every project in this corpus was: the same rubric, at a pinned commit, with the result published in full. Point a surveyor at a repository you know and see whether you agree with it.
About this page
- The score is its most recent published measurement, taken on 19 September 2026 at a pinned commit. It is not a live figure and does not change until the project is measured again.
- Measured at commit ff9c331a64223f63380eb76e00568e4ac0ec6f24 — the exact code this score is about.
- Scored under rubric-2026.09.15 — the same rubric and the same method as every other entry in this index.
- Measured by watchdog.canine.dev using codehealth-analyzer preprod-13a154b7f5d1.