Day-1 Readiness Check

The final Get Started check. If you can complete this in 30 minutes from start to finish, your laptop is ready for Day 1.

If you get stuck on any step, post in #help on Discord before Day 1 — that’s the whole point of this check. We’d rather fix your environment over Discord than in front of the cohort on Saturday.

What you’ll do

A 12-step exercise that touches every part of the toolchain you installed in the installation guide:

1. Clone the cohort’s day1-check repo
2. Open it in VS Code
3. Create a personal branch
4. Edit three files to add your name (the README, a Next.js page, a Python module)
5. Run the Next.js dev server (pnpm install && pnpm dev) — see your name in a browser
6. Run the Python module (uv sync && uv run python -m agents.hello) — see your name in the terminal
7. Take two screenshots (browser + terminal, both showing your name)
8. Commit your changes
9. Push your branch to GitHub
10. Open a draft Pull Request with the screenshots attached
11. Watch the GitHub Actions CI run — wait for green
12. Done!

Where to find the repo

The full step-by-step instructions live in the repo’s README.md. Kamal will share the repo URL on Discord in #announcements once it’s published.

Repo URL: [populated by Kamal — see Discord #announcements]

What you’re proving

If you finish this exercise, you’ve proven you can:

• Clone a repo from the cohort GitHub org
• Open it in VS Code and navigate the file tree
• Install Node dependencies and run a Next.js dev server
• Install Python dependencies and run a Python module
• Make a personal branch, commit, push to your branch
• Open a Pull Request that triggers CI and passes

That’s the same workflow every Week 1+ lab uses. Once this PR is green, you’re administratively and technically ready for Day 1.

What to do if anything fails

• pnpm: command not found or uv: command not found — re-check the installation guide. One of the tool installs didn’t complete.
• GitHub authentication errors — run gh auth status to confirm you’re signed in. If not, gh auth login (covered in installation guide §8).
• CI fails on the PR — read the failing log line. The check verifies your name replaced the placeholder in three files. If you missed one, fix it, commit, push again — the CI re-runs automatically.
• Anything else — post the exact error in #help on Discord with a screenshot of the terminal.