DEV Community

Rob Nova
Rob Nova

Posted on

Introducing the Websanova Starters

Most projects start the same way. Before you get to anything unique to the app there is auth, account verification, billing, an admin, localization, mail, notifications and a pile of conventions to settle on. The Websanova Starters are a full pass at all of that, built as working apps rather than bare starter kits.

There are three main repos. The API and SPA are plain Laravel and Vue codebases that work fine on their own. The third is a flows repo that centralizes the docs and specs used to drive agentic coding, and the agent files that go with it are just a starting point that can be removed or swapped for other agent tools. All three are currently in beta.

What's in the box

Laravel API

  • Token auth with Sanctum, code-based account verification, password reset and account self-management with soft delete and restore
  • Stripe billing through Laravel Cashier with plans, subscriptions, trials, promotion codes, automatic tax and webhooks
  • Roles and permissions, stats, mail, notifications, backups, S3 file storage and full localization
  • Dockerized dev environment with MySQL, Redis, Mailpit and the Stripe CLI, plus a Pest test suite

Vue SPA

  • A Vite + Vue 3 monorepo with an app, an admin and a shared core, using TypeScript, Tailwind v4 and shadcn-vue
  • Auth, account verification, plans and Stripe subscriptions, promotion codes and trials
  • Localization, timezones, dark mode, mobile friendly layouts, a dialog manager and page transitions
  • A separate admin app with users, plans and stats, on the same shared codebase

Flows

  • Docs, user flows, system flows and diagrams as markdown files
  • A viewer demo so the flows can be read and shared without touching the code

AI

  • MCP servers for users and admins, where clients like Claude sign in with OAuth from just the server URL
  • A shared MCP login page in the SPA for both the app and admin
  • Agent commands for a step-by-step workflow, plus Boost and skills on the API

The flows workflow

"Flows" is just a stand-in for docs, user flows, system flows and architecture diagrams, and pretty much every project has some form of it. In practice though, it rarely plays out the way it should. Documentation becomes an afterthought and slowly drifts from what's actually implemented until it's stale and a burden to maintain.

Agentic coding changes that. Agents take on most of the grunt work, keeping the docs in sync and writing a large portion of the code. That frees you up to focus on app design, architecture, edge cases, security and the flows themselves. The same bird's-eye view makes working with clients and non-technical team members easier. They send over requirements, you work through them together at the spec level, and the agents build from there.

Every new feature starts from the flows. Each code repo includes a .local agent file, ignored by git, that points to wherever your flows directory lives, so you can prompt against a flow straight from the code side. It works both ways too. Some things are easier to work out in code first, and a quick prompt from the code repo updates the matching flow afterwards. The full write-up is on the starters page.

Beta

The core features above are in place and no breaking changes are expected on the way to 1.0, just more polish. The flows format is the part most likely to be reworked, accessibility in the app is built on reka-ui but not yet fully audited, and SMS verification is scaffolded in the API but still needs a phone capture flow. The docs on websanova.com are also AI generated and need a polish pass, so if something reads off, check it against the source.

Try it

The quickest way to see what's included is to try the demos and look through the docs and source code for yourself.

Docs:

Demos:

Source:

Top comments (0)