Get set up for class

I'm a student setting up for class. I've never coded before. Walk me through each step one at a time. Wait for me to confirm before moving to the next step. Explain things simply — if there's a term I might not know (like "repo" or "commit"), explain what it means.

First, ask me for my full name. You'll use it on my website.

Then, check if Node.js and Git are installed on my computer. If they're not, install them for me and confirm they're working before continuing.

Then, build me a website:
- A Next.js app with a single page
- My name in large text
- Below it: "I'm ready to build something great."
- Below that: "BUSI-371 · Rice University · 2026"
- Clean, minimal design. Dark text on light background.
- No images or icons. Just beautiful typography and spacing.

After building it, run it locally so I can see it in my browser. Tell me to open localhost:3000 in Chrome (or any browser) and check it out before we continue. Explain what localhost means.

Once I've confirmed it looks good, help me put it on the internet:
1. Help me create a GitHub account at github.com (skip if I already have one). Explain what GitHub is in one sentence.
2. Install the GitHub CLI and Vercel CLI if they're not installed
3. Create a GitHub repository, commit my code, and push it
4. Help me create a free Vercel account at vercel.com/signup — choose "Hobby" then "Continue with GitHub." Explain what Vercel is in one sentence.
5. Deploy this site to Vercel

Give me the final live URL when it's done and tell me to visit it to confirm it's working.

---

Everything below this line is instructions for the AI, not for you. You can ignore it.

---

IMPORTANT — Technical instructions for Cursor (the student should never have to open or type in a terminal):

Do EVERYTHING from this chat. The student should never type a command in the terminal. The only thing the student should ever have to do is click a link in their browser and approve/authorize — nothing else.

If a background process finishes before the student completes a browser action, don't mention it. Just verify the result after the student confirms. Never make the student feel like something went wrong if it didn't.

1. Git and Command Line Tools: Running `git --version` on a fresh Mac triggers a system popup to install Xcode Command Line Tools. This is expected and takes 5-10 minutes. Do NOT tell the student to open Terminal or run anything manually. Just run `git --version`, and if CLT isn't installed, tell the student: "Your Mac needs to install some developer tools. You should see a popup — click Install and wait a few minutes. Let me know when it's done." After the student confirms, verify with `git --version` again.

2. Node.js installation: Do NOT use Homebrew (it often has permission and macOS version issues). Instead, install Node.js via NVM (Node Version Manager):
   - Run: curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/master/install.sh | bash
   - Then load NVM and install the LTS version: export NVM_DIR="$HOME/.nvm" && [ -s "$NVM_DIR/nvm.sh" ] && \. "$NVM_DIR/nvm.sh" && nvm install --lts
   - IMPORTANT: Before every node/npm/npx/vercel command in this session, always load NVM first with: export NVM_DIR="$HOME/.nvm" && [ -s "$NVM_DIR/nvm.sh" ] && \. "$NVM_DIR/nvm.sh"

3. GitHub CLI installation: Check if gh is installed with `gh --version`. If not, download and install the .pkg from GitHub. The .pkg installer requires admin privileges — use `osascript` to pop a native macOS password dialog (the familiar system prompt students see for app installs) instead of asking them to type a password in the terminal:
   - First, resolve the latest version dynamically (do NOT hardcode a version number — it will 404 when a new version is released):
     GH_VERSION=$(curl -s https://api.github.com/repos/cli/cli/releases/latest | grep '"tag_name"' | head -1 | sed 's/.*"v\(.*\)".*/\1/')
   - Download: curl -LO "https://github.com/cli/cli/releases/download/v${GH_VERSION}/gh_${GH_VERSION}_macOS_universal.pkg"
   - Verify the file is a real installer (should be several MB, not a few bytes). If the download is suspiciously small, the version resolution failed — check https://github.com/cli/cli/releases/latest manually for the correct filename.
   - Install via osascript (pops native password dialog): osascript -e "do shell script \"installer -pkg gh_${GH_VERSION}_macOS_universal.pkg -target /\" with administrator privileges"
   - Tell the student: "Your Mac needs your password to install a tool. You should see a password popup — type your Mac login password and click OK."
   - Verify with: gh --version

4. Vercel CLI installation: Install globally via npm (no sudo needed with NVM):
   - Run: export NVM_DIR="$HOME/.nvm" && [ -s "$NVM_DIR/nvm.sh" ] && \. "$NVM_DIR/nvm.sh" && npm install -g vercel
   - Verify with: export NVM_DIR="$HOME/.nvm" && [ -s "$NVM_DIR/nvm.sh" ] && \. "$NVM_DIR/nvm.sh" && vercel --version

5. GitHub CLI login: The shell runs in non-interactive mode, so `gh auth login` can't open a browser directly. Use this workaround:
   - Run `gh auth login --hostname github.com --git-protocol https --web --skip-ssh-key` as a background command (block_until_ms: 0 or use &), then sleep a few seconds and read the output.
   - It will print a one-time device code and a URL (https://github.com/login/device).
   - Give the student ONLY the link and the code. Tell them to open the link in their browser, enter the code, and click Authorize. That's it.

6. Vercel CLI login: The `vercel login` command auto-detects non-interactive mode and refuses to start the auth flow. Use `expect` (pre-installed on macOS at /usr/bin/expect) to simulate an interactive terminal:
   - Run: expect -c 'spawn vercel login; expect { "Continue with" { send "\r" } timeout { } }; set timeout 120; expect { "Congratulations" { } "authenticated" { } eof { } }' 2>&1 &
   - Then sleep a few seconds and read the output. It will print a device URL with a code (like https://vercel.com/oauth/device?user_code=XXXX-XXXX).
   - Give the student ONLY the link. Tell them to open it in their browser and approve. If they don't have a Vercel account yet, tell them to sign up at vercel.com/signup first, choose "Hobby", then "Continue with GitHub", then come back and open the device link.
   - IMPORTANT: The expect process will likely exit before the student finishes approving in their browser. This is normal. Do NOT tell the student anything went wrong or that something "timed out." Simply wait for the student to confirm they approved, then run `vercel whoami` to verify. The browser-side approval persists regardless of whether the expect process is still running.

7. Vercel deployment: After login is confirmed with `vercel whoami`, deploy with: vercel --yes
   - If `vercel whoami` fails after the student approved, the expect process may have timed out. Re-run the expect command — since the student already approved in their browser, it will complete instantly.

8. All shell commands: Always use required_permissions: ["all"] to avoid sandbox restrictions for installs and network access.

9. Admin privileges: If any command needs sudo (other than the GitHub CLI .pkg install covered above), use osascript to pop a native macOS password dialog instead of asking the student to type in the terminal:
   - osascript -e 'do shell script "<COMMAND>" with administrator privileges'
   - Tell the student: "Your Mac needs your password. You should see a password popup — type your Mac login password and click OK."
   - NEVER ask the student to type `sudo` or enter a password in the terminal.

10. GitHub repo creation: First commit the code, then create the repo and push in one step:
    - Run: git add -A && git commit -m "Initial commit"
    - Then: gh repo create <name> --public --source=. --remote=origin --push

11. Next.js app creation: Use `npx create-next-app@latest <name> --typescript --tailwind --eslint --app --src-dir --no-import-alias --turbopack --yes` to avoid all interactive prompts.