section

Part 3 — The machine

Learn the terminal, editor, runtime, Git, GitHub, assets, and web-service layers needed by the two projects.

These pages explain the tools that the project routes ask you to use. Open the one that unblocks the current step.

Lesson	Use it when
Read what the terminal will do	A lesson or agent proposes a command.
Work in a project folder	You need to find source, assets, configuration, or the agent panel.
Node, npm, Bun, and dependencies	A project needs an install, script, package, or lockfile.
Commit, diff, branch, restore	You need a recoverable milestone.
Put history online	You need a remote repository, push, or review.
Give the AI usable material	You are preparing text, images, filenames, and links.
See the whole web stack	You need to place Astro, Next.js, GitHub, Vercel, Supabase, DNS, and the browser.

Return to Start here or start with the terminal.

Read a terminal command's target and side effects before allowing it to inspect, install, change, or delete anything.

Open one project root and locate source, assets, configuration, terminal, version-control changes, and agent activity.

Identify the runtime, package manager, manifest, lockfile, install step, and project scripts before changing dependencies.

Inspect changes, stage only intended files, create a meaningful commit, and understand recovery before discarding work.

Distinguish local Git from GitHub, confirm repository visibility, push the intended branch, and review proposed changes before merge.

Prepare readable Markdown, predictable filenames, useful image alternatives, and relative paths that survive a build and deploy.

Place the browser, framework, repository, deployment host, domain, authentication, and database in the correct layers.