By the endYour first screen is backed up on GitHub, and you know how to check that any backup arrived.
Your app now exists in exactly one place: your project folder on this computer. A spilled coffee, a stolen bag or a wrong click, and it is gone. A backup fixes that. Claude makes one in a few seconds, and from now on you ask for one after every change that works.
Ask for the backup
Claude does two things, and asks to allow each: it records a snapshot of every file with a short note, then sends the snapshot to your repository on GitHub. Say yes to both.
Check it yourself
Don't take "done" on trust, this first time.
In your browser, go to github.com and open your repository: profile picture, Your repositories, your app's name.
Near the top of the file list is the note Claude wrote and a time like "2 minutes ago". That is the backup.
Click Commits or the clock icon near it to see every backup so far, newest first: this one, and the first one from Part 4.
Each backup is a complete copy of the project at that moment, with a note. Step 5 uses them to go back.
The habit
If you chose it in your rules (Part 4, step 6), Claude backs up after every change on its own. Even so, ask once a week:
Backups can quietly stop for weeks before anyone looks. A send can fail, a sign-in can expire, and the chat moves on. The question above catches it.