Star it.Clone it.Prompt.Upgrade it.
A pro-grade foundation with proper development standards built in, so Claude Code can build and maintain your project the right way. You own everything it makes. No coding knowledge required.
github.com/dev-geddy/backflipFour prompts from empty folder to running product
Auth, database, admin console and UI system are already wired, so there is no boilerplate left to describe. You start at the feature.
You have Docker and dev tools ready.
What you can do with it, without being a developer
Set it up once by following the steps. After that it's your product to run, and the building happens in conversation.
Say it, don't code it
Describe the feature you want in plain words. The repo ships the instructions Claude Code needs to build it the same way every time.
Run it without a developer
Your own admin area from the first deploy: see who signed up, change settings, keep an eye on things — no terminal, no code.
Bring people in from day one
Add whoever is helping you build or run it, each with their own sign-in and level of access. Owner, admin and teammate exist before your first feature does, so what you build later can be scoped to them instead of bolting permissions on afterwards.
Turn things on with a key
Paste a key in the admin to switch on AI, email or speech. Keys are stored encrypted; swapping providers takes a minute, not a rewrite.
Own the whole thing
Your server, your domain, your database, MIT-licensed code. No seats to buy, no platform to be locked into, nothing to migrate off later.
Ask Claude about your platform
Connect Claude to it and ask who signed up or how things are doing, in chat. You switch it on in the admin; it reads only what your own account is allowed to see.
Decided, documented, and yours to bend
Auth, database, admin and deploys are already decided and running — and the reasoning behind them lives in the repo, in a three-level doc system a coding agent reads before it changes anything. Point it at different infrastructure, bend the conventions to fit the next project, hand it to more people: the baseline holds, so every initiative starts at the feature instead of the scaffolding.
Auth, built in
Google OAuth and email + password, sessions and guards already configured.
Admin dashboard
A working admin surface for users, records, and settings out of the box.
Postgres + Drizzle
Typed schema, migrations, and a query layer — a real database from commit one.
shadcn UI system
Base UI components, theme tokens, and dark mode — consistent from the start.
AI, ready to call
Provider config and typed helpers — swap models without rewiring your app.
MCP connector
A remote MCP server and its OAuth 2.1 provider already ship. Adding a tool is one file — auth, consent and role scoping are done.
From clone to shipped in three steps
Ask your platform questions from Claude
Connect claude.ai, Claude Desktop or Claude Code straight to your platform over the Model Context Protocol (MCP), as an authenticated connector. It signs in as a real account, so it only ever sees what that user's role already allows.
Signed in as a real user
OAuth 2.1, not a shared API key. It authenticates as an actual account on your platform, scoped to that person's existing role.
Read-only, for now
Ask about users, the dashboard summary, and integration status. No write tools in this phase.
Your own tools next
Five tools ship today, and the hard part — OAuth, consent, per-role scoping — is already built. A new tool is one file registered against an existing scope.
Off until you turn it on
Disabled by default — an owner enables it and creates the client in settings. Disconnect any time from the account page; a password change revokes it too.