Small apps built with Claude Code, with the rules written down first.
This is my plan for making consumer apps on my own. I pick the idea and Claude Code writes the code. A folder of notes decides what counts as finished.
The vault
Every session starts by reading the same notes.
They live in one Obsidian folder: 13 playbooks on building, 6 on marketing, and lessons from 8 videos about growing apps. Claude reads the ones that fit the task before it touches anything.
The order an app gets made in
-
01
Idea
I bring it. One sentence on what the app does and who it's for goes into a project note before any code exists.
-
02
Name and look
Twenty or more name candidates, then a search of domains, trademarks, app stores, and social handles for each finalist. The brand kit and mascot get built in Canva after that.
-
03
Data and accounts
Tables go into Supabase with row-level security on, so a signed-in person can read their own rows and nobody else's.
-
04
Payments
Only if the app charges. Stripe runs checkout, and the app waits for Stripe's signed message before it unlocks anything.
-
05
Build
Claude Code builds the screens for a phone first. I test on a real phone, with the keyboard alone, and on a slow connection.
-
06
Launch
The app goes out on Cloudflare. Decisions and mistakes go back into the notes for the next one.
Six tools, one job each
- Hosting
Cloudflare
Serves the app, handles the domain, and filters junk traffic.
- Data
Supabase
Database, sign-in, and file storage.
- Payments
Stripe
Checkout and subscriptions, for apps that charge.
- Design
Canva
Logo, colors, and the mascot each app gets.
- Planning
Obsidian
Holds the notes: specs, decisions, and checklists.
- Builder
Claude Code
Writes the code and drafts the copy, then checks both against the notes.
Rules the work is held to
I choose the idea.
Claude is told never to pick or assume one, and to ask when it's unclear. It asked before building this site.
Small first version, fixed floor.
Four things are never skipped: database rows locked per user, secret keys kept on the server, payment messages verified, and test data kept apart from live data.
Everything on the page is real.
No placeholder text and no invented testimonials.
Finished means checked.
Each playbook ends with a list of checks. Work is done when there's evidence for every line, like a test result or a screenshot.
Honest marketing.
The apps get promoted with ordinary unpaid posts on TikTok and Instagram. I won't buy followers, invent reviews, or run accounts that pretend to be customers, and AI footage that looks real gets labeled.
Where it stands
-
13 Oct 2026
This site went live
It runs on Cloudflare Pages and started the day as a one-page deploy test.
-
12 Oct 2026
The playbooks were written
The building ones come from the official documentation for each tool. The marketing ones come from TikTok's and Instagram's own rules.
-
Next
Pick the first idea
No app has been built from these notes yet.