Download the PHP package sandermuller/project-boost-laravel without Composer
On this page you can find all versions of the php package sandermuller/project-boost-laravel. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download sandermuller/project-boost-laravel
More information about sandermuller/project-boost-laravel
Files in sandermuller/project-boost-laravel
Package project-boost-laravel
Short Description 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).
License MIT
Homepage https://github.com/sandermuller/project-boost-laravel
Informations about the package project-boost-laravel
project-boost-laravel
The Laravel-application member of the boost family. It sits next to
laravel/boostin the same project.laravel/boostkeeps doing what it already does — the MCP server, the Laravel docs API, its bundled Laravel skills — and this package takes over the agent-file fan-out, adding per-project filtering, remote skill sources, and origin tracing on top.
Documentation: https://sandermuller.github.io/boost-core/packages/project-boost-laravel/
You run laravel/boost and this package together. Neither replaces the other;
the design assumes they are installed side by side.
What this adds on top of laravel/boost
Both tools write the same ten agents. What differs is the control you get over what reaches them.
laravel/boost alone |
With this package | |
|---|---|---|
| MCP server, docs API, bundled Laravel skills | Yes | Unchanged |
| Tag filtering | — | withTags(). Ship inertia-vue-development only on Inertia projects |
| Remote skill sources | — | withRemoteSkills(). Pull GitHub-published .skill bundles |
| Vendor allowlist | Automatic, from composer.json |
Explicit withAllowedVendors(), for collision control |
| Origin tracing | — | boost where, plus project-boost:where for the injected set |
| User-scope sync | — | boost sync --scope=user, for globally-installed CLI tools |
| Health check | — | boost doctor --check-versions |
Install
laravel/boost and sandermuller/boost-core come in transitively. Do not
require boost-core separately.
project-boost:install wraps boost:install --mcp, so laravel/boost writes
its MCP client config exactly as it always does, then runs
project-boost:sync for the fan-out. It detects a non-TTY shell, so CI and
Docker need no extra flags.
[!WARNING] Running
php artisan boost:installwithout--mcpfireslaravel/boost's own guideline and skill writers, which then race this package overCLAUDE.mdand the per-agent skill directories. Always go throughproject-boost:install.
Already have hand-edited agent 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.
Configuration
boost.php in the project root, or .config/boost.php:
Every BoostConfig method, the tag vocabulary, and the auto-sync hook are in the
configuration guide.
Commands
| Command | Does |
|---|---|
project-boost:install |
Wraps boost:install --mcp and runs the sync. The recommended entry point |
project-boost:sync |
Discover, render, tag-filter, fan out. Run after composer install or a boost.php edit |
project-boost:sync --dry-run |
Preview the full pipeline in check mode |
project-boost:where |
The laravel/boost skills and guidelines this package injects, with ship / filtered / shadow status |
project-boost:reconcile |
Capture laravel/boost-seeded guidance into .ai/guidelines/ before a sync would overwrite it |
Documentation
| Topic | Page |
|---|---|
| What it adds, who owns which file, the architecture | Overview |
| Install, first run, troubleshooting | Install |
boost.php, auto-sync, suppress_upstream_writers |
Configuration |
| The canonical command sequence and the data-loss seam | Coexistence with laravel/boost |
| Tags, skill dependencies, remote skills, conventions | Guide |
| Every command and exit code | CLI reference |
The semver-protected surface — the commands, the config keys, and the behaviour
this package guarantees — is in PUBLIC_API.md. It exposes no
@api PHP classes: the public contract is the commands and the config.
Testing
Pest suite: unit tests for discovery, version resolution, and the
suppress-upstream listener, plus Testbench-backed feature tests for
project-boost:install's TTY-versus-non-TTY branching.
.github/workflows/ci-smoke.yml runs the consumer install path end to end on
every push and pull request. It creates a fresh laravel/laravel application,
installs this package from the checkout, runs
project-boost:install --no-sync --no-interaction and asserts .mcp.json lands
with the laravel-boost server entry, then runs project-boost:sync and asserts
no Blade directives leak into the rendered output.
License
MIT. See LICENSE.
Credits
- Sander Muller
laravel/boostfor the MCP server, the bundled Laravel skills, and the per-agentMcpWriterthis package reuses.sandermuller/boost-corefor the sync engine this package extends.
All versions of project-boost-laravel with dependencies
illuminate/contracts Version ^12.0||^13.0
illuminate/support Version ^12.0||^13.0
laravel/boost Version ^2.5
laravel/roster Version ^1.0
sandermuller/boost-core Version ^1.8.1