PHPackages sandermuller/project-boost-laravel - PHPackages - PHPackages [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register) 1. [Directory](/) 2. / 3. [Utility & Helpers](/categories/utility) 4. / 5. sandermuller/project-boost-laravel ActiveLibrary[Utility & Helpers](/categories/utility) sandermuller/project-boost-laravel ================================== Sync AI agent skills + guidelines for Laravel apps. Companion to laravel/boost: boost stays the MCP, this package owns the agent-file fanout (skills, guidelines, remote skills, tag filtering). 1.1.0(1mo ago)1449↑12.5%MITPHP ^8.3 Since May 25Compare [ Source](https://github.com/SanderMuller/project-boost-laravel)[ Packagist](https://packagist.org/packages/sandermuller/project-boost-laravel)[ Docs](https://github.com/sandermuller/project-boost-laravel)[ RSS](/packages/sandermuller-project-boost-laravel/feed)WikiDiscussions Synced 3w ago READMEChangelog (10)Dependencies (52)Versions (29)Used By (0) project-boost-laravel ===================== [](#project-boost-laravel) [![Latest Version on Packagist](https://camo.githubusercontent.com/494cd6893ecc75983ba9d86166812ee486307d931f5255518d38ead23d99fbb8/68747470733a2f2f696d672e736869656c64732e696f2f7061636b61676973742f762f73616e6465726d756c6c65722f70726f6a6563742d626f6f73742d6c61726176656c2e7376673f7374796c653d666c61742d737175617265)](https://packagist.org/packages/sandermuller/project-boost-laravel)[![GitHub Tests Action Status](https://camo.githubusercontent.com/bb5692ec344750773ed916ebc76f61df9cc28f92fd0b55f9fd6b2bbed5c72ad5/68747470733a2f2f696d672e736869656c64732e696f2f6769746875622f616374696f6e732f776f726b666c6f772f7374617475732f73616e6465726d756c6c65722f70726f6a6563742d626f6f73742d6c61726176656c2f72756e2d74657374732e796d6c3f6272616e63683d6d61696e266c6162656c3d7465737473267374796c653d666c61742d737175617265)](https://github.com/sandermuller/project-boost-laravel/actions/workflows/run-tests.yml)[![Total Downloads](https://camo.githubusercontent.com/f6575beef08d2005e0b94eb365e17ce40872ad56c3063e87aa9cf2195a6ddb9f/68747470733a2f2f696d672e736869656c64732e696f2f7061636b61676973742f64742f73616e6465726d756c6c65722f70726f6a6563742d626f6f73742d6c61726176656c2e7376673f7374796c653d666c61742d737175617265)](https://packagist.org/packages/sandermuller/project-boost-laravel)[![License](https://camo.githubusercontent.com/b2f18a534290e8b9d6f2418d0aa56eab792ecf0c75a59471ea2e6792f08d72d0/68747470733a2f2f696d672e736869656c64732e696f2f7061636b61676973742f6c2f73616e6465726d756c6c65722f70726f6a6563742d626f6f73742d6c61726176656c2e7376673f7374796c653d666c61742d737175617265)](LICENSE)[![Laravel Boost](https://camo.githubusercontent.com/90f2604136cf241bd1fa46f5c025c7dad12d8cdc1b66e7662c12003c7f79abf8/68747470733a2f2f62616467652e6c61726176656c2e636c6f75642f626f6f73742d62616467652e7376673f7374796c653d666c61742d737175617265)](https://github.com/laravel/boost) > The Laravel-app member of the [sandermuller boost family](#which-package-fits-your-role). Sits next to [`laravel/boost`](https://github.com/laravel/boost) in the same project. Boost keeps doing what it already does: MCP server, Laravel docs API, bundled Laravel skills. This package picks up everything else — fanning the generated agent files out across nine AI coding agents instead of four, and adding the family's filtering controls (`withTags()`, `withAllowedVendors()`, `withRemoteSkills()`, `boost where`). [![overview image](overview.png)](overview.png) You run Laravel Boost and this package together. Neither replaces the other; the design assumes they're installed side by side. Which package fits your role? ----------------------------- [](#which-package-fits-your-role) You're buildingInstallShipsA PHP application (not a package)[`sandermuller/project-boost-php`](https://github.com/sandermuller/project-boost-php)App-dev skills: dependency injection, legacy coexistence + the `foundation` guideline**A Laravel application****[`sandermuller/project-boost-laravel`](https://github.com/sandermuller/project-boost-laravel)****`laravel/boost` MCP coexistence + nine-agent fanout + tag filter + remote skills ← you are here**A framework-agnostic Composer package[`sandermuller/package-boost-php`](https://github.com/sandermuller/package-boost-php)Package-author skills + `lean` / `gitattributes` commandsA Laravel package[`sandermuller/package-boost-laravel`](https://github.com/sandermuller/package-boost-laravel)Laravel-package skills + `McpJsonEmitter`Your own skill bundle, or custom tooling[`sandermuller/boost-core`](https://github.com/sandermuller/boost-core)The sync engine. You supply the skills.What this adds on top of `laravel/boost` ---------------------------------------- [](#what-this-adds-on-top-of-laravelboost) `laravel/boost` alone+ `project-boost-laravel`MCP server (`boost:mcp`)✅✅ unchangedLaravel docs API + semantic search✅✅ unchangedBundled Laravel skills + guidelines✅✅ re-rendered through this package's pipelineTag filtering—✅ `withTags()`. Ship `inertia-vue-development` only on Inertia projectsRemote skill sources—✅ `withRemoteSkills()`. Pull GitHub-published `.skill` bundlesVendor allowlistauto via `composer.json`✅ explicit `withAllowedVendors()` for collision control`boost where` origin tracing—✅ host / vendor / remote / shadow attribution`project-boost:where` injection-set tracing—✅ symmetric, for the `laravel/boost` skill set this package injectsUser-scope sync—✅ `boost sync --scope=user` for globally-installed CLI toolsDoctor + path-repo audit—✅ `boost doctor --check-versions`Under the hood, `project-boost:install` calls `boost:install --mcp` so laravel/boost writes its MCP client config the same way it always does, then `project-boost:sync` takes over for the nine-agent fan-out. Install ------- [](#install) ``` composer require --dev sandermuller/project-boost-laravel ``` `laravel/boost` and `sandermuller/boost-core` come in transitively — do **not** require `sandermuller/boost-core` separately, it resolves through this package. Where do the skills come from? ------------------------------ [](#where-do-the-skills-come-from) Anywhere you want. Skill sources stack: - **Your own `.ai/skills/` folder**, hand-authored next to the rest of the project. Same convention `laravel/boost` uses, and `boost-core` picks them up automatically. - **A Composer-installed catalog package**. Any package that ships `resources/boost/skills/` works. I publish my personal catalog at [`sandermuller/boost-skills`](https://github.com/sandermuller/boost-skills) — adopt it if your preferences align with mine, or treat it as a template for your own. Private repo, public package, monorepo subfolder; Composer resolves all of them. - **External, non-Composer sources** via `withRemoteSkills()`. Pull GitHub-published `.skill` bundles or single-skill repos straight from the URL. - **`laravel/boost`'s bundled Laravel skills** plus whatever Laravel-aware third-party packages it knows about. Picked up through the injection seam this package adds. Mix and match freely. `withAllowedVendors()` gates Composer-scanned vendors (source 2) only — host skills (source 1), remote skills (source 3), and the `laravel/boost` bundle (source 4) are not gated by it. `withTags()` filters sources 2, 3, and 4. Host skills (source 1) bypass both gates: your project authored them, so the engine treats them as canonical and applies neither filter. First run --------- [](#first-run) ``` php artisan project-boost:install ``` What the wrapper does: 1. Runs `php artisan boost:install --mcp`. Boost writes its MCP client config; the `--mcp` flag keeps its `GuidelineWriter` and `SkillWriter` dormant, so this package owns the agent-file fan-out from here on. 2. Runs `php artisan project-boost:sync`. Discovers laravel/boost-bundled skills and guidelines, renders Blade templates, applies your `withTags()` filter, fans out to every agent you declared in `boost.php`. In CI / Docker / any non-TTY shell, the wrapper detects the absence of an interactive STDIN (`stream_isatty(STDIN)` plus the `--no-interaction` flag) and skips boost's install command entirely. It calls boost's `McpWriter` directly, once per agent in `boost.php`. No prompts, no integration multiselect, no crashes. Warning If you run `php artisan boost:install` **without** `--mcp`, boost's `GuidelineWriter` and `SkillWriter` fire and race this package over `CLAUDE.md` and the per-agent skill directories. Always go through `project-boost:install`, or pass `--mcp` explicitly. The `suppress_upstream_writers` flag below is the guardrail for muscle-memory mistakes. `boost.php` ----------- [](#boostphp) > **Config location.** boost-core resolves its config from `.config/boost.php`(canonical on boost-core ≥ 0.17) or a legacy root `boost.php` — this package's commands honor both. laravel/boost's own `boost.json` is a separate file that laravel/boost owns and resolves from the project root; it intentionally stays there and is not moved under `.config/`. Minimal: ``` use SanderMuller\BoostCore\Config\BoostConfig; use SanderMuller\BoostCore\Enums\Agent; use SanderMuller\BoostCore\Enums\Tag; return BoostConfig::configure() ->withAgents([Agent::CLAUDE_CODE, Agent::CURSOR, Agent::CODEX]) ->withTags([Tag::Laravel, Tag::Php]); ``` Skills are tag-gated. A skill ships if every tag in its `metadata.boost-tags` is also in your `withTags()`. Untagged skills always ship. `vendor/bin/boost tags` lists every tag your installed packages declare. For a worked example of how someone organizes a tag vocabulary across a catalog, see [`sandermuller/boost-skills`'s tag registry](https://github.com/sandermuller/boost-skills#tags). Common shapes: ProjectTagsLaravel + Livewire`Tag::Laravel, Tag::Php, 'livewire'`Laravel + Inertia React`Tag::Laravel, Tag::Php, 'frontend', 'inertia'`Laravel API only`Tag::Laravel, Tag::Php`+ Pest 4 + browser testsadd `'pest'`See the [`boost-core` README](https://github.com/sandermuller/boost-core) for the full `BoostConfig` surface. Commands -------- [](#commands) CommandDoes`project-boost:install`Wraps `boost:install --mcp` (boost owns MCP) and runs `project-boost:sync`. Auto-detects non-TTY for CI / Docker. Recommended entry point.`project-boost:install --no-sync`MCP only; skip the sync.`project-boost:sync`Discover, render, tag-filter, fan out to nine agents. Run after `composer install` or after editing `boost.php`.`project-boost:sync --dry-run`Preview the full sync pipeline (laravel/boost + host + scanned vendors + remote skills) in check mode. Requires `boost.php` or `.config/boost.php`.`project-boost:where`List the laravel/boost-bundled skills and guidelines this package injects, with per-skill ship / tag-filter / shadow status. The companion to `vendor/bin/boost where`, which covers the host, scanned-vendor, and remote origins.`project-boost:reconcile`Capture laravel/boost-seeded guidance (the `` block `boost:install` writes into `CLAUDE.md` / `AGENTS.md`) into `.ai/guidelines/` before a sync would overwrite it, back up each file, then sync. Run once after a first `boost:install` or when migrating. See [docs/laravel-coexistence.md](docs/laravel-coexistence.md).Coexistence with `laravel/boost` -------------------------------- [](#coexistence-with-laravelboost) ConcernOwnerMCP server (`boost:mcp` artisan command, `boost:install` MCP config writes)**`laravel/boost`**MCP config files (`.mcp.json`, `.amp/settings.json`, agent-specific)**`laravel/boost`**Laravel docs API + semantic search**`laravel/boost`**`CLAUDE.md` / `AGENTS.md` / `GEMINI.md` content**this package** (via `boost-core`)`.{agent}/skills//SKILL.md` files**this package** (via `boost-core`)Skill content discovery + Blade rendering**this package** (`LaravelBoostAssetReader` + `BladeRenderer`)Versioned-variant resolution (e.g. `pest/3` vs `pest/4`)**this package**. `Laravel\Roster\Roster::scan()` matches the host's installed majorTag filtering + collision resolution**`boost-core`**Remote skill fetching (`withRemoteSkills`)**`boost-core`****First-install takeover.** `boost:install` seeds its guidelines directly into your agent files inside a `` marker. If you have hand-edited those files, run `php artisan project-boost:reconcile` once before syncing — it captures your edits into `.ai/guidelines/` and backs the files up, so the (markerless, wholesale) sync never drops them. The full sequence and the data-loss mechanics are in [docs/laravel-coexistence.md](docs/laravel-coexistence.md). Things to avoid: - **A bare `vendor/bin/boost sync` on a wrapper project.** It bypasses this package's laravel/boost injection, assembles a smaller guidance set, and wholesale-overwrites your files with it. Always use `php artisan project-boost:sync`. - `php artisan boost:install` without `--mcp`. The interactive default re-engages boost's writers and races this package. - `php artisan boost:update`. Boost's bundled-asset refresh. Harmless but pointless; `project-boost:sync` re-renders on every run anyway. Auto-sync on `composer install` ------------------------------- [](#auto-sync-on-composer-install) In Laravel projects using this package, wire `@php artisan project-boost:sync` into composer's post-install / post-update hooks: ``` { "scripts": { "post-install-cmd": ["@php artisan project-boost:sync"], "post-update-cmd": ["@php artisan project-boost:sync"] } } ``` The `@php artisan project-boost:sync` hook routes through this package's wrapper, which walks `vendor/laravel/boost/.ai/`, pre-renders Blade templates with proper container context, and injects laravel/boost-bundled skills (`pest-testing`, `livewire-development`, `filament-development`, `inertia-development`, `eloquent-models`, and the rest) into the sync call. Without this hook, those bundled skills don't reach your agent directories — host skills + scanned vendors + remote skills still sync, but the laravel/boost set silently doesn't. ### Why not `BoostAutoSync::run`? [](#why-not-boostautosyncrun) `boost-core` ships a `SanderMuller\BoostCore\Scripts\BoostAutoSync::run` composer-script helper that invokes `vendor/bin/boost sync` (bare CLI). In Laravel projects using this package, that helper is the wrong hook: bare CLI bypasses this wrapper's injection pipeline entirely, so the laravel/boost-bundled skill set never reaches your agent directories. Operators who wire `BoostAutoSync::run` into their composer scripts typically don't notice — the bare-CLI sync still reports success, just against a smaller skill set than the wrapper would have surfaced. Use `@php artisan project-boost:sync` instead. A stray bare-CLI sync no longer *deletes* the wrapper's already-emitted skill files — the `BoostWrapper` contract (see [Architecture](#architecture)) declares them so the cleanup pass leaves them in place. But bare CLI still won't *(re)emit* the laravel/boost set, so `@php artisan project-boost:sync` remains the correct hook. (For non-Laravel projects consuming `boost-core` directly without a wrapper, `BoostAutoSync::run` IS the correct hook. The guidance above is Laravel-app-specific.) Defensive flag: `suppress_upstream_writers` ------------------------------------------- [](#defensive-flag-suppress_upstream_writers) Set `PROJECT_BOOST_SUPPRESS_UPSTREAM=true` in `.env` to enable a `CommandStarting` listener that intercepts ad-hoc `php artisan boost:install` calls and injects `--mcp` before they run. Any truthy value works (`=true`, `=1`, `=yes`). Off by default — `project-boost:install` already does the right thing in both TTY and non-TTY modes, so the flag is belt-and-suspenders for teams worried about muscle-memory mistakes. Note: this does not suppress boost's integrations writers (cloud / sail / nightwatch). `--mcp` short-circuits feature selection only; the integrations multiselect still runs in TTY mode, and selecting one triggers its writer. Remote skills ------------- [](#remote-skills) Declared in `boost.php` via `withRemoteSkills([RemoteSkillSource::githubBundle(...), RemoteSkillSource::githubPath(...)])`. The mechanism, cache behavior, `BOOST_GITHUB_TOKEN`, and `BOOST_REMOTE_STRICT` all live in [boost-core's README](https://github.com/sandermuller/boost-core#remote-skill-sources) — same surface in this package. Architecture ------------ [](#architecture) `LaravelBoostAssetReader` and `LaravelBoostGuidelineReader` walk `vendor/laravel/boost/.ai/`, render any `.blade.php` files through the package's `BladeRenderer` (which uses `laravel/boost`'s own `RendersBladeGuidelines` trait so `$assist` binds correctly), and hand the resulting `Skill[]` and `Guideline[]` to boost-core via `BoostSync::sync(injectedVendorSkills, injectedVendorGuidelines)`. From there it's boost-core's normal pipeline — tag filter, collision resolution, per-agent fan-out. See [boost-core's README](https://github.com/sandermuller/boost-core) for the engine internals. Guidelines are install-gated. `LaravelBoostGuidelineReader` emits only the core guidelines plus guidelines for packages the host actually installed, mirroring `laravel/boost`'s own `GuidelineComposer` detection (PHPUnit-vs-Pest priority, Sail opt-in, direct-only MCP / Livewire). An app never receives guidelines for packages it doesn't use — a Livewire + Filament + PHPUnit app won't get Inertia, Pest, or Sail guidance. Version-major sub-fragments are version-scoped too, on two axes: package dirs by exact installed major (a Laravel 12 app gets `laravel/12`, not `laravel/11` — they're alternative complete sets), and `php/8.x` cumulative-downward to your declared `require.php` floor (`php/8.4` features are usable on 8.5, so a project supporting `^8.3` keeps `≤8.3` and won't be told to use 8.5-only syntax it can't rely on). A `BoostWrapper` class implements boost-core's `BoostWrapperContract` (introduced in 0.11.0), declaring the per-agent skill-emit paths this package injects. A bare `vendor/bin/boost sync` (no wrapper injection) then preserves those files instead of flagging them stale-to-delete. Requires `boost-core ^1.0`. This package's own semver-protected surface — the CLI commands, config keys, and behaviour it guarantees — is documented in [`PUBLIC_API.md`](PUBLIC_API.md). It exposes no `@api` PHP classes: it's an artisan/CLI-driven wrapper, so its public contract is the commands and config, not a class API. Troubleshooting --------------- [](#troubleshooting) **`No boost config found (expected boost.php or .config/boost.php)`** — create one (see `boost.php` above; `.config/boost.php` is the canonical location on boost-core ≥ 0.17) or run `vendor/bin/boost install`. **`Errors during sync: ... listed more than once`** — `boost.php` declared a `withRemoteSkills` source whose skill name overlaps another source, or the laravel/boost asset reader produced two versioned variants of the same skill that didn't dedupe. The second case is a bug; please report. **`Errors during sync: ... also published by a scanned vendor`** — a package you allowlisted via `withAllowedVendors` publishes a skill colliding with one this package injects from laravel/boost. Either rename the vendor's skill or exclude it: `->withExcludedSkills(['vendor/pkg:skill-name'])`. **Blade-templated skill output contains literal `@php` or `{{ ... }}`** — `BladeRenderer` didn't fire. Confirm `laravel/boost` is installed (`composer show laravel/boost`), and run the sync through **`php artisan project-boost:sync`**: that path auto-registers the renderer against a bootstrapped framework, so your `.ai/skills//SKILL.blade.php` and `.ai/guidelines/*.blade.php` render. Bare `vendor/bin/boost sync` can't render Blade — it never boots Laravel, so the renderer has no application context and fails fast with an actionable error. Use the artisan command for Blade-templated content. **`unchanged` for every file on a second sync** — that's expected. boost-core's `FileWriter` is content-aware. Testing ------- [](#testing) ``` composer test ``` Pest suite. Unit tests for discovery, version resolution, and the suppress-upstream listener, plus Testbench-backed feature tests for `project-boost:install`'s TTY-vs-non-TTY branching. `.github/workflows/ci-smoke.yml` runs the end-to-end consumer install path on every push and PR. It spins up a fresh `laravel/laravel` app, installs this package from the checkout, runs `project-boost:install --no-sync --no-interaction` (asserts `.mcp.json` lands with the `laravel-boost` server entry), then `project-boost:sync` (asserts no Blade directives leak into rendered output). License ------- [](#license) MIT. See [LICENSE](LICENSE). Credits ------- [](#credits) - [Sander Muller](https://github.com/sandermuller) - [`laravel/boost`](https://github.com/laravel/boost) for the MCP server, the bundled Laravel skills, and the per-agent `McpWriter` this package reuses. - [`sandermuller/boost-core`](https://github.com/sandermuller/boost-core) for the sync engine this package extends. ### Health Score 47 — FairBetter than 93% of packages Maintenance90 Actively maintained with recent releases Popularity20 Limited adoption so far Community2 Small or concentrated contributor base Maturity59 Maturing project, gaining track record How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window. **Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores. **Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement. **Maturity (30%)** — Project age, version count, PHP version support, and release stability. ### Release Activity Cadence Every ~0 days Total 27 Last Release 49d ago Major Versions 0.10.2 → 1.0.02026-06-05 ### Community Maintainers ![](https://www.gravatar.com/avatar/abeb7bd51fd77656b4133bdcdf4eca99cc8b495b83ca72f63674ff15f2b72a39?d=identicon)[SanderMuller](/maintainers/SanderMuller) --- Tags laravelsandermullerproject-boost-laravel ### Code Quality TestsPest Static AnalysisPHPStan, Rector Code StyleLaravel Pint Type Coverage Yes ### Embed Badge ![Health badge](/badges/sandermuller-project-boost-laravel/health.svg) ``` [![Health](https://phpackages.com/badges/sandermuller-project-boost-laravel/health.svg)](https://phpackages.com/packages/sandermuller-project-boost-laravel) ``` ### Alternatives [psalm/plugin-laravel Psalm plugin for Laravel 3345.3M347](/packages/psalm-plugin-laravel)[laravel/ai The official AI SDK for Laravel. 1.0k3.2M246](/packages/laravel-ai)[moonshine/moonshine Laravel administration panel 1.3k253.1k86](/packages/moonshine-moonshine)[api-platform/laravel API Platform support for Laravel 58174.6k17](/packages/api-platform-laravel)[tomshaw/electricgrid A feature-rich Livewire package designed for projects that require dynamic, interactive data tables. 119.4k](/packages/tomshaw-electricgrid) PHPackages © 2026 [Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)