S1. Start here
What this page helps you do
Figure out how to use VibeLaunch Framework without reading the whole repo front to back.
Why it matters
Most launch guides assume you already know the shape of the problem. A lot of builders do not. They have an app, some code, maybe a domain, maybe a hosting idea, and a vague feeling that something important is missing.
This guide is meant to reduce that feeling.
You should already have
- an app idea, codebase, or rough prototype
- a willingness to make small practical improvements before launch
Skip this page if
- you already know how the page codes work and want the fastest route
- you already decided your app type and hosting path
In that case, go to S2. Quick start or S4. Choose your path.
What to do
Pick the way you want to use this guide:
- Guided beginner path: start at S2. Quick start, then follow the recommended route.
- Jump by checkpoint: start at S5. What you already have.
- Solve one problem: jump straight to a troubleshooting page like T1. App works locally but not online.
Every major page has a short code so you can move around quickly.
Spages help you startPpages help you pick the right pathFpages cover foundations like GitHub and local runsH,D, andRpages help you actually go liveTpages help you debug launch problems
Recommended default
If you are not sure where to begin, use this path:
- S2. Quick start
- S4. Choose your path
- F1. Put your code on GitHub
- F4. Run your app locally
- H1. Choose hosting
- H6. Deploy your app
- D2. Set up Cloudflare
- D3. Point your domain to your app
- R8. Launch checklist
Common mistakes
- trying to understand every tool before making progress
- jumping into server setup before the app works locally
- assuming a working demo is the same as a launch-ready app
- treating missing evidence as proof that something exists
Next step
Go to S2. Quick start.
Related pages
Advanced notes
If you are using this repo as an audit standard for an AI agent, start with agent/README.md and then use one of the prompts in agent/prompts/.