Resource Vault

Reza Process to take control of his website

Step 1 is not redesigning anything yet. First, get control of the hosting, get the code, and make sure you can safely run the website on your computer.

ForRezaGoalOwn the website workflowStart hereHosting and Git repo access
Part A

Get the keys first

1

Ask the designer where the website is hosted

Before touching the design, find out where the live website is actually hosted. The Git repo is the code, but hosting is where the live website runs.

Message to send the designer
Edit before copying

Heads Up

Do not make changes to the live site until you know the host, the deployment flow, and whether the Git repo is connected to automatic deployment.
2

Get the Git repo from the designer

Ask for the repository link, then make sure your GitHub account is added as a collaborator. If the repo is private, you will not be able to clone it until your account is authorized.

What the repo link usually looks like
https://github.com/[designer-or-company]/[website-repo-name]

Send Joe your GitHub username after you create the account. Joe can help authorize the right account and confirm the access path.

3

Create your GitHub account

If you do not already have one, create a GitHub account at github.com/signup. Use an email you will keep long term.

After the account is created, send Joe your GitHub username and the email on the account.

Part B

Set up Git in Claude Code

4

Open Claude Code and install Git

Open Claude Code and ask it to check whether Git is installed. If Git is missing, use the install command for your computer.

Prompt for Claude Code
Check whether Git is installed on my computer.

Run:
git --version

If Git is not installed, tell me exactly which command to run for my operating system, then wait for me to run it.
Common install commands
# Mac with Homebrew
brew install git gh

# Windows
winget install Git.Git GitHub.cli

# Check after installing
git --version
gh --version

Note

If you do not have Homebrew on Mac, install Git from git-scm.com or ask Claude Code to help install Homebrew first.
5

Tell Git who you are

Git needs your name and email so every saved change has an author. Use the same email as your GitHub account if possible.

Run in Terminal
Edit before copying
6

Authenticate GitHub

The cleanest way is to use GitHub CLI. It opens a browser login and connects your computer to GitHub.

Run in Terminal
gh auth login

Choose GitHub.com, HTTPS, and browser login unless Claude Code gives you a clear reason to choose something else.

7

Pull the repo onto your computer

Once the designer has shared the repo and your GitHub account has access, clone the repo.

Run in Terminal
Edit before copying
Prompt for Claude Code after cloning
I just cloned my website repo. Please inspect it and tell me:

1. What platform/framework this website uses
2. How to install dependencies
3. How to run it locally
4. Whether it has environment variables I need
5. How it appears to deploy to the live website

Do not change files yet. Just inspect and summarize.
Part C

Practice safely before changing the live site

8

Run the website locally

After Claude Code identifies the project type, ask it to install dependencies and start the local development server.

Prompt for Claude Code
Set this website up locally.

1. Install the dependencies using the package manager this repo expects.
2. Start the development server.
3. Give me the local URL to open in my browser.
4. If anything fails, explain the exact missing dependency or environment variable.

Heads Up

Local changes do not automatically mean the live website changed. That is good. Practice locally first, then deploy only when you know the flow.
9

Install the Web Design Arsenal from Session 2

Go to the Session 2 resource and install the Web Design Arsenal. This gives Claude Code better design skills and the animation libraries needed for modern pages.

Open: Web Design Arsenal

Note

For Claude Code, follow the full install. If you are using Codex or Gemini CLI later, use the npm library install section only.
10

Create a practice page, not a homepage redesign

Your first change should be a low-risk new page, like a lead magnet page. Do not start by changing the homepage, checkout flow, or navigation.

Prompt for Claude Code
Edit before copying
11

Save the work on a branch

A branch lets you experiment without mixing practice work into the main website. Ask Claude Code to create a branch before editing.

Run in Terminal
git checkout -b reza-lead-magnet-practice
After the page works locally
git status
git add .
git commit -m "Add practice lead magnet page"
12

Do not deploy until the hosting path is clear

Before pushing or deploying, confirm which service hosts the website and whether that service auto-deploys from GitHub. Common hosts include Vercel, Netlify, Cloudflare Pages, Shopify, Squarespace, Wix, WordPress, and traditional cPanel hosting.

Final deployment question for the designer
Edit before copying

Done means

  • You know where the live website is hosted.
  • You have access to the Git repo through your own GitHub account.
  • Git and GitHub authentication work on your computer.
  • The website runs locally.
  • You have installed the Web Design Arsenal.
  • You created a practice lead magnet page on a branch without touching the live site.