Skeleton Laravel Package

Product Decisions This Supports

• Accelerating Laravel Package Development: Reduces boilerplate for building reusable Laravel packages, enabling faster iteration on internal tools, plugins, or third-party offerings.
• Standardizing Package Architecture: Ensures consistency across teams by enforcing a proven structure (e.g., for Filament, CMS, or eCommerce modules).
• Build vs. Buy Decision: Justifies building custom Laravel packages over third-party solutions when domain-specific needs exist (e.g., proprietary integrations, niche workflows).
• Roadmap for Package Ecosystem: Foundation for scaling a suite of Laravel packages (e.g., for a SaaS platform or enterprise app) by reusing the same template.
• Developer Experience (DX) Investments: Aligns with initiatives to improve onboarding for junior devs or reduce technical debt in package maintenance.

When to Consider This Package

• Adopt When:
  • Building reusable Laravel packages (e.g., for Filament admin panels, CMS features, or eCommerce components).
  • Your team lacks a standardized template for package development, leading to inconsistent codebases.
  • You need to rapidly prototype or iterate on packages without reinventing scaffolding (e.g., config, commands, providers).
  • Part of a larger Moox ecosystem adoption (e.g., using Filament + Moox packages).
• Look Elsewhere If:
  • You’re developing full applications, not packages (use Laravel’s built-in make:package or Laravel Breeze/Sail).
  • Your packages require heavy customization beyond the template’s scope (e.g., unique service containers).
  • You prioritize minimal dependencies (this template pulls in Moox’s ecosystem by default).
  • Your team lacks PHP/Laravel expertise to leverage the template effectively.

How to Pitch It (Stakeholders)

For Executives: "Moox Skeleton is a pre-built ‘starter kit’ for creating Laravel packages—think of it as a template for building Lego blocks that snap into our larger app ecosystem. By standardizing how we develop packages (e.g., for Filament admin tools or CMS features), we’ll cut development time by 30–50% and reduce bugs from inconsistent code. This aligns with our goal to [X roadmap item], while keeping us flexible to customize packages for our unique needs. The MIT license and Moox’s active development make it a low-risk choice."

For Engineering: "This template solves the ‘how do we structure a new Laravel package?’ problem once and for all. It handles the boring setup (autoloading, service providers, commands) so we can focus on business logic. The moox:install command and build.php script automate scaffolding, and since it’s used by Moox’s own packages, we know it’s battle-tested. If we adopt Moox’s Filament ecosystem later, this template will play nicely with it. Downside: slight lock-in to Moox’s conventions, but the tradeoff is worth it for consistency."