Product Decisions This Supports
- Developer onboarding and time-to-first-PR. Bundling Laravel Boost into core means every project and module built on this package ships with AI-assistant guidelines and "skills" wired up out of the box. For a PM, that is a measurable lever on ramp-up time for new engineers and on consistency of AI-generated code across teams — worth tracking as an onboarding KPI rather than an engineering nicety.
- Build vs. buy on internal tooling. Rather than maintaining bespoke prompt libraries, Cursor rules, or CLAUDE.md/AGENTS.md conventions per module, the package now delegates that to an established Laravel-ecosystem tool. This is a clear "buy/adopt" signal: do not budget engineering time for a homegrown AI-context layer.
- Roadmap positioning: DX as a product feature. This release strengthens the case for marketing the stack as "AI-ready by default." If you are selling to engineering teams or publishing an open-source starter, "your AI assistant already knows our module conventions" is a differentiator worth a landing-page bullet and a docs page.
- Architecture consistency across modules. Module-scoped guidelines imply a convention that AI tooling can read. That makes module boundaries and public APIs effectively a contract — a useful forcing function for keeping interfaces documented, but also a maintenance obligation.
- Adoption/migration planning. Because this ships in core, it is a passive upgrade for existing consumers. No opt-in decision, no integration project. Plan for a version bump in the next maintenance window rather than a dedicated workstream.
- Support and documentation scope. Expect a new class of support questions ("why is my assistant suggesting the wrong pattern?"). Budget a troubleshooting page and assign an owner for the guideline content.
When to Consider This Package
Adopt or upgrade when:
- You are building a modular Laravel application and want each module to carry its own AI-readable guidelines and skills without per-module setup.
- Your team already uses Laravel Boost or an MCP-capable assistant (Cursor, Claude Code, Copilot, Windsurf) and you want conventions surfaced automatically.
- You want zero-config developer experience for new contributors — the strongest argument for taking this release.
- Your modules have stable, well-documented public APIs. The guidelines are only as good as the conventions they encode.
Look elsewhere or defer when:
- Production dependency hygiene matters more than DX. Verify whether Boost and its guideline/skill assets are dev-only or ship into your production artifact. If they land in
vendor/ for production builds, split them out or exclude via composer install --no-dev verification before rollout.
- You are on Laravel/PHP versions outside the supported matrix — check Boost's own constraints, which move faster than a core package's.
- Your team has no AI-assisted workflow or has standardized on a non-Laravel-aware assistant. The guidelines become dead weight and a docs-drift liability.
- You operate in a regulated or air-gapped environment where AI tooling integrations require review; treat adoption as a security/procurement decision, not a routine bump.
- Your module conventions are unstable or undocumented. Encoding them into skills now locks in churn.
Assessment caveat: this release note is a single line. Before committing to a roadmap story around it, confirm the practical details — dependency type (require vs. require-dev), Laravel/PHP version floor, whether guideline files are generated or static, and how they stay in sync as modules evolve.
How to Pitch It (Stakeholders)
For executives (one paragraph). v1.14.0 makes our Laravel core ship with built-in AI coding-assistant context, so every module and every project built on it is "AI-ready" by default instead of requiring bespoke prompt engineering. The product value is faster onboarding, more consistent code from AI tools, and a credible "AI-native developer experience" claim in our positioning — at essentially zero integration cost, since it arrives with a routine version bump. The ask is not budget; it is a decision to treat developer experience as a first-class part of the product story and to name an owner for keeping the module guidelines accurate.
For engineering leads. Low-risk, high-leverage upgrade. No migration work: bump the version, verify Boost resolves as a dev-only dependency, and confirm your Laravel/PHP versions are inside its support matrix. In exchange, contributors get module-aware guidelines and skills without per-repo configuration. Two obligations follow — keep the module conventions in the guidelines current as APIs change, and sanity-check that AI-suggested code matches your actual patterns before it spreads.
What we are not claiming. This is a developer-tooling release, not a customer-facing feature. Success looks like shorter ramp-up for new engineers and fewer convention-drift corrections in review — measure those, and revisit the investment if the guidelines are not being consumed or are going stale.