Superstack Laravel Package

Product Decisions This Supports

• Platform expansion (web → desktop/mobile): The NativePHP SuperNative layer lets one Laravel codebase ship a web app, a desktop shell, and a native-ish mobile build. This is the decision it most directly informs — whether to fund a second client codebase or wrap the existing one.
• Back-office build vs. buy: Filament is a pre-built admin panel framework. The starter answers "do we build our own internal admin UI or adopt the Filament ecosystem?" with a working baseline rather than a slide.
• Agent/AI roadmap sequencing: Bundling MCP (Model Context Protocol) signals that AI-agent access is a first-class surface, not a bolt-on. That supports decisions about whether to expose app operations to LLM agents, internal copilots, or automated ops workflows — and whether to do it via a standard protocol rather than bespoke endpoints.
• MVP scoping and time-to-demo: A starter kit compresses the "empty repo to clickable product" window from weeks to days. Useful for roadmap commitments where the first milestone is a stakeholder demo rather than production.
• Agent-assisted development as a delivery model: The repo ships AGENTS.md and a Laravel Boost bootstrap, i.e. it is explicitly designed to be worked on by coding agents. That is an input into decisions about team shape, onboarding cost, and how much of the scaffolding work you expect tooling to absorb.
• Architecture baseline lock-in: Adopting it commits you to Laravel + Filament + NativePHP conventions. That is a roadmap-relevant constraint worth naming before, not after, the first sprint.

When to Consider This Package

Adopt when most of these are true:

• You are already a Laravel/PHP shop, or willing to become one.
• The product is a line-of-business tool, internal ops app, or single-tenant desktop utility — not a consumer-scale, design-heavy web product.
• You need an admin surface and a native/desktop distribution channel in the same release.
• You want an AI-agent integration surface early and prefer a standard (MCP) over custom APIs.
• You are greenfield, small-team, and optimizing for speed to a working demo over long-term upgrade ergonomics.

Look elsewhere when:

• Web-only delivery — the NativePHP half is dead weight, and a lighter Laravel + Filament start would do.
• You need a bespoke design system; opinionated admin scaffolding fights you.
• Enterprise procurement requires vendor SLAs, security review, or LTS support — 99 stars and MIT licensing mean community-supported only, and the starter becomes your fork to maintain.
• You need a managed multi-tenant SaaS foundation; starters like this rarely encode tenancy, billing, or RBAC depth out of the box.
• The team has no PHP depth — the savings evaporate the moment debugging moves into the runtime or the native shell.

Treat maturity as a real risk: low star count and bundled early-stage dependencies (SuperNative especially) mean you should verify the upgrade path across Laravel, Filament, and NativePHP majors before committing a roadmap to it.

How to Pitch It (Stakeholders)

To executives: This is a ready-made application skeleton that gives us an admin console, a path to shipping the same product as a desktop/mobile app, and built-in hooks for AI agents — on day one instead of week six. It is free and MIT-licensed, so the cost is our engineering time plus the risk of depending on a young open-source project. The concrete win is a shorter runway to a demoable product and one codebase instead of three. The concrete risk is that we own the fork and its upgrades, and the native-runtime piece is early.

To engineering: It is a Laravel starter, not a library — we fork it and own it. It brings Filament for the admin layer, NativePHP SuperNative for native shells, and an MCP server for agent access, plus an agent-oriented setup path via Laravel Boost. Evaluate it as a scaffold: confirm the NativePHP build/signing story, measure app size and startup behavior on target platforms, and check the upgrade story across the three major dependencies before we build anything we cannot cheaply replace.