new-project

Files (1)

• SKILL.md

SKILL.md (first lines)

# New Project

Interview first. Understand the product, pick Astro or Next.js, and decide
which extras belong in v0. Then scaffold the smallest working project, verify
it, and push it. Everything else gets added later, one block at a time.

The user is a senior web developer. Skip explanations of basics. Ask only what
you can't infer. Do not silently fill gaps in the stack.

## Gate

Do not create a directory, run a generator, write app files, or open a repo
until all of these are true:

1. You understand the product (name, purpose, who it's for, site vs app).
2. The framework is **Astro** or **Next.js**, chosen after questions — never
   assumed, never a silent default.
3. Each extra that could apply is **in v0**, **later**, or **out**. Ask; do
   not assume.
4. You recapped the stack in a short table and the user confirmed it.

If the user already answered something, don't re-ask. Partial answers are not
permission to scaffold. If they say "just start" without a framework, still
ask the discriminating questions, recommend one, and wait.

## Defaults vs choices

State the defaults. Only ask about them if the conversation contradicts them.
**Framework has no default.**

| Concern | Choice |
| --- | --- |
| Framework | *No default.* Astro **or** Next.js — ask, then confirm. |
| Hosting | Vercel |
| Styling | Tailwind CSS |
| Components | shadcn/ui, base components customized in place (React; on Astro that means the React integration) |
| Package manager | pnpm |
| Tests | Vitest + Testing Library |
| Lint | ESLint, as the generator configures it |
| Repo | GitHub, `jcottam` org, private unless told otherwise |

## Interview

Work in rounds. Don't dump the whole list. Don't implement between rounds. Ask
in the conversation; if the host has a structured question tool, use it.

### 1. Product

Ask:

- Project name
- One-sentence purpose
- Who uses it and what they do in it
- Is v0 a **site** (content, marketing, docs, brochure) or an **app** (auth,
  dashboards, mutations, user-specific data)?
- What must exist on day one vs later?

### 2. Framework — Astro or Next.js

Ask enough to recommend. Discriminators:

- HTML-first pages with islands of interactivity, or React as the default UI?
- Mostly public / static-capable pages, or authenticated / session-heavy flows?
- Content collections, MDX, or marketing as the core — or app routing, server
  mutations, and dashboard UI?

Recommend explicitly, with one or two lines of why:

- **Astro** — content-led sites, marketing, docs, portfolios, mostly public
  pages, islands of interactivity
- **Next.js** (App Router, TypeScript, `src/`) — app-led products, auth,
  dashboards, mutations, React-default UI

If mixed, ask which shape v0 is. **Do not pick one without confirmation.**

### 3. Extras — ask; none ship in v0 unless yes

For each extra that could apply, ask **in v0 / later / out**. Skip only when
the purpose makes it nonsense. When in doubt, ask.

| Extra | Discriminators |
| --- | --- |
| Database | **Supabase** (Postgres, Auth, Realtime) vs **Turso** (libSQL / SQLite at the edge, lighter) vs none |
| Storage | **Vercel Blob** (simple, Vercel-native) vs **Cloudflare R2** (scale, cost, S3, access outside Vercel) vs none |
| Email | **Resend** vs none |
| AI | **Vercel AI Gateway** through the AI SDK vs none |
| Edge and access | **Cloudflare DNS / domains** and/or **Zero Trust (Access)** vs none |

Do not install or configure an extra until the answer is **in v0**. "Later" is
not a yes. Never add an extra because it appears on this list.

### 4. Recap

Print a short stack table: framework, defaults, each extra as in / later /
out. Wait for go-ahead. Then scaffold.

## Rules

- **Build by addition.** Start from nothing and add only what the current step
  needs. No speculative packages, folders, or abstractions.
- **Latest stable.** Use `@latest` installers and resolve versions live. Never
  pin from memory. No canary, beta, or RC.
- **Trust the generator's current output, not your memory of it.** Defaults
  shift between majors (lint config, Tailwind config, CLI flags). Read what
  was generated before building on it.
- **Green before push.** `pnpm check` and `pnpm build` pass before the first
  push.

## Steps

1. **Interview** (see above). Stop here until the gate is met.

2. **Scaffold** the chosen framework. Pass flags rather than interactive
   prompts. If a flag is rejected, check `--help` and current docs.
   - **Next.js:** `pnpm create next-app@latest <name>` with TypeScript,
     Tailwind, ESLint, App Router, `src/`, `@/*` alias.
   - **Astro:** `pnpm create astro@latest <name>` with TypeScript (current
     default), Tailwind, and the React integration. Add the official Vercel
     adapter. Ensure `@/*` → `./src/*` in `tsconfig`.

From jcottam/agent-resources, MIT.

More from jcottam/agent-resources