Questions
Straightforward answers to the things people ask most.
Who is this for?
Mostly solo founders and small teams who are building real products, not demos. If you have tried using AI to write code and keep running into messy output, scope creep, or broken builds, this gives you a repeatable way to fix that.
How long does it take?
Most people work through the core modules over a weekend or a few focused evenings. After that, the templates and toolkit stay useful for every project you work on. There is no deadline or cohort schedule.
What do I actually end up with?
A working web app with real authentication, payments wired up, and a deploy pipeline. You also walk away with a set of templates, checklists, and prompt patterns that you will keep using long after you finish the modules.
Do I have to use Next.js?
The modules use Next.js and TypeScript because they are a good fit for this kind of workflow. But the prompts, the verification habits, and the cost discipline all transfer to whatever stack you prefer.
What does local-first mean?
It means you develop on your own machine using VS Code, own every file, and push to your own GitHub repo. There is no cloud IDE sitting between you and your code. If you want to leave, everything comes with you.
How much does AI usage cost?
Probably less than you think. One of the modules is specifically about picking the right model for each task so you stop overpaying. Most people waste money because they use the same expensive model for everything, including things a cheaper one handles fine.
What does production-grade mean here?
It means the build passes with no errors, auth and payments actually work, errors are handled, and the app runs on a real URL that other people can visit. Not a localhost screenshot.
Do I need coding experience?
You should be comfortable using a terminal and a text editor. The AI handles most of the code generation. Your job is to write clear specs, keep the scope tight, and verify what comes back.
What if I get stuck?
Each module includes debug playbooks and checklists for the most common problems. If those do not cover it, use the contact page to reach out. Founding Members get direct support.
Are there updates?
Yes. Founding Members have lifetime access, which includes any new modules, templates, or toolkit additions that get published later. No extra charge, no upsells.
Do I have to use your exact docs files?
No. The names and format are suggestions. What matters is that you have an equivalent system: something that captures execution rules, project invariants, current state, and lessons learned. Call the files whatever you want, organize them however makes sense for your project. The point is that your AI agent gets reliable context at the start of every session, not that you copy our filenames.
Do I need different docs for web vs mobile?
Same structure, different details. CLAUDE.md, INVARIANTS.md, and ARCHITECTURE.md work the same way regardless of platform. The differences show up in VERIFICATION.md (web uses npm run build, mobile might use xcodebuild or gradle), RELEASE_CHECKLIST.md (app store submissions vs. Vercel deploys), and STACK.md (React Native, Expo, or Flutter instead of Next.js). Use the same folder layout and the same generator prompt. It handles all of this when you tell it your targets.