Buying the starter gives one GitHub account of yours read access to its private repository
(how that works). A clone is the starter as it ships, demo data
included, and a few commands later pnpm dev runs it with no Cloudflare account, key or database
of your own.
Before you start
Section titled “Before you start”| You need | Check | You should see |
|---|---|---|
Node 22.18 or newer. .nvmrc pins Node 24, the tested version |
node --version |
v24.x.x (or v22.18.0 and up) |
pnpm — package.json pins the version; corepack enable installs it |
pnpm --version |
a 10.x version |
| git — to clone, and to pull updates later | git --version |
any version |
Read access to zerodirs/zerodirs, the private starter repository — granted to the GitHub account you connect on your access page after paying (Your repository access) |
https://github.com/zerodirs/zerodirs, signed in to GitHub |
the repository’s files. A 404 means the signed-in account has no access, or has not accepted the invitation yet |
wrangler is a project dependency, not an install: pnpm exec wrangler runs the pinned one.
Install and run
Section titled “Install and run”-
Clone the repository under the name you want the project to have.
Terminal git clone git@github.com:zerodirs/zerodirs.git my-directorycd my-directoryOver HTTPS:
https://github.com/zerodirs/zerodirs.git. Either waygit remote -vlists the cloned address asorigin, the remote an update comes from. -
Install the dependencies.
Terminal corepack enablepnpm installcorepack enableselects the pnpm versionpackage.jsonpins.postinstallcopies the agent skills into.claude/skills/and prints:skills: N skills → .claude/skills/ (N files) -
Start the dev server.
Terminal pnpm devpnpm devprepares the clone first, printing a line per step:dev: wrote .env from .env.example — placeholder secrets for local developmentdev: applied 2 migrations to the local D1 (.wrangler/state)dev: the local database is empty — seeding the ai-tools demo dataset with its logos (once; needs the network, about half a minute)- It never touches a Cloudflare account and never writes over a file that exists.
- The seed runs only while the local database is empty and ends with
seeded N listing(s) into the local database; a logo it cannot fetch renders as an initial-letter tile. - On the next run line one is gone, line two says
dev: local D1 is up to dateand line threedev: local D1 holds N listings. - The local D1 is what the site builds from, and what lets
/submit/and/admin/work without a Cloudflare account. .envis the whole environment: build-time variables and runtime secrets, a placeholder wherever a secret belongs.pnpm cf:setupreplaces the two admin placeholders with generated values when you go live.
Verify
Section titled “Verify”| Open | You should see | |
|---|---|---|
| The site | http://localhost:4321/ |
the demo directory: the AI-tools dataset, its categories and tags |
| Submissions | http://localhost:4321/submit/ |
the first step of the form, against the local Miniflare database just migrated |
| The admin | http://localhost:4321/admin/ |
the sign-in page. Put your address in admin.emails, sign in with Google or prove the address with the reset link the console provider prints, and the review queue opens |