Recipes

The starter ships 10 agent skills in .agents/skills/. Each is a procedure an agent follows instead of improvising: which file to edit, which rule it will trip, which command proves it worked. pnpm skills:sync copies them to .claude/skills/ on every install, so Claude Code and Codex both see the same set.

These pages are generated from the skill files themselves — the descriptions below are the exact text an agent matches on.

Recipe	What it does
Add category	Add a category to a ZeroDirs directory site.
Add listing field	Add a custom per-listing field to a ZeroDirs directory site via listing.customFields in site.config.ts, put the value in a listing’s extra frontmatter, and surface it on the detail page.
Configure accounts	Set up submitter accounts on a ZeroDirs directory site — features.accounts, sign-in by emailed link, “Continue with Google” through a Google Cloud OAuth client (GOOGLE_CLIENT_ID and GOOGLE_CLIENT_SECRET via pnpm cf:secrets, the redirect URI with its trailing slash), what the /account/ page shows, how the submit form changes, and how to verify or switch it off.
Configure email	Configure transactional email for a ZeroDirs directory site — the submitter receipt, the admin notification and the approval mail.
Generate listings	Fill a ZeroDirs directory with verified listings — the full pipeline from a candidates TSV to a promoted dataset.
Go live	Take a ZeroDirs directory site from a local checkout to a running site on Cloudflare, one question at a time — pnpm cf:setup for the first deploy (Worker name, custom domain or workers.dev, D1, R2, migrations, deploy, admin secret), then the steps it leaves to the owner (D1 as the build source, Workers Builds and the Deploy Hook, email, payments) and how to verify each.
Import listings	Bulk-import listings into a ZeroDirs directory site from a CSV or JSON file with pnpm listings:import.
New pSEO template	Add a programmatic-SEO page template to a ZeroDirs directory site.
New theme	Add or customise a theme preset in a ZeroDirs directory site.
Plan directory	Turn a niche idea into a ZeroDirs directory plan — a candidates TSV of real product names and URLs, plus proposed categories and tags blocks for site.config.ts.

The two-stage content pipeline

Two of these are halves of one job. plan-directory turns a niche into a candidates list of real names and URLs and stops there — it is forbidden from writing descriptions. generate-listings takes that list, verifies every URL resolves, writes each description only from the fetched page, records where each fact came from, and lints the result before anything reaches src/content/. The split exists because that is the point where a language model would otherwise invent products.