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.
7. Design direction? (or I propose 2-3) If the owner has one, take it as given. Otherwise load the design-direction skill and run its steps 1-5 on the answers above (question 1 is the subject), and wait for the owner to pick one before scaffolding. Its step 6 (DESIGN.md) runs at scaffold time, below; its step 7 runs once there is a page to render. An app with no UI (CLI, script, library) may answer "none"; record that instead.

Scaffold

Using the answers above, create:

Repository setup

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

DESIGN.md

Unless question 7 was answered "none", write DESIGN.md at the repo root as the design-direction skill's step 6 says (from its references/design-md-template.md). If the owner gave a direction, fill the template from it. The CLAUDE.md "Design direction" section below is the pointer line that step 6 asks for.

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
• A Design direction section from question 7 — later UI sessions read it instead of falling back on a model default. Write the chosen direction concretely, then the avoid-list and the trigger line; do not copy the skill's full list. The avoid-list is not written in this command: read ~/.claude/CLAUDE.md → "Design defaults" at scaffold time and copy its named list of patterns (the items after "Never default to") verbatim, so the new project holds its own self-contained copy of the current list:

  ## Design direction
  
  [Chosen direction in one or two sentences: palette, type, the one signature element.] The full direction is in `DESIGN.md`, this project's identity.
  
  Avoid unless this section asks for it: [the list, copied verbatim from ~/.claude/CLAUDE.md → Design defaults].
  
  **Before any UI or visual work here, load the `design-tells` skill** — it holds the full trap list. This section overrides it wherever they disagree.
  

  If question 7 was answered "none", write the section as a single line: No UI yet — before adding one, load the design-direction skill.