Setup Gate

Verify the workspace, terminal, Node, npm, Git identity, accounts, and project folder before the coach plans or builds.

Goal

Let the trainer confirm your setup before real building starts.

Do now

Run the setup checks and ask for help on anything that fails.

Output

A cleared workspace or a clear rescue path.

Stop when

The trainer has cleared you to continue, or you are in rescue mode.

Setup Gate

What this is

The Setup Gate proves your workspace can read the starter, run commands, save files, and publish later.

Trainer checkpoint: stop here

This is the end of the self-guided Arrival Runway. Work through both checklists below, then raise your hand and ask the trainer to check your setup before any planning or building.

If you are waiting, do not start building to fill the 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.

Do this now

Part 1: Accounts. These only need a browser and a login.

KrackedDevs (KD) account: opened and signed in.
GitHub: opened and signed in.
Vercel: opened and signed in, or I accept screenshot proof as my fallback.

Part 2: Your machine. These need the workspace and the terminal.

The starter folder is open and I can see START_HERE.md and prompts/.
My terminal is open inside the project folder.
node --version returns a version.
npm --version returns a version.
git --version returns a version.
My Git name and email are configured.
The agent can read and update files in this project.

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	Use the fallback lane below

If something is blocked

You can still finish the session

GitHub blocked → a screenshot of your working build still counts as proof.

Vercel blocked → GitHub plus a screenshot still counts as proof.

Node or Git blocked → stay in the planning phase, or use pair mode with a tutor. Do not lose the session to an install.

Fix only the blocker in front of you, then rerun the gate. Never share a password, token, or private key in chat.

Check yourself

Every check above either passes, or I know which fallback lane I am using.
I have stopped and asked the trainer to check me.

You are ready when

The trainer has confirmed your setup, or you have a named fallback lane and permission to continue.

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.
Starting the build before the trainer check.

Next step

When the trainer has cleared you, Build in Your Workspace.