KDBM Lite · 08 / 10
Setup Gate
Verify the workspace, terminal, Node, npm, Git identity, accounts, and project folder before the coach plans or builds.
Setup Gate
What this is
The Setup Gate proves your workspace can read the starter, run commands, save files, and publish later.
| Check | Pass condition | If it fails |
|---|---|---|
| Project folder | START_HERE.md and prompts/ are visible | Open the unzipped root folder |
| Terminal | Opens inside the project folder | Reopen the workspace from that folder |
| Node + npm | node --version and npm --version return versions | Ask the tutor for the install lane |
| Git | git --version returns a version | Install Git, then reopen the terminal |
| Git identity | Name and email are configured | Set them with tutor guidance |
| Accounts | GitHub and Vercel sign-in works | Reset access before publishing time |
Why it matters
Setup problems become expensive when discovered halfway through a build. Passing the gate now protects the planning and publishing time later.
What to do
Ask the coach to run the safe checks and show you the result. The coach may inspect versions and files, but it must not install packages or create app code yet.
Confirm these statements before moving on:
- The agent can read and update files in this project.
- The terminal is in the correct folder.
- Node, npm, and Git respond.
- Your Git identity is configured without exposing private credentials.
- You can sign in to GitHub and Vercel, or you accept screenshot proof as the fallback.
If one check fails, fix only that blocker and rerun the gate.
Common mistakes
- Installing tools without first checking whether they already exist.
- Continuing with the terminal in the wrong folder.
- Sharing a password, token, or private key in chat.
- Losing build time to an optional account problem when screenshot proof is acceptable.
Next step
When every required check passes, Build in Your Workspace.