Download the PHP package sandermuller/project-boost-php without Composer

On this page you can find all versions of the php package sandermuller/project-boost-php. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.

FAQ

After the download, you have to make one include require_once('vendor/autoload.php');. After that you have to import the classes with use statements.

Example:
If you use only one package a project is not needed. But if you use more then one package, without a project it is not possible to import the classes with use statements.

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 PHP packages are not free to download and because of that hosted in private repositories. In this case some credentials are needed to access such packages. Please use the auth.json textarea to insert credentials, if a package is coming from a private repository. You can look here for more information.

  • 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.
Please rate this library. Is it a good library?

Example code of sandermuller/project-boost-php

Informations about the package project-boost-php

project-boost-php

Latest Version on Packagist GitHub Tests Action Status Total Downloads Laravel Boost

AI agent skills for PHP application developers — any framework, or none. Two framework-agnostic skills (dependency injection, legacy coexistence) plus a foundation guideline that frames the codebase as an application, not a package. Rides the sandermuller/boost-core sync engine; ships no code of its own.

For PHP application developers on any framework or none. laravel/boost is Laravel-only; project-boost-php covers Symfony, plain-PHP, and framework-agnostic apps. Building a Laravel app? Install sandermuller/project-boost-laravel instead — it layers laravel/boost MCP coexistence on the same nine-agent fanout.

Which package fits your role?

You're building Install Ships
A PHP application (not a package) sandermuller/project-boost-php App-dev skills: dependency injection, legacy coexistence + the foundation guideline ← you are here
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
Your own skill bundle, or custom tooling sandermuller/boost-core The sync engine. You supply the skills.

What you get

Two skills — universally-applicable PHP practices, not tied to any architecture.

Skill Triggers when
dependency-injection Constructor injection, container hygiene, avoiding service locators.
legacy-coexistence Adding modern PHP (typed properties, readonly, enums) to a 7.x codebase incrementally.

One guideline — foundation. Framework-agnostic application-developer framing: what an app codebase is, how its edges form its real contract, and how to work in it. Always shipped, no tag required.

Want architecture-specific guidance (DDD layering, repositories, domain modeling)? Those shipped through 0.x but were dropped at 1.0 to keep the default framework-agnostic — copy any you want into your own .ai/skills/<name>/SKILL.md (host copies shadow vendor skills), or exclude a shipped skill via ->withExcludedSkills(['sandermuller/project-boost-php:<name>']).

How it compares to laravel/boost

laravel/boost project-boost-php
Framework scope Laravel only any PHP — Symfony, plain-PHP, framework-agnostic
Skill set Laravel runtime guidelines (Eloquent, Blade, …) framework-agnostic app practices (DI, legacy coexistence) + foundation
Agent reach Laravel apps only (broad agent set) non-Laravel apps too — same agent set via boost-core
Tag filter / remote skills / allowlist — via boost-core (withTags(), withRemoteSkills(), withAllowedVendors())
MCP server + Laravel docs API ✅ Not in scope; use laravel/boost directly in Laravel apps

Both can sit in the same Laravel app via project-boost-laravel — the family member designed for that combo.

Install

PHP 8.3+. Pulls in sandermuller/boost-core transitively.

First run

The five skills land in your selected agent skill directories (.claude/skills/, .cursor/skills/, …); foundation merges into each agent's guidelines file (CLAUDE.md, AGENTS.md, …). Generated dirs are added to .gitignore automatically. Edit .ai/ only — the fan-out regenerates on every sync.

boost.php

Minimal:

withAllowedVendors() is explicit — a dependency's skills sync only if its package name is listed. Full BoostConfig surface is documented in boost-core's README.

Where do the skills come from?

project-boost-php's two are one source. Skill sources stack:

  1. Hand-authored in your project's .ai/skills/ folder. boost-core picks them up automatically; host overrides shadow vendor-shipped versions of the same name.
  2. Composer-installed catalogs that ship resources/boost/skills/. This package is one example. sandermuller/boost-skills is another — Sander's personal mix, shared as an illustration of the pattern. Anyone can publish their own.
  3. External non-Composer sources via withRemoteSkills(). GitHub-published .skill bundles or single-skill repos. No Composer required.

(laravel/boost's bundled Laravel skills are a fourth source in Laravel apps — surface them via project-boost-laravel.)

withAllowedVendors() gates Composer-scanned vendors (source 2) only. withTags() filters sources 2 and 3. Host skills (source 1) bypass both — your project authored them, so the engine treats them as canonical and applies neither filter.

Coexistence

Auto-sync on composer install

Wire the callback into your own project's composer.json so a composer install / composer update re-syncs:

BOOST_SKIP_AUTOSYNC=1 disables the callback. Full detail in boost-core's automating-the-sync section.

Testing

Pest suite — sanity tests on the shipped skill + guideline set: skills parse with a name matching the filename and a non-empty description; guidelines are frontmatter-free and open with a Markdown heading.

License

MIT. See LICENSE.

All versions of project-boost-php with dependencies

PHP Build Version
Package Version
Requires php Version ^8.3
sandermuller/boost-core Version ^1.0
Composer command for our command line client (download client) This client runs in each environment. You don't need a specific PHP version etc. The first 20 API calls are free. Standard composer command

The package sandermuller/project-boost-php contains the following files

Loading the files please wait ...