new-app

Create a new portfolio app named $0 in ~/Dev/$0.

Validation

1. Name format: $0 must be kebab-case. If it contains uppercase, spaces, or underscores, reject and ask for a corrected name.
2. Name collision: check if ~/Dev/$0 already exists. If yes, abort.
3. GitHub collision: run gh repo view {github-username}/$0 2>/dev/null — if the repo already exists, warn.

Information Gathering

Before scaffolding, ask the owner:

1. What does this app do? (one paragraph)
2. Who is it for? (public / family / personal)
3. Preferred stack? (or "you choose")
4. User-facing language? (French / English / Bilingual)
5. Deploy target? (Netlify / Vercel / Cloudflare / local-only for now)
6. Should it get a tile on the hub ({portfolio-site-url})? If yes, get a one-line French tagline, one-line English tagline, and (if it's a real project the hub would feature, not a personal-only tool) a facts line for each language.

Scaffold

Using the answers above, create:

Repository setup

mkdir -p ~/Dev/$0
cd ~/Dev/$0
git init

CLAUDE.md

Create covering: project overview, tech stack, dev/build commands, deployment, and any conventions that override or extend the global CLAUDE.md. Include:

• Project overview from the owner's description
• Tech stack from chosen stack
• User-facing language
• Development commands (npm install && npm run dev, or equivalent)
• Deployment info

README.md

Write a real README (not boilerplate) with:

• Project description
• Tech stack
• How to run locally
• Deployment setup
• Layer 2 frontmatter (per portfolio-conventions) at the very top of the file:

  ---
  name: [Display Name]
  tagline_fr: "[one-line FR tagline]"
  tagline_en: "[one-line EN tagline]"
  facts_fr: "[facts line, only if the app will get a hub tile]"
  facts_en: "[facts line, only if the app will get a hub tile]"
  ---
  

  If the owner only gave one language's tagline (question 6), write only that tagline_* key — do not invent a translation nobody asked for. Omit facts_* entirely for apps that won't get a hub tile.