Download the PHP package sandermuller/package-boost-laravel without Composer
On this page you can find all versions of the php package sandermuller/package-boost-laravel. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download sandermuller/package-boost-laravel
More information about sandermuller/package-boost-laravel
Files in sandermuller/package-boost-laravel
Package package-boost-laravel
Short Description AI agent skills for Laravel package authors. Adds Laravel-flavored skills + .mcp.json emission on top of package-boost-php.
License MIT
Homepage https://github.com/sandermuller/package-boost-laravel
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package package-boost-laravel
package-boost-laravel
AI agent skills, guidelines, and .mcp.json emission for Laravel-package authors. Inherits the framework-agnostic package-author toolkit from sandermuller/package-boost-php and layers on Laravel-specific context: Testbench conventions, cross-version Laravel support, CI matrix diagnostics, and the McpJsonEmitter that wires laravel/boost's MCP server into Claude Code during boost sync.
Where
laravel/boosttargets Laravel application developers,package-boost-laraveltargets the people building Laravel packages — the dev-time codebase whereapp/,bootstrap/, and.envdon't exist andphp artisandoesn't apply. Coexists cleanly withlaravel/boostif you also dogfood it from inside your package's test app.
Which package fits your role?
| You're building | Install | Ships |
|---|---|---|
| A PHP application (not a package) | sandermuller/project-boost |
App-dev skills: DDD layering, repository pattern, DI, domain modeling, legacy coexistence |
| A Laravel application | sandermuller/project-boost-laravel |
laravel/boost MCP coexistence + nine-agent fanout + tag filter + remote skills |
| A framework-agnostic Composer package | sandermuller/package-boost-php |
Package-author skills + lean / gitattributes commands |
| A Laravel package | sandermuller/package-boost-laravel |
Laravel-package skills + McpJsonEmitter ← you are here |
| Your own skill bundle, or custom tooling | sandermuller/boost-core |
The sync engine. You supply the skills. |
What you get
McpJsonEmitter — the zero-overlap claim against laravel/boost. Writes .mcp.json on every boost sync, idempotent, with the command pointed at vendor/bin/testbench boost:mcp (not php artisan) so the MCP server actually boots in a package codebase. laravel/boost writes .mcp.json once at install time against php artisan, which doesn't exist here. The emitter fires only when all three conditions hold: laravel/boost is in your dev dependencies, orchestra/testbench is in your dev dependencies, and Agent::CLAUDE_CODE is in your active agents. Otherwise it returns null and skips silently.
Three Laravel-flavored skills — on-demand workflows for Laravel-package authorship. All three are untagged, so they ship whenever this package is installed.
| Skill | When it loads | Tag |
|---|---|---|
package-development |
Testbench conventions: vendor/bin/testbench vs php artisan, service-provider registration in testbench.yaml, workbench/ layout for fixtures, migrations, routes, factories. |
— |
cross-version-laravel-support |
Supporting multiple Laravel majors in one release: ^12.0\|\|^13.0 constraint patterns, version-specific API shims, CI matrix shape including prefer-lowest. |
— |
ci-matrix-troubleshooting |
Debugging "fails on prefer-lowest" / "fails on Laravel 13 but not 12" type matrix failures. | — |
One Laravel guideline — pinned context for AI agents working in a Laravel-package codebase.
| Guideline | Scope | Tag |
|---|---|---|
laravel-packages |
Detection rule (require.illuminate/* or require.laravel/framework), Testbench context, artisan-substitution table, cross-version compatibility pointer. Composes with the framework-agnostic foundation guideline inherited from package-boost-php. |
— |
Inherits everything package-boost-php ships — foundation guideline, lean / gitattributes CLI commands, the lean-dist skill, and the release-flow content skills (readme, release-notes, upgrading) from sandermuller/boost-skills under the release-automation tag. The skill-authoring + writing-file-emitter skills ship too but are gated behind the boost-extension tag — declare it if your package extends the engine with a custom FileEmitter (this package does, for McpJsonEmitter).
Install
PHP 8.3+ and Laravel 12 or 13. sandermuller/package-boost-php, sandermuller/boost-core, and stolt/lean-package-validator all come in transitively — do not require any of them separately, they resolve through this umbrella. A Laravel-package author requires only sandermuller/package-boost-laravel and gets the whole stack. (Internally this package now pins sandermuller/boost-core directly at ^0.22 so its McpJsonEmitter is guaranteed the iterable FileEmitter contract — an implementation floor, not something you declare.)
First run
If laravel/boost + orchestra/testbench are in your dev deps and Claude Code is one of your active agents, boost sync writes .mcp.json automatically. Generated agent dirs (.claude/, .cursor/, etc.) are added to .gitignore; edit .ai/ only, then re-run vendor/bin/boost sync.
boost.php config
The release-automation tag pulls the release-flow skills from sandermuller/boost-skills; add 'boost-extension' to pull skill-authoring + writing-file-emitter if you author a custom FileEmitter. Full BoostConfig reference lives in sandermuller/boost-core's README.
Coexistence and inheritance
Three relationships, distinct shapes:
- Inherits from
sandermuller/package-boost-php. Required as a Composer dependency. Everything that package ships — thefoundationguideline, thelean/gitattributesCLI, the framework-agnostic package-author skills — is available without re-declaring. This package layers Laravel-specific skills, thelaravel-packagesguideline, andMcpJsonEmitteron top. - Coexists with
laravel/boostinside the package's test app. Disjoint concerns: this package is dev-time package authorship (skills, guidelines, MCP wiring);laravel/boostis the MCP server + Laravel docs API your AI agent talks to once running. TheMcpJsonEmitteris the seam — it points the MCP client atvendor/bin/testbench boost:mcpsolaravel/boost's server can boot under Testbench. Without this emitter,laravel/boost's install-time.mcp.jsonwrite targetsphp artisan, which doesn't exist in a package codebase. - Serves Laravel-package projects. The consumer is a package author writing a Composer package that depends on Laravel. The guideline activates only when
composer.jsondeclaresrequire.illuminate/*orrequire.laravel/framework; the skills are tagged for Laravel-package workflows.
Auto-sync
To re-sync on every composer install / composer update, wire the callback into your project's composer.json:
BOOST_SKIP_AUTOSYNC=1 disables the callback. (Boost-core 0.6.0 retired its Composer plugin; consumer auto-sync is opt-in via this script hook.)
Testing
License
MIT. See LICENSE.
All versions of package-boost-laravel with dependencies
illuminate/contracts Version ^12.0||^13.0
illuminate/support Version ^12.0||^13.0
sandermuller/package-boost-php Version ^0.16.1