Agent Ready Starter · Free founder setup wizard

Step 1 · Before you begin

Create the three accounts you will use.

You do not need to connect anything yet. Open each service, create an account or sign in, then return to this wizard.

About 10 minutesUse an email you can access

Why three accounts? GitHub stores the project, Supabase stores the app’s data, and Vercel puts the app online.

GitHub

Your project’s online folder and change history.

Create GitHub account

Supabase

The database that will hold users and app information.

Create Supabase account

Vercel

The service that will publish your proof of concept online.

Create Vercel account

✓You are ready for the next step when all three dashboards open. Keep those tabs available. The wizard will tell you when to use each one.

Step 2 · GitHub

Create an empty private repository.

GitHub cannot make a fork of a public repository private. Instead, create an empty private repository first; your coding agent will copy the starter into it in Step 3.

About 5 minutesPrivate from the beginning

Open GitHub’s new repository page.
Select your GitHub account as the owner and give the product a short, recognisable name.
Select “Private.”
Only you and people you invite will be able to view this repository.
Leave the repository empty.
Do not add a README, .gitignore or licence—those files already exist in the starter.
Select “Create repository.”
Keep the new repository page open so you can copy its HTTPS address in Step 3.

Create a private GitHub repository

github.com · Create a new repository

Owneryour-github-name

Repository namemy-product

● Private · no starter files selectedCreate repository

1Choose your account and name the product.

2Select Private, leave it empty, then create it.

✓Your project starts private, but privacy does not make committed secrets safe. Step 5 enables the starter’s pre-commit secret scan, and GitHub Actions checks pushes and pull requests again.

Step 3 · Your computer

Copy the starter into your private project.

Your coding agent will download the public starter, connect the local folder to your empty private repository and verify the safety checks before the first push.

About 10 minutesNode 22.12 or newer

Install these first: Node runs the project on your computer. Then choose either Codex or Claude Code as the coding tool that will help you work on it—you do not need both.

Install Node.js Get Codex Set up Claude Code

Copy the private repository’s HTTPS address.
Copy it from the empty repository page you created in Step 2.
Paste the setup prompt into your coding agent.
Replace YOUR_PRIVATE_REPO_URL with the address you copied and tell it where the local project folder should live.
Review the connections before the first push.
The agent should show origin pointing to your private repository and starter-upstream pointing to Modais.

Prompt to paste: “Set up a private project from https://github.com/Modais-AI/modais-agent-ready-starter. Clone the starter into my projects folder, rename its existing remote to starter-upstream, and add YOUR_PRIVATE_REPO_URL as origin. Show me both remotes without credentials. Run npm install, enable the repository’s pre-commit hook, and run the secret scan. Use read-only or dry-run checks, then ask before the first push. Never display or change private keys, tokens or passwords.”

Do you need SSH? No—HTTPS is the simplest starting option. If you choose SSH, ask the agent to check for an existing key first, never overwrite a key, help you add only the public key to GitHub and verify the connection.

Read GitHub’s SSH guide

Local workspace

MY-PRODUCTAGENTS.md
CLAUDE.md
README.md
src/
supabase/
docs/

# The agent prepares the private copy
$ git clone https://github.com/Modais-AI/modais-agent-ready-starter.git my-product
$ git remote rename origin starter-upstream
$ git remote add origin YOUR_PRIVATE_REPO_URL
origin → private · hook → enabled

1The agent instructions are already in the folder.

✓You know it worked when origin is private and the secret scan passes. The hook blocks likely keys before commits; the GitHub workflow checks them again after a push.

Step 5 · Guided setup

Let the starter connect your local settings.

Open the terminal inside your coding tool. Run each command below, one at a time. When asked, paste the two Supabase values you copied in Step 4.

About 5 minutesSafe to rerun

Terminal · guided setup

Agent Ready Starter setup

$ npm install
$ npm run setup:guided

Supabase Project URL [missing]: https://your-project.supabase.co
Supabase publishable key [missing]: ••••••••••••••••
Optional service-role key [leave blank]:
✓ Updated .env.local and enabled the secret-scanning hook.

1Paste only browser-safe Supabase values here.

✓You know it worked when the terminal says it updated .env.local and enabled the secret-scanning hook. Leave the service-role prompt blank.

Step 4 · Supabase

Create Supabase, then let your agent connect it.

Create a new Supabase project for this proof of concept. Your coding agent can then link the starter to it, preview the database changes and apply the migrations for you.

About 15 minutesYou approve every database push

Create your Supabase project.
Select “New project,” give it your product name, create a secure database password and choose a nearby region.
Copy the two browser-safe values.
Open Project Settings, then API. Copy the Project URL and publishable key. Never copy the service-role key into chat.
Ask your coding agent to connect it.
Use the prompt below. You will privately complete the Supabase sign-in, then the agent will show you the linked project and migration preview before asking to apply anything.

Prompt to paste: “Connect this starter to my new Supabase proof-of-concept project. Let me complete the private login, link only to the project I choose, show me the project and migration dry-run, then ask before applying anything.”

Open Supabase dashboard

Supabase · Project settings

PROJECTGeneralAPIAuthenticationDatabase

Project API

Project URLhttps://project.supabase.coCopy

Publishable keysb_publishable_••••••••Copy

Service roleKeep this server-onlyPrivate

1Copy the Project URL and publishable key.

Coding agent · Supabase connection

Connect this proof of concept to Supabase

$ npm run supabase:login # you complete sign-in
$ npm run supabase:projects # confirm the project
$ npm run supabase:link # choose your project
$ npm run supabase:plan
✓ Preview: 0001_initial_schema.sql

Agent: I am linked to “my-product”. May I apply this migration?
$ npm run supabase:push # only after you approve

2The agent must show the project and preview before it changes the database.

!This gives the agent the ability to change the linked database. Use a disposable proof-of-concept project with no real customer or production data. Review the project name and dry-run every time, and never approve reset, repair or destructive data commands.

✓You know it worked when the agent reports that the migration was applied and npm run supabase:verify passes. Keep the Project URL and publishable key ready for Step 5.

Step 6 · Vercel

Put the proof of concept online.

Open Vercel, choose “Add New Project,” then import the GitHub repository you created. Add the same two Supabase values before selecting Deploy.

About 10 minutesPreview deployments included

Open Vercel projects

Vercel · New project

Import your Git repository

your-github-name / my-product

Environment variables

NEXT_PUBLIC_SUPABASE_URLhttps://project.supabase.co

NEXT_PUBLIC_SUPABASE_PUBLISHABLE_KEYsb_publishable_••••••

Deploy

1Add the two browser-safe values before deploying.

✓You know it worked when Vercel gives you a live website address. Open it and confirm the homepage loads.

Step 7 · Final check

Run the doctor, then build one useful thing.

In your coding tool’s terminal, run the doctor command. It reports OK, WARN or FAIL for each connection. Fix anything marked FAIL before building.

About 5 minutesRerun whenever setup feels unclear

Terminal · system connection doctor

$ npm run setup:doctor

[OK] Node: Node v22.21.1 is supported.
[OK] Dependencies: node_modules exists.
[OK] GitHub: origin remote is set.
[OK] Agent instructions: files exist.
[WARN] Vercel: confirm the first deployment.
[OK] Supabase: connected and readable.

Result: 0 failed, 1 warning.

1Zero failures means you are ready to start experimenting.

✓You are ready when the result shows zero failures. Start with: “Read the project instructions. Add a simple page that explains the problem this product solves, then run the checks.”

Build the first version yourself.

Start with the rails already in place.

Set up your first project.