- Is Flirt Kit a Composer library I can require into an existing Laravel app?
- No. Flirt Kit is a skeleton application, not a dependency-injection library. You consume it with composer create-project or by forking the repository, and you own the resulting codebase from that point on. Treat it as the genesis commit of a new product rather than a package you add to a running service.
- How do I install Flirt Kit and what stack does it include?
- Create a project from the repository using Composer's create-project command, then install frontend dependencies and run the usual Laravel setup steps. It ships the RILT stack: React with Inertia.js, Laravel, and Tailwind, plus Filament v4 as the admin panel. It is MIT licensed, so there is no legal friction to adopting or modifying it.
- Which Laravel, PHP, and Node versions does Flirt Kit require?
- Check the repository's composer.json for the PHP floor and the laravel/framework constraint, and package.json for the Node requirement. Because it bundles Filament v4, the Laravel version is also constrained by what that Filament release supports. Pin these versions explicitly in your fork so upgrades stay deliberate.
- Does Flirt Kit include tests, CI, and static analysis?
- That is not visible from the package metadata, so verify it directly in the repository before committing. Look for a test suite, a CI workflow, and static-analysis configuration such as PHPStan or Larastan. The project has no published consumers or issue history, so you would be the first substantive adopter and should add your own quality gates if they are missing.
- Is Flirt Kit ready for production use?
- It is a starting point, not a hardened production build. Skeleton kits typically ship development defaults such as SQLite, the sync queue driver, file sessions, and a basic asset pipeline, all of which need production configuration. Expect to do your own security review, add tests, configure queues and caching, and set up deployment before going live.
- How does Flirt Kit compare to the official Laravel skeleton, Breeze, or Jetstream?
- The official skeleton stays neutral and receives upstream security-relevant changes each major release, which you inherit for free. Breeze and Jetstream add authentication scaffolding for Blade, Vue, or React without bundling an admin panel. Flirt Kit collapses auth, an Inertia React frontend, Tailwind, and Filament into one scaffold, but you take on manual tracking of Laravel upstream diffs. Choose it only if you want exactly that combination.
- Does Flirt Kit include authentication, roles, multi-tenancy, or audit logging?
- Filament v4 provides admin panel authentication and CRUD resources, but role and permission management, multi-tenancy, and audit logging are not confirmed by the available metadata. Inspect the repository to see whether the admin panel is a thin panel provider or deeply customized. Anything missing is work you must plan for, and deep customization raises your future Filament upgrade cost.
- How do I keep a Flirt Kit fork updated with Laravel and Filament upgrades?
- Track the laravel/laravel repository and compare its changes against your fork at each major release, then document a merge or rebase process for your team. Divergence compounds quietly and only surfaces during an upgrade, so schedule a periodic diff review. For Filament v4, pin an exact minor version and read the upgrade notes before bumping.
- Is Filament v4 stable enough to build a Flirt Kit admin panel on?
- Filament v4 is recent and its plugin and API surface is still settling, so your admin panel inherits some churn. Keep the panel close to stock, avoid heavy custom plugins early, and pin the exact version in composer.json. Test upgrades in a branch before rolling them into your main application.
- Can I remove Inertia or use Vue and Blade instead of React with Flirt Kit?
- There is no practical migration path, because Inertia binds React to Laravel's routing and controller contracts. Replacing Inertia with a REST API or swapping React for Vue or Blade costs more than starting from the official skeleton. If your team is Vue-first or Blade-first, use Breeze, Jetstream, or the plain Laravel skeleton instead.