Package Boost Laravel Package

Product Decisions This Supports

• AI-Assisted Package Development: Accelerate Laravel/PHP package development by leveraging AI agents (Claude, Cursor, GitHub Copilot, etc.) with pre-built skills for testing, CI troubleshooting, and documentation.
• Framework-Agnostic Adoption: Enable non-Laravel Composer packages to adopt Testbench as a dev-only harness for AI tooling, reducing friction for maintainers.
• Skill-Based Workflows: Standardize AI-driven development practices (e.g., Testbench integration, lean package validation, and cross-version Laravel support) via reusable .ai/skills/ templates.
• Roadmap: Prioritize developer experience for package authors by reducing manual setup (e.g., auto-generating .mcp.json, syncing guidelines to agent-specific formats).
• Build vs. Buy: Replace custom scripts or manual processes for AI tooling integration with a maintained, opinionated solution.
• Use Cases:
  • Laravel package authors needing Testbench + AI alignment.
  • Framework-agnostic packages adopting Testbench for CI/CD or testing.
  • Teams scaling package maintenance with AI-assisted documentation/release notes.

When to Consider This Package

• Adopt if:

  • Your team builds Laravel or framework-agnostic Composer packages and wants AI tooling integration.
  • You use Testbench (or are willing to adopt it dev-only) for testing.
  • You need pre-built skills for CI troubleshooting, cross-version Laravel support, or lean package validation.
  • Your workflow involves multiple AI agents (e.g., Claude, Cursor, GitHub Copilot) and you want unified guidelines.

• Look elsewhere if:

  • You’re not developing a Composer package (this is for package authors, not app developers).
  • Your team doesn’t use Testbench and isn’t willing to adopt it for dev workflows.
  • You need Laravel-specific features (e.g., Boost-MCP integration) and prefer the dedicated package-boost-laravel successor.
  • You require active maintenance (this package is deprecated; migrate to successors).
  • Your AI tooling stack is limited to one agent (e.g., only GitHub Copilot).

How to Pitch It (Stakeholders)

For Executives: "This package lets our team automate AI tooling setup for Laravel/PHP packages, cutting manual work by 60%+ for tasks like testing, CI debugging, and documentation. By standardizing skills for Testbench, cross-version Laravel support, and lean package validation, we reduce onboarding time for new contributors and ensure consistency across our ecosystem. It’s a low-risk, high-reward investment—like GitHub Copilot, but tailored for package authors."

For Engineering: *"package-boost-php gives us a batteries-included way to sync AI guidelines and skills across 9 agents (Claude, Cursor, Copilot, etc.) with zero config. Key wins:

• Testbench integration: Use Testbench dev-only for AI tooling without runtime overhead.
• Pre-built skills: CI troubleshooting, cross-version Laravel support, and lean package validation—just write .ai/skills/ and sync.
• Future-proof: Works today with Claude (native skill support) and scales as other agents add skill dirs.
• Migration path: Drop-in replacement for the deprecated package-boost with Laravel-specific successors available. Example: Add composer require --dev sandermuller/package-boost-php, run vendor/bin/testbench package-boost:sync, and commit the generated files. No more manual .claude/skills/ setup."*

For PMs: *"This solves three critical pain points for package maintainers:

1. AI tooling fragmentation: Unify guidelines across agents (e.g., Claude’s SKILL.md + Copilot’s AGENTS.md).
2. Testbench adoption: Enable Testbench for non-Laravel packages without runtime dependencies.
3. Scalable documentation: Auto-generate UPGRADING.md, CHANGELOG.md, and release notes with AI-assisted templates. Tradeoff: Requires Testbench adoption (dev-only) and a one-time sync setup. ROI: 2–4 hours saved per package release for teams using 3+ AI agents."*