Laravel Starter Kit Inertia React Laravel Package

Product Decisions This Supports

• Greenfield bootstrap and stack standardization. This is a scaffold, not a runtime dependency — you fork or clone it once and own the result. The PM decision it informs is "what do all new Laravel + React services look like," not "which library do we require." With 0 dependents and a low opportunity score (1.69), treat it as an accelerator for a repeatable stack, not an ecosystem bet.
• Build vs. buy on internal scaffolding. The alternative is writing your own conventions doc, CI config, auth wiring, and TypeScript route bindings — typically 1–3 engineer-weeks per greenfield project, repeated each time. Adopting (and forking) this collapses that into days, at the cost of inheriting someone else's opinions.
• Definition of Done and quality gates. The kit ships the gates already wired: declare(strict_types=1), Larastan v3, Pint, Rector v2, Pest v5, plus an explicit "every change must be programmatically tested" rule. This is a concrete input to a team charter decision: do we enforce static analysis and coverage as merge blockers, or as advisory?
• Architecture standard: the Action pattern. Business logic lives in app/Actions as single-handle() classes callable from HTTP, jobs, commands, and MCP requests. That's a scoping and estimation decision — it changes how you decompose epics, and it makes reuse across entry points a first-class requirement rather than an afterthought.
• Agent-assisted development as a product capability. AGENTS.md with domain skills (Laravel best practices, Wayfinder, Fortify) plus Laravel Boost MCP tooling means AI coding assistants produce code in your conventions. This is the most defensible PM angle here: it directly affects onboarding time, PR review load, and how safely you can parallelize work across engineers.
• Roadmap de-scoping. Fortify v1 covers login, registration, password reset, email verification, 2FA/TOTP, and profile updates out of the box. Auth moves from "feature" to "configured," freeing roadmap capacity for actual differentiation.
• Frontend/backend contract risk. Wayfinder generates typed functions from Laravel routes, so React code never hardcodes URLs. PM-relevant because route-drift defects are a recurring integration cost in SPA builds.
• Use-case fit: internal admin tools, SaaS MVPs, agency/consultancy repeatable stack, and any team already React-committed and wanting opinionated defaults rather than a blank slate.

When to Consider This Package

Consider it when all of the following hold:

• Greenfield project; no meaningful legacy Laravel code to reconcile with.
• Team is committed to React (not Vue, not Livewire) and to Inertia as the SPA layer.
• You value strict typing and static analysis enough to accept the friction — this kit is explicitly "ultra-strict" and will slow down engineers who don't work that way.
• You are willing to own a fork. There is no semver contract, no upgrade tooling, and no downstream community to absorb breaking changes for you.
• You can absorb bleeding-edge pins: PHP 8.5, Laravel 13, Inertia v3, Pest v5, Larastan v3. Confirm each is stable and supportable on your timeline before committing.
• You want the Action pattern or are indifferent — if your team has a strong competing convention, you'll be fighting the scaffold.

Look elsewhere when:

• You need vendor-backed support, LTS guarantees, or procurement-approved provenance. Single-maintainer project; high credibility, high bus factor.
• The first-party Laravel starter kits satisfy your requirements — they carry official support and a larger user base, which is usually the right default for teams without a specific reason to deviate.
• You need Vue, Livewire, or a Blade-first stack.
• You're adding to an existing application — this is a skeleton, not an installable package, and retrofitting it is a rewrite, not an integration.
• Your team lacks React depth, or your delivery timeline can't absorb the learning curve of the strict-mode toolchain.
• You need a minimal skeleton — this one is batteries-included and opinionated, and removing pieces costs more than starting clean.

How to Pitch It (Stakeholders)

To executives: This is a pre-built, quality-gated starting point for new Laravel + React applications. It encodes our engineering standards — strict typing, static analysis, automated testing, typed frontend/backend contracts — into the scaffold itself, so quality is enforced by tooling rather than by reviewer diligence. Expected benefit is reduced time-to-first-release and lower rework on new projects. Two caveats to state plainly: it is a community project by an individual maintainer, not a supported vendor product, so we adopt it as an internal fork we own and patch; and it tracks very recent framework versions, so we should validate stability before the first production commitment.

To engineering: Clone-and-own. Batteries included: Fortify auth (including 2FA), Inertia v3 + React, Wayfinder typed routes, Pest v5, Larastan v3, Pint, Rector, Pail, and Boost MCP. Conventions are pre-loaded for AI assistants via AGENTS.md, so agent-generated code follows house style and the Action pattern. The tradeoff is explicit: you inherit ultra-strict defaults and a very new dependency matrix, and you own upgrades — there is no upstream migration path. Recommendation is to fork, pin, and treat the divergence as a maintained internal template rather than tracking upstream continuously.

Positioning statement: Adopt this if you are React-committed, greenfield, and want opinionated quality gates for free; default to the official Laravel starter kits if you need first-party support or a broader safety net.