Next step · What to do next

Save my project safely with Git and GitHub

What you may see

I want a backup and history of my project
I have never used Git

Why this step

Git keeps every saved step so you can undo mistakes, and GitHub keeps a copy online; it is the safety net for working with AI tools.

Before you start

Do you have a GitHub account with two-step sign-in turned on?
Does the project contain a .env file or keys? They must be ignored before the first commit.

The prompt for this step

What you type here never leaves your browser. The search runs on this page, and nothing is sent to a server or to an AI.

Any error or warning you see now

What you have now (tool, framework, where it is hosted)

Kept only in this browser, on this device. Keys and passwords are removed before anything is saved.

Prompt language

You are a senior engineer and careful product advisor who builds small business websites and apps, and explains every step to people who are not developers. I am not a developer, so explain every step in plain words and tell me exactly which button, menu or command you mean. If you are not sure about something, say so; do not guess.

WHAT I WANT NEXT
Save my project safely with Git and GitHub

ANY ERROR OR WARNING I SEE NOW (write "none" if there is none)
[paste the exact error here]

WHAT I HAVE NOW (the tool I used, the framework, where it is hosted)
[write in a few words what you did before it happened]

WHY THIS STEP
Git keeps every saved step so you can undo mistakes, and GitHub keeps a copy online; it is the safety net for working with AI tools.

DO THESE STEPS, IN THIS ORDER
1. Check whether the folder is already a Git repository; if not, explain git init in plain words and ask me before running it.
2. Create a .gitignore for this kind of project (node_modules, build folders, .env files, system files) BEFORE the first commit.
3. Search the files for anything that looks like a key or password and tell me before committing.
4. Make the first commit with a clear message, help me create an empty repository on GitHub (private), connect it and push; explain the sign-in method in the safest simple way.
5. Explain a simple routine: commit before every AI task, work on a branch for big changes.
Stop and tell me if what you see does not match a step. Do not skip ahead.

CHECK THAT IT WORKED
- The repository on GitHub shows my files, no .env or keys, and git log shows the first commit.
Tell me exactly what I should see on the screen when it works.

DO NOT CHANGE
- Do not commit secrets or node_modules.
- Anything I did not ask about: the design, the text, other pages, other settings or the data.
- Do not delete files, data or branches, do not reset or force-push, and do not rewrite history, unless you first show me exactly what would be lost and I say yes.
- Do not paste, print or ask me to paste a password or secret key into this chat. If one is needed, tell me which settings page of the right service to store it in.

WHEN YOU FINISH
Explain in simple words what you changed (file by file or setting by setting), why you changed it, and how I can undo it.

Paste it into Claude, ChatGPT, Gemini or Cursor, then follow what it says.

After you tried it, did it work?

Steps

Check whether the folder is already a Git repository; if not, explain git init in plain words and ask me before running it.
Create a .gitignore for this kind of project (node_modules, build folders, .env files, system files) BEFORE the first commit.
Search the files for anything that looks like a key or password and tell me before committing.
Make the first commit with a clear message, help me create an empty repository on GitHub (private), connect it and push; explain the sign-in method in the safest simple way.
Explain a simple routine: commit before every AI task, work on a branch for big changes.

Do not do this

Do not make the repository public if the project is private business work.
Do not commit secrets or node_modules.

Try another entry