particle-academy/fancy-starter-kit
The Laravel starter kit: a new Laravel 13 + Inertia + React 19 + Tailwind v4 app with Fancy Core (react-fancy, fancy-inertia, fancy-query) already wired and Fortify auth pages built from Fancy Dev Kit. One `laravel new --using=` command; the result is your app, not a dependency.
laravel new my-app --using=particle-academy/fancy-starter-kitAPI surface
Headless package — drive it from code or an agent. No component grid.
Fancy Dev Kit — Laravel starter kit
A Laravel + Inertia + React 19 + Tailwind v4 starter kit with Fancy Dev Kit
preinstalled — use it in place of the official react / vue / livewire
starter kits when you want to build on the Fancy Dev Kit
component suite.
It ships Fancy Core (react-fancy + fancy-inertia + fancy-query), full
Fortify auth (login, register, password reset, dashboard, profile/password
settings) with every page built on Fancy Dev Kit, and a Fancy-branded welcome page
with jump-off points to grow your app.
For agents. This package is listed on the Fancy MCP catalog server at
https://ui.particle.academy/mcp(streamable HTTP, no API key; MCP idfancy-ui), with install commands and docs, alongside the rest of the kit. How an agent installs and uses this package is in AGENTS.md.
Create a new app
laravel new my-app --using=particle-academy/fancy-starter-kit
cd my-app
npm install && npm run build
composer run dev
Then open http://localhost:8000.
What's inside
- Laravel 13 (
type: project) + Inertia (inertiajs/inertia-laravel) - React 19 + TypeScript + Tailwind v4 + Vite
- Fancy Core —
@particle-academy/react-fancy,@particle-academy/fancy-inertia(thesetupFancyAppclient entry),@particle-academy/fancy-query - Fortify auth — login / register / forgot + reset password, a protected dashboard, and profile / password settings — all rendered as Inertia pages built with Fancy Dev Kit primitives
resources/js/
├── app.tsx # client entry — setupFancyApp + providers
├── layouts/ # AuthLayout, AppLayout, SettingsLayout
└── Pages/
├── Welcome.tsx # the branded welcome (guest)
├── Dashboard.tsx # authenticated home
├── auth/ # Login, Register, ForgotPassword, ResetPassword
└── settings/ # Profile, Password
Add components
Vendor Fancy components straight into your app with the CLI:
npx fancy-cli@latest add data-table # one primitive
npx fancy-cli@latest add catalog-fms # a full block (pricing, feature gating, …)
Browse everything at https://ui.particle.academy/packages, or ask the
fancy-ui MCP (start_project, search_components, install_instructions).
Auth (Fortify)
Authentication is powered by Laravel Fortify.
Tune features in config/fortify.php and the create/reset logic in
app/Actions/Fortify/. Two-factor auth is off by default — re-enable it in
config/fortify.php (it needs the two_factor_* columns + the
TwoFactorAuthenticatable trait on App\Models\User).
Factories and fake data
The kit does not install fakerphp/faker, so Laravel's fake() helper is
not defined — Laravel only registers it when Faker is present. Factories and
seeders use the kit's own generator instead, in
database/factories/Support/FakeData.php:
use Database\Factories\Support\FakeData;
'name' => FakeData::shared()->name(), // instead of fake()->name()
'email' => FakeData::shared()->unique()->safeEmail(), // instead of fake()->unique()->safeEmail()
- It is your code, not a dependency. It covers the formatters the kit's own
factories use; when you need another kind of value, add a method (and a test
in
tests/Unit/FakeDataTest.php). unique()never repeats a value for the same formatter, and throws once it runs out. Likefake(), the shared generator belongs to the application container, so each test starts with a clean slate.- Seed it for repeatable data:
FakeData::shared()->seed(1234)yields the same sequence every run, on every machine.
Why: Faker has had no release or commit since February 2026, which fails the
Fancy Dev Kit rule that every third-party dependency has been maintained within the
last three months. If you would rather use it anyway, composer require --dev fakerphp/faker brings fake() back and nothing in the kit needs to change.
SSR
Inertia SSR is wired but off by default — a fresh install renders
client-side. resources/js/ssr.tsx (createFancyServer from
@particle-academy/fancy-inertia/server) renders each page inside the same
Fancy provider tree as app.tsx, and npm run build produces both the client
and SSR (bootstrap/ssr/ssr.js) bundles.
To turn it on:
- set
INERTIA_SSR_ENABLED=truein.env npm run buildphp artisan inertia:start-ssr(keep it running alongside your app)
Inertia falls back to client rendering whenever the SSR daemon isn't reachable, so leaving SSR off — or forgetting to start the daemon — never breaks the app.
The SSR server listens on the port in INERTIA_SSR_URL (default
http://127.0.0.1:13714), the same URL Laravel sends its render requests to.
To run SSR for two apps on one machine, give each its own port there.
Charts
@particle-academy/fancy-echarts is installed. Render charts with
<Chart option={...} height={240} /> from resources/js/components/Chart.tsx
(the Dashboard has one). It loads ECharts, and registers every chart type and
the built-in themes (components/chart-runtime.ts), on demand: a separate chunk
fetched the first time a page mounts a chart. Pages without a chart never
download it, and the server renders a placeholder of the same height.
Import <Chart>, not <EChart>: a value import of @particle-academy/fancy-echarts
in a page puts all of ECharts (about 1 MB minified) back into that page's bundle.
If your app uses only a few chart types, register just those in
chart-runtime.ts.
Sessions, queues and cache
The kit uses Laravel's database driver for all three
(SESSION_DRIVER, QUEUE_CONNECTION, CACHE_STORE), so a fresh install needs
nothing extra and behaves the same on every machine and in CI. Atomic locks
(Cache::lock()) work on the database store too. The REDIS_* lines in
.env.example are Laravel's defaults and are unused until you point a driver at
Redis.
To move to Redis, pick a client and install it first. Laravel fails at the first Redis call if the chosen client isn't there:
phpredis(REDIS_CLIENT=phpredis) is a PHP extension. It's the faster choice, but every dev machine, CI image and server needs theredisextension.predis(REDIS_CLIENT=predis) is pure PHP:composer require predis/predis. It works anywhere PHP runs.
Then set SESSION_DRIVER=redis, QUEUE_CONNECTION=redis and/or
CACHE_STORE=redis, and the REDIS_HOST/REDIS_PORT/REDIS_PASSWORD for your
server.
License
MIT.

