What's in the kit.
Every claim here maps to code that actually ships in the repo. No aspirational features. Start with the part that's hardest to buy elsewhere: the conventions.
// 00 / the differentiator
Conventions & rails
The thing you don't get from Lovable, v0, or a bare Cursor project: opinionated guardrails that keep an AI agent (and you) on the rails as the codebase grows.
CLAUDE.md, per app & domain
Root + per-app instruction files so Claude Code already knows your conventions on the first clone — not after ten corrections.
Engineering principles, written down
A clear set of rules for keeping code simple and consistent — DRY, YAGNI, KISS and the rest — so your codebase stays clean as it grows, not just on day one.
AI quality gates
typecheck + lint + format must pass before any change counts as "done." The agent checks its own work.
Drizzle migration conventions
A safe, repeatable way to evolve your database. Each work-stream gets its own isolated copy, so two changes happening at once never clobber each other.
MCP-as-API-client
MCP tools are thin clients over your real API — no privileged backdoor backend. The agent uses the same surface your users do.
Monorepo rules
Clear apps/ vs packages/ boundaries, no cross-app imports, one lockfile — so the structure stays legible at scale.
// the apps
What ships in each app
01 · apps/api
Hono + Better Auth + Drizzle on Neon
The backend every SaaS needs, already wired together.
- Sessions, organizations, and invitations out of the box
- Better Auth: email/password + OAuth (Google, GitHub), bearer tokens for CLI/agents
- Drizzle schema + tracked migrations against Neon Postgres
- A real Hono app you test via app.request()
The auth-and-org plumbing that usually eats your first two weeks is done.
02 · apps/web
Vite + React 19 + TanStack Router + shadcn/ui
A real authenticated dashboard, not a hello-world.
- Auth-aware routing patterns wired to the API
- shadcn/ui + Tailwind v4 component conventions
- Dashboard layout + sign-in flows ready to extend
You start from a logged-in app with conventions, not a blank canvas.
03 · apps/cli
Bun-runtime CLI, npm-distributable
A real command-line tool your users (and your agents) can pipe.
- login, logout, whoami, and org commands out of the box
- JSON output mode for agent piping
- Publishable to npm; tested in-process
Distribution and scripting are first-class, not an afterthought.
04 · apps/mcp
TypeScript MCP server (scaffolded)
The slot for your AI-native tooling, pre-wired to the right architecture.
- Workspace member with the MCP-as-API-client pattern documented
- Tools are thin API clients with forwarded API keys — the convention, not the boilerplate
- No privileged backend — same surface as your users
AI-native from the architecture up, not bolted on.