Builder Toolkit
What this is
Builder Toolkit is the reference layer for the technical foundations underneath your builds: your editor, Node, GitHub, deployment, secrets, domains, databases, and login.
It is not a course. You do not finish it. You open the page you need, do the one thing it asks, and go back to building.
The one idea
KDBM Lite teaches you the method. Builder Toolkit explains the machinery that method runs on.
Why it matters
After one guided build, most learners can ship something but cannot yet say what actually happened.
You typed npm install without knowing what it downloaded. You pushed to GitHub without knowing what a commit is. You added a key to a file and nobody explained why that file must never be uploaded.
That gap is fine on day one. It becomes expensive on day thirty, when a deploy fails and every fix looks like guessing.
What to do
Enter where you are blocked
You do not read this top to bottom. Find your situation:
| Your situation | Start here |
|---|---|
| No editor set up yet | IDE Setup |
Commands like npm install are unclear | Node and npm |
| Code lives only on your laptop | GitHub Basics |
| Worried you pushed something private | Gitignore and Secrets |
| Need the project online | Vercel Basics |
| Works locally, breaks when deployed | Environment Variables |
| Want your own web address | Domains and DNS |
| About to share the link publicly | Deployment QA |
| App needs to save data | Supabase Basics |
| App needs user login | OAuth Basics |
Understand the ladder
The pages are ordered as a real dependency chain, not alphabetically:
Editor → Node → GitHub → Secrets → Deploy → Env vars → Domain → QA → Database → LoginEach rung assumes the ones before it. You need an editor before npm means anything, a repository before you can deploy, and a working deploy before a domain or a database is worth attempting.
Do this now
Read the ladder above and name the highest rung you have actually done yourself, without help. That is where you start.
Check yourself
If something is broken right now
This section explains and sets up. It does not repair. For a build that is currently failing, go to Troubleshooting and come back afterwards.
Common mistakes
- Reading all ten pages before building anything. The foundations only stick once you have hit the problem.
- Skipping to Supabase or OAuth before a plain site deploys successfully.
- Treating this as required homework. It is a toolbox, not a syllabus.
- Looking for fixes here. Fixes live in Troubleshooting.
Next step
Start at the bottom rung: IDE Setup.