Fission Laravel Package

Product Decisions This Supports

• Build vs. buy (or "build vs. fork") for the app skeleton. Fission is not a feature library — it's an opinionated starting point. The decision it informs is whether to spend engineering weeks assembling auth, layout, navigation, team scoping, testing harness, and AI-agent conventions, or to adopt a curated baseline and spend that time on differentiating product work.
• Frontend stack commitment: Livewire 4 + Flux over Inertia/React/Vue. Adopting Fission is a durable architectural bet on server-driven reactive UI in PHP. That choice ripples into hiring profiles, component reuse, and how fast you can ship interactive screens without a JS specialist.
• Time-to-first-demo / time-to-validated-learning. For pre-seed through Series A teams and internal tools, the relevant metric is days-to-working-prototype. Fission compresses the "blank repo to something a stakeholder can click" window, which directly accelerates discovery cycles.
• Team/multi-tenancy scoping as a first-class pattern. The bundled conventions (current_team_id on users, team-scoped URLs, team_id on owned records, TeamPolicy authorization, team switcher rather than a top-level nav item) encode a specific product opinion: teams are an ambient context, not a destination. Adopting this defers the classic "retrofit tenancy later" rewrite.
• AI-assisted development as a first-class workflow. The shipped agents/AGENTS.md and Boost guidelines (skills for Laravel best practices, Flux, Livewire 3→4 migration, Pest, Tailwind, plus MCP tooling for schema queries and log reading) mean the repo is pre-configured for coding agents to operate correctly. This is a real, measurable lever on engineering throughput and on how safely non-specialists can contribute.
• Quality-gate defaults. Pest 4, Larastan 3, Pint, Rector, Sail, and Pail are wired in — the decision here is whether mandatory test coverage and static analysis are policy from day one or an aspiration. Fission makes them the path of least resistance.
• Roadmap sequencing for "table stakes" work. Auth, profile management, password reset, email verification, appearance settings, and shell layout are the tax you pay before differentiating. Using Fission explicitly reclassifies that work as solved, freeing roadmap capacity.
• Use cases where this is a clear fit: internal admin/ops tools, SaaS MVPs and beta products, client delivery shops needing a repeatable house stack, and hackathon/validation spikes that may later graduate to production.
• Explicitly not supported: public-facing marketing pages at scale, heavy client-side interactivity (real-time canvas, complex editors), mobile/native clients, or anything requiring a decoupled API-first backend as the primary architecture. Fission's opinion is a monolith with Blade-rendered reactivity.

When to Consider This Package

Adopt when most of the following hold:

• Greenfield. You are starting a new Laravel application, not retrofitting an existing one. Starter kits do not merge cleanly into mature codebases.
• You have already chosen, or are willing to choose, Livewire + Flux. If the team is committed to Inertia/React/Vue or a separate SPA, the value proposition collapses to "a Blade layout you'll delete."
• You want opinions, not options. Fission is explicitly opinionated. Teams that will immediately fight the team-scoping convention, the nav structure, or the directory layout should pick a slimmer baseline — the friction cost outweighs the scaffolding savings.
• Team is small or the delivery cadence is fast. 1–8 engineers, or an agency shipping repeated similar apps. The payoff is measured in saved setup weeks; large teams with established platform conventions gain less.
• You intend to use AI coding agents. The pre-authored agent guidelines are among the more distinctive assets here. If you're not using agents, you're paying for a benefit you won't realize.
• Flux licensing is acceptable. Flux Pro is a paid dependency; confirm budget and license terms before adopting, since the UI layer is not fully free-tier.
• Version currency is tolerable. Fission targets PHP 8.4, Laravel 13, Livewire 4, Flux 2 — bleeding-edge at time of writing. If your hosting, third-party packages, or client constraints require LTS-stable versions, wait or expect to downgrade.

Look elsewhere when:

• You need a batteries-included admin/CRUD framework. Filament solves a different, larger problem; Fission is a shell, not an application generator.
• API-first or headless architecture is the target. No meaningful value; use a minimal Laravel skeleton plus Sanctum.
• Existing product with established conventions. Grafting a starter kit's AGENTS.md, Pest config, and team model onto a live codebase creates inconsistency for marginal gain.
• You need a large ecosystem and battle-testing. 213 stars and a single maintainer indicate a young project. For a low-risk, long-horizon commitment, prefer laravel/react-starter-kit or laravel/livewire-starter-kit (first-party, larger community) unless Fission's specific opinions — team patterns and agent guidelines — are the differentiator you want.
• You require long-term support guarantees or vendor accountability. Assess maintenance cadence, issue responsiveness, and upgrade path before betting a production roadmap on it. Consider forking and taking ownership explicitly rather than depending on upstream.

How to Pitch It (Stakeholders)

For executives — the one-liner: Fission is a pre-assembled, opinionated foundation for a Laravel product. It converts two-to-four weeks of undifferentiated setup — authentication, user profiles, navigation shell, team scoping, test harness, code-quality gates, and AI-agent conventions — into roughly an afternoon. Every week of engineering not spent on login screens is a week spent on the thing customers pay for.

The business case:

• Compressed time-to-demo. Faster path from idea to something clickable, which shortens the validate-or-kill loop and reduces spend on ideas that won't survive contact with users.
• Lower delivery cost for repeatable work. For agencies and multi-product teams, a house starter kit means each new app begins at a known, tested baseline rather than at zero. Setup cost becomes marginal, not fixed.
• Baked-in quality and security posture. Authentication, authorization patterns, static analysis, and a mandatory testing discipline are defaults rather than things someone remembers to add. This reduces the class of defects that surface late and expensively.
• Reduced key-person risk. The conventions are written down in machine-readable form. A new hire — or an AI agent — reads the repo and follows the house style on day one instead of absorbing it over months.
• Productive AI-assisted development. The repository ships with structured guidance for coding agents. This is a concrete, contemporary lever on throughput, and it means AI-generated code arrives in-pattern rather than needing rework.

For engineering — the honest framing:

• It is a starting point, not a dependency you inherit. The correct mental model is "fork and own," not "install and depend." Expect to delete or rewrite opinionated pieces, especially around team scoping if your product isn't team-based.
• It commits you to Livewire 4 + Flux, plus a current-generation stack (PHP 8.4, Laravel 13, Pest 4, Larastan 3, Tailwind 4). That's an advantage if you're greenfield and current; a blocker if you're version-constrained.
• Flux Pro is a commercial license — budget for it and confirm terms before it becomes load-bearing in the UI.
• Maintenance risk is real but manageable. Small project, single maintainer, modest adoption. The mitigation is straightforward: fork it, pin versions, and treat upstream as a source of ideas rather than a support contract. Budget a small amount of ownership time for upgrades.
• Ask before committing: Does our product actually have a team/multi-tenant model? Are we standardized on Livewire, or is there a React/Vue constituency? Do we have a licensing path for Flux? If the answers are "no," "unclear," or "no," evaluate the first-party Laravel starter kits instead — you'll get less opinion and less friction.

Recommendation: Run a one-week spike — build a single real screen end-to-end on Fission — before adopting it as the house standard. The spike is cheap, and it will settle the Livewire/Flux commitment and the team-scoping question with evidence rather than argument.