← ClaudeAtlas

new-projectlisted

Scaffold a new project with its own CLAUDE.md and register it in the project registry so every future session has full context. Use when the user says "new project", "start a project", "scaffold X".
KogaCyber/jarvis-skills · ★ 0 · AI & Automation · score 68
Install: claude install-skill KogaCyber/jarvis-skills
# Scaffold New Project Every project your JARVIS touches gets a `CLAUDE.md` — that's what makes session #50 as sharp as session #1. ## Steps ### 1. Create and init ```bash mkdir -p ~/project-name && cd ~/project-name git init ``` ### 2. Write the project's CLAUDE.md ```markdown # project-name One line: what this is and who it's for. ## Stack e.g. Rust/Axum + React/Vite/Tailwind + PostgreSQL ## Structure - `backend/` — API (routes/, services/, models/) - `web/` — frontend - `db/migrations/` — numbered SQL migrations ## Production - Server: <name from ~/.jarvis/servers.md> - URL: https://... - Deploy: see `deploy` skill ## Known Bugs (keep this honest — future sessions read it) ## Log - YYYY-MM-DD — project created ``` ### 3. Register in the registry Append a row to `~/.jarvis/projects.md`: ```markdown | project-name | `~/project-name` | `~/project-name/CLAUDE.md` | server | port | ``` This registry is how one JARVIS juggles many projects without mixing them up: one session = one project, context loaded on demand. ### 4. Scaffold the stack Use whatever the project needs — `cargo init`, `npm create vite@latest`, `docker compose` config. Add a `.gitignore` before the first commit (`.env`, `node_modules/`, `target/`, session files). ### 5. First commit ```bash git add -A && git commit -m "feat: initial project scaffold" ``` ## Checklist - [ ] CLAUDE.md in project root - [ ] Row in `~/.jarvis/projects.md` - [ ] `.gitignore` covers secrets before anything is co