Academyacademy / vibe-102 / github

GitHub for Vibe 102

What this is

This is the Vibe 102 checkpoint for saving your mini app code on GitHub.

Use the full GitHub reference if you need a deeper explanation.

Why it matters

Vercel deploys from GitHub. If the latest code is not pushed, the live app will not match the app you tested on localhost.

GitHub also keeps project-brief.md with the code, so your tutor can see what the app was supposed to do.

What to do

Step 1 - Check the project first

Before opening GitHub, confirm:

Reference

project-brief.md exists in the project root.
package.json exists.
localhost worked.
The app can add, update, delete, and save with localStorage.
node_modules is not something I should push.

Step 2 - Do these manually in the browser

These steps need you, not the AI agent:

  1. Open github.com.
  2. Log in or create a GitHub account.
  3. Click New repository.
  4. Name the repository after your mini app.
  5. Choose Public unless your tutor says otherwise.
  6. Do not add README, .gitignore, or license if your project already has files.
  7. Click Create repository.

Keep the GitHub page open. You will need the repository URL.

Do not paste your GitHub password, recovery codes, or tokens into AI chat.

Step 3 - Ask AI to guide the terminal push

Use this in the IDE after the repository exists:

Copy prompt
Help me push my Vibe 102 mini app to GitHub step by step.

Important:
- Do not ask for my password, token, or private key.
- Use the integrated terminal in my IDE.
- Check the current folder first.
- Explain each command before I run it.

My GitHub repository URL is:
[paste repository URL]

Before pushing, check:
1. I am in the correct project folder
2. project-brief.md exists
3. package.json exists
4. node_modules is not being committed
5. git status is safe to review

Then guide me through:
1. git init if needed
2. git add
3. git commit
4. adding the remote repository
5. pushing to GitHub
6. checking the files online

Run the commands one by one. Read the AI explanation before pressing Enter.

Step 4 - Confirm the push worked

Refresh the GitHub repository page.

You should see files like:

  • project-brief.md
  • package.json
  • src
  • public
  • Vite config files

If you do not see the files, stop and fix GitHub before going to Vercel.

Common mistakes

  • Using the wrong GitHub account.
  • Forgetting to push project-brief.md.
  • Pushing to the wrong repository.
  • Forgetting to push the latest code before deploying.
  • Pushing node_modules.
  • Pasting tokens or passwords into AI chat.

Vibe 102 / Current checkpoint

GitHub Checkpoint

Ready to stamp - Saved in this browser only.

0 of 16 checkpoints complete

0 of 16 checkpoints complete.