Get the code

Outcome: the repository is on your machine, pnpm install has finished, and .env.local exists. The agent fills .env.local during setup; you do not edit it by hand.

What you need first

The simplest way to get the right pnpm is Corepack, which ships with Node: it reads packageManager and uses that pnpm version inside this project.

corepack enable

A Node version manager that reads .node-version (for example fnm) switches to 22.23.4 when you enter the folder. With nvm, run nvm install 22.23.4 once.

Steps

1. Repository access

You: after purchase you receive access to the private repository. Use the GitHub account that received it in the next step.

2. Clone

You:

git clone <repository URL> my-saas
cd my-saas

Pick any folder name. If you prefer, open your agent in an empty folder and ask it to clone the repository; it uses your Git credentials.

3. Install

You or Agent:

pnpm install

4. Create .env.local

You or Agent:

cp .env.example .env.local

.env.example lists every setting with a comment saying what it is for. .env.local holds your keys for local development. It is ignored by Git and never committed. The agent writes each value into it when the matching skill reaches that step.

5. Your own repository (when you deploy)

Your site lives in its own private GitHub repository. The deploy skills create it for you with the GitHub CLI (gh repo create <owner>/<name> --private --source . --push) when you reach deployment. One rule: the repository name must not end in -starter. The Cloudflare workflow skips the deploy for such names, so a repository named like the starter itself never goes live.

To keep pulling ShipAgent updates into your project, keep the ShipAgent repository as a second remote before the agent sets up yours:

git remote rename origin shipagent

When it fails

Next

Your first session.