- What PHP version does lyrihkaesa/filament-starter-kit require?
- The release notes declare PHP 8.3 or higher, but they also reference PHP 8.4-style attributes such as #[WithoutIncrementing], #[Fillable], and #[Guarded]. You should verify the actual platform requirement in composer.json and the CI matrix before planning your container or runtime upgrade. If those attributes are PHP 8.4-only, the declared 8.3 floor will fail in CI.
- Which Laravel and Filament versions does this starter kit support?
- Version 1.2.0 targets Laravel 13 and Filament 5, with PHP 8.3+ declared as the floor. It also pulls in Filament Shield, Curator, Impersonate, Pest 5, PHPStan at level max, Rector, Pint, Vite, Tailwind, and Playwright. Because these are major-version boundaries, confirm that your host, CI images, and other packages support the same lines.
- Is filament-starter-kit a Composer package I can install into an existing Laravel application?
- No. It is a scaffolding template rather than a runtime Composer dependency, so you create a new project from it and then own and diverge the code. Brownfield adoption is low-to-moderate and usually means porting selected models, Filament resources, policies, and tests into your existing app rather than merging the kit wholesale.
- How do I install the filament-starter-kit?
- Treat the repository as a template: create a new Laravel project from it or clone it, then follow the repository README for the exact setup commands. Expect the usual scaffold steps such as composer install, environment file setup, application key generation, database migrations and seeders, and a frontend build with npm. Do not add it as a normal Composer dependency if you intend to customize the generated application.
- Does the starter kit include role and permission management?
- Yes. It integrates Filament Shield for roles and permissions alongside Filament v5 authentication and user management. Shield must be on a Filament 5-compatible major, because mismatched plugin majors are a common source of silent permission and migration breakage. Plan and test role and permission migrations carefully when adopting or upgrading.
- What is the CQRS Action and Query pattern used in this kit?
- The kit includes an opinionated CQRS-style structure using Action and Query classes to separate write operations from read operations. This is application architecture inside the scaffold, not a runtime feature you import from the package. Teams that prefer a different application structure will need to adapt or replace those conventions.
- Does filament-starter-kit include API authentication?
- Yes, the kit includes Laravel Sanctum for API authentication. That makes it more suitable for admin back-offices that also expose a small API than for purely API-first products, which the evaluation flags as a poor fit. You should still review token abilities, route protection, and CORS settings against your own security requirements.
- How do I upgrade filament-starter-kit from v1.1 to v1.2?
- There is no documented v1.1 to v1.2 migration guide, so the supported paths are cherry-picking changes or re-scaffolding a fresh project. The release crosses several major boundaries, including Laravel 13, Filament 5, Pest 5, and a PHP floor change. Budget time for manual comparison and regression testing rather than expecting a simple composer update.
- What testing and code quality tools are included in the starter kit?
- The kit ships with Pest 5, Pint, Rector, PHPStan at level max, and LaraStan, plus a Playwright browser testing layer. The technical evaluation reports 360 passing tests with 1,076 assertions, zero skipped tests, and clean static analysis and formatting. Even if you do not adopt the whole template, its test harness is a strong reference for building your own quality gate.
- Is filament-starter-kit production-ready or too bleeding-edge to adopt?
- The main risk is platform timing, not package quality: Laravel 13, PHP 8.3+, Filament 5, and Pest 5 are new major lines, and managed runtimes, CI images, and container base images may lag. The kit has a credible quality gate, but it is still a single-maintainer template with no stated upgrade path. Before committing, verify PHP compatibility, plugin major versions, Laravel 13 support windows, hosting assumptions, licensing, and the maintainer's release cadence.