Project Boost Laravel Laravel Package

Product Decisions This Supports

• Standardizing AI context across the Laravel portfolio. The package generates and maintains the AI guideline files (agent instructions/rules) that ship with each project by syncing them against laravel/boost's upstream guidance. That turns "every repo has hand-edited, drifting AI instructions" into a repeatable, reviewable artifact — a governance decision, not just a dev convenience.
• Build vs. buy for guideline plumbing. Writing an in-house project-boost:sync script is ~a day of work plus permanent maintenance against upstream changes. This release is direct evidence of that maintenance cost: 1.6.0 exists because the sync silently dropped laravel/boost's Tools, search-docs, and record-rule guidance, plus the "Skills Activation" section. Adopting the package outsources that drift-tracking.
• Context budget / token-cost control. The new mcp config key (PROJECT_BOOST_MCP, default true) lets a project opt out of laravel/boost's MCP tool guidance when MCP is already documented centrally. This is a real product lever: duplicated tool instructions inflate every agent prompt. We can now decide per-project whether MCP guidance is owned by the package or by our own platform docs, instead of patching generated files after the fact.
• Upgrade-parity gating for laravel/boost adoption. If we bump laravel/boost in the roadmap, 1.5.x would have quietly produced incomplete guidelines. 1.6.0 makes guideline completeness a supported property, so laravel/boost upgrades no longer need a manual "did anything go missing?" audit.
• Onboarding and reproducibility. Because the output is generated and committed, new contributors — human or agent — get the same guidance on day one, and guideline changes show up as diffs in PR review rather than as untracked local edits.

When to Consider This Package

Consider adoption when:

• The team has standardized (or is standardizing) on laravel/boost as its AI tooling layer, and there are more than a couple of Laravel repos to keep consistent.
• Generated guideline files are (or will be) committed to VCS, so guideline drift is visible in code review.
• You want per-project control of MCP guidance rather than one global convention — 1.6.0's PROJECT_BOOST_MCP toggle is the deciding feature here.
• You are willing to re-run sync and diff the output after every laravel/boost upgrade. The 1.6.0 fixes show the sync is tightly coupled to upstream file/section layout; silent omission is the failure mode, not a loud error.

Look elsewhere (or defer) when:

• The stack is not laravel/boost — the package is a thin, opinionated adapter and carries no value without that upstream.
• You have one project whose AI instructions are hand-maintained and short; the sync adds a moving part for negligible benefit.
• You need framework-agnostic or multi-vendor guideline generation (PHP + JS + Go in one monorepo standard) — this is Laravel-shaped by design.
• You need guaranteed stability of generated output across versions. The 1.6.0 changelog is a compatibility fix, meaning output content can change between minor releases; treat generated guidelines as a reviewed artifact, not a pinned contract.
• Your org cannot tolerate guidance content changing without a major version bump — the config default (true) preserves prior behavior, but the fix items change generated output for existing installs on a minor bump.

How to Pitch It (Stakeholders)

For executives: This is a small, low-risk dependency that keeps the AI assistant instructions in our Laravel repositories correct and consistent without anyone hand-editing them. Version 1.6.0 fixes a real correctness gap — the tool was silently leaving out key guidance sections and now doesn't — and adds a per-project switch so we don't pay twice for MCP tool instructions that are already documented centrally. Cost is a package dependency plus a sync step in CI; upside is consistent AI-assisted development across every repo and one less bespoke script for us to own.

For engineering: Adopt it as the single source for generated AI guideline files. Enable the new PROJECT_BOOST_MCP toggle to false in repos where MCP guidance is owned by platform docs. Two operating rules: (1) run project-boost:sync and review the diff in the same PR as any laravel/boost upgrade — 1.6.0 demonstrates that upstream layout changes can cause silent omissions; (2) treat regenerated guidelines as a reviewed artifact, not generated noise, since output content can change on minor releases. 1.6.0 is a backward-compatible minor: the new config key defaults to true (existing behavior preserved), so adoption is a low-friction upgrade from 1.5.x, and it's a required upgrade if we're already on 1.5.x with incomplete guideline output.