- How does `package-boost-laravel` differ from `package-boost-php` for Laravel package authors?
- `package-boost-laravel` extends `package-boost-php` with Laravel-specific AI agent skills and emits `.mcp.json`, a standardized metadata file tailored for Laravel packages. It’s designed to help package authors document dependencies, hooks, and conventions automatically, while `package-boost-php` is more generic. Both are dev-only dependencies with no runtime overhead.
- Will this package work in Laravel 10.x projects, or is it only for newer versions?
- Yes, it works with Laravel 8+ because it’s a dev-only dependency (no `illuminate/*` in `require`). It won’t force Laravel constraints on your project, so you can use it even if your app targets older versions like 10.x. The package itself is framework-agnostic at runtime.
- Do I need to configure anything to use this package, or is it zero-config?
- It’s zero-config by default. Just install it via Composer (`composer require --dev sandermuller/package-boost-laravel`), and it will automatically discover and process your package’s metadata during `boost sync`. No service provider registration or config publishing is required unless you’re migrating from an older version.
- What’s the `.mcp.json` file used for, and how can I validate its contents?
- `.mcp.json` is a machine-readable metadata artifact that describes your Laravel package’s structure, dependencies, and conventions. You can validate it against schemas in CI/CD pipelines (e.g., using JSON Schema validators) or integrate it with package registries. The format is designed to be extensible but currently lacks external tooling—check the [Boost ecosystem](https://github.com/SanderMuller/package-boost-php) for updates.
- Are the AI agent skills customizable, or are they locked to predefined prompts?
- The AI agent skills are built on top of `package-boost-php`’s core, which may offer some customization via configuration files or environment variables. However, the package doesn’t explicitly document prompt customization yet. For Laravel-specific needs, you’d need to check `package-boost-php`’s roadmap or contribute to its open-source project.
- How can I test this package locally without affecting my production environment?
- Since it’s a dev-only dependency, you can safely install it in your project without runtime impact. Use Laravel’s Testbench (included via `require-dev`) to test package behavior locally. If you’re not using Testbench, ensure your testing environment includes the `illuminate/*` dependencies required for dev-time operations.
- What are the performance implications of running `boost sync` in a large Laravel package?
- Performance depends on `package-boost-php`’s underlying implementation, which isn’t heavily documented. The package emits `.mcp.json` during sync, so frequent runs in CI might slow builds. You can disable `.mcp.json` generation in CI by excluding the relevant config, though this may reduce metadata benefits. Monitor CPU/memory usage if sync feels slow.
- Is this package maintained actively, or should I consider alternatives like `spatie/laravel-package-tools`?
- `package-boost-laravel` is a newer addition to the Boost family, with `package-boost-php` as its core dependency. While it follows SemVer, its long-term maintenance depends on the Boost project’s adoption. For traditional Laravel package tools (e.g., scaffolding, publishing), `spatie/laravel-package-tools` is more mature. Use this package if you’re focused on AI-assisted metadata and `.mcp.json` integration.
- Can I use this package in a CI/CD pipeline to auto-generate documentation?
- Yes, `.mcp.json` is designed for CI/CD integration. You could parse it to auto-generate `README.md` sections, validate package metadata, or enforce conventions. For example, you might write a script to extract Laravel-specific details (e.g., service providers, events) from `.mcp.json` and format them into Markdown. Combine it with tools like `phpDocumentor` for full coverage.
- What happens if I upgrade to a new minor version of `package-boost-php`, and will it break `.mcp.json` compatibility?
- Since `package-boost-laravel` pins `package-boost-php` to `^1.0`, minor upgrades should maintain `.mcp.json` compatibility *if* `package-boost-php` follows SemVer. However, `package-boost-php`’s maturity is unproven, so undocumented breaking changes in minor releases are a risk. Always test upgrades in a staging environment and back up your `.mcp.json` schema if critical.