- What is mariojgt/skeleton-admin?
- Skeleton Admin is a Laravel scaffolding package that generates a ready-to-use admin panel skeleton. It wires together Tailwind CSS, Inertia.js, Vue 3, DaisyUI and a multi-guard authentication layout so you can bootstrap back-office screens quickly. It is a starter kit rather than a runtime library: you consume it once at project inception and then own the generated code.
- Is mariojgt/skeleton-admin still maintained?
- No. The repository is archived, which means no security patches, no new Laravel major-version support and no Inertia, Vue or Tailwind compatibility fixes. Adoption signals are also very weak, with only a handful of stars and no active community or issue history to draw on. Treat it as a one-time template or reference implementation, not a long-lived dependency.
- Which Laravel versions does Skeleton Admin support?
- The scaffold was authored against an older Laravel release and has not been updated since the repository was archived. Laravel 11 and 12 restructured the application skeleton, so expect to spend time adjusting the generated structure before it runs cleanly. Always verify the targeted versions before committing to the scaffold.
- How do I install Skeleton Admin?
- Installation is mechanical: create the project with Composer, configure your .env file, run the migrations and seed the database. The real effort is not installation but auditing and pruning the generated code. Budget one to three days to generate, review and trim the scaffold before building features on top of it.
- Does Skeleton Admin support multiple authentication guards?
- Yes, multi-authentication is the headline feature, with separate admin and end-user login flows, route groups and middleware. Multi-auth is also the highest-risk surface in any scaffold, because guard, session and provider misconfiguration can become a privilege-escalation bug. Assume no two-factor authentication, no hardened rate limiting and no email-verification policy decisions, and review the guard setup as untrusted code before going live.
- Can I use Skeleton Admin in an existing Laravel application?
- No, it is designed for greenfield projects only. The value is the wired-together skeleton, and grafting a second auth model or front-end stack onto an existing app usually costs more than it saves. It also fits poorly against Blade or Livewire codebases and API-only services.
- Does Skeleton Admin include tests?
- The scaffold does not ship a meaningful test suite that you can rely on, and nothing in the archive will confirm coverage against a current Laravel release. Treat the generated authentication and authorization flows as untested until you write your own feature tests around them. Prioritise tests for login, registration, password reset and guard separation.
- Is Skeleton Admin compatible with Tailwind 4 and Inertia 2?
- Probably not out of the box. Tailwind v4, DaisyUI's migration to it, and Inertia 2.x conventions all moved after this scaffold was authored, so expect dependency drift and version fixes. Keep DaisyUI styling swappable and component markup thin so you can upgrade or replace it later.
- What are good alternatives to Skeleton Admin?
- The official Laravel starter kits paired with a first-party admin template cover the same ground and stay maintained. Filament or Laravel Nova are stronger choices if you want a supported admin framework rather than generated code you own outright. For Livewire or Blade teams, Breeze or Jetstream is a closer architectural fit.
- Is Skeleton Admin safe to use in production?
- Use it as a reference implementation only: read it, borrow the multi-guard layout and the DaisyUI setup, and do not treat it as a maintained dependency. It is licensed under MIT, so copying and modifying the code is legally clean, but no security patches will ever arrive. Before production, audit the guard configuration, password reset flow and authorization policies, and assign explicit internal ownership for future upgrades.