- What is joshcirre/fission?
- Fission is an opinionated Laravel starter kit built around Livewire 4, Flux 2, Tailwind 4, and Pest 4. It is distributed as a fork-and-own project rather than a Composer library you depend on, so you clone or template the repository and maintain it yourself. It bakes in team-aware conventions such as current_team_id, team-scoped routes, and TeamPolicy authorization.
- Can I install Fission with composer require?
- No. Fission has no composer require upgrade path and no semantic-version contract because it is a starter kit you fork and own. You start from the repository, run composer install and bun install, configure the environment and database, then migrate and seed. All future upgrades are manual diffs you apply yourself.
- What are the requirements for Fission?
- Fission targets a bleeding-edge stack: PHP 8.4, Laravel 13, Livewire 4, Flux 2, Tailwind 4, Pest 4, Larastan 3, Rector 2, and PHPUnit 12. You also need Node with Bun for the frontend pipeline and a database supported by Laravel 13. Confirm your CI and hosting images support PHP 8.4 before starting.
- Is Fission a good fit for an existing Laravel app?
- Retrofitting Fission into a mature application is not recommended. Its value comes from conventions applied from commit zero, including team-scoped routing, Flux components, and agent guidelines. Grafting those onto an existing codebase produces churn without the coherence. Use it for greenfield projects only.
- Does Fission support multi-tenant teams?
- Yes. Team awareness is a first-class convention: users carry current_team_id, URLs are team-scoped such as /{team}/playground, owned records carry team_id, and authorization runs through membership checks plus TeamPolicy. This is an asset for multi-tenant B2B products. It is dead weight and extra surface area for single-tenant or API-first products.
- Do I need a paid Flux Pro license for Fission?
- Fission uses Flux 2 free plus Flux Pro 2, which is commercial and licensed per seat. A lapsed license degrades the UI and may breach terms, so confirm seats and a renewal owner before a pilot. Budget for it as a recurring cost, not a one-time purchase.
- What frontend tooling does Fission assume?
- Fission assumes a Bun-based frontend pipeline with bun run build and composer run dev, plus Tailwind 4 and Livewire 4. It also expects the Laravel Boost v2 MCP toolchain for tools like database-query, database-schema, get-absolute-url, and browser-logs. Teams on npm-only workflows or editors without MCP support lose part of the value.
- How do I keep a forked Fission project up to date?
- There is no upstream patch channel. Treat upstream as inspiration rather than a support contract, keep your diffs small and documented, and run an upstream-diff ritual each minor Laravel or Livewire cycle. Assign an owner to refresh AGENTS.md whenever dependencies move, because stale version pins cause agents to follow outdated rules.
- What is the agents/AGENTS.md layer in Fission?
- It ships Laravel Boost v2 with version-pinned ecosystem context and seven activation-gated skills covering Laravel best practices, Livewire, Flux UI, Pest testing, Tailwind, Blaze optimization, and Instruckt. This layer encodes an opinionated engineering operating model: Artisan-first workflow, programmatic tests for every change, Pint before finalizing, and searching docs before edits. It is the kit's main differentiator and its main architectural coupling.
- How is testing handled in Fission?
- Fission uses Pest 4 for tests alongside Larastan, Rector, and Pint as quality gates. The bundled agent conventions require every change to be programmatically tested and Pint to run before work is finalized. Treat the test suite as ground truth when agent guidelines drift.