← ClaudeAtlas

bootstrap-projectlisted

Use when setting up a new project with the full opinionated workflow — session memory, commit hooks, copyright headers, ROADMAP, and CLAUDE.md. Invoke with "bootstrap project", "setup project", "new project setup", or /bootstrap-project
jkm-4314/claude-code-skills · ★ 4 · AI & Automation · score 80
Install: claude install-skill jkm-4314/claude-code-skills
# Bootstrap Project You are setting up a new project with an opinionated standard workflow. This creates the full project infrastructure: session memory files, commit hooks, copyright headers, ROADMAP, and CLAUDE.md. ## Step 1: Pre-Flight Checks 1. Verify this is a git repository (`git rev-parse --git-dir`). If not, ask the user if you should run `git init`. 2. Check which of the expected files already exist: - `.claude/SESSION_LOG.md` - `.claude/CONTEXT.md` - `CLAUDE.md` - `ROADMAP.md` - `.githooks/commit-msg` 3. If any exist, warn the user and ask before overwriting. ## Step 2: Gather Project Info Ask the user these questions. If they say "just use defaults" or similar, infer from the repo (`package.json`, `pyproject.toml`, `docker-compose.yml`, etc.) and confirm before writing. 1. **Project name** — e.g., "Acme Widget Manager" 2. **Short identifier** — e.g., `widget-mgr` 3. **One-line description** — what the project is 4. **Tech stack** — e.g., "FastAPI + React + PostgreSQL + Docker" 5. **Project ownership** — ask the user to pick one of their configured ownership profiles, or to define a new one inline. An ownership profile is a `(label, copyright-text | none)` pair. Examples: - `Personal` → single-line copyright with the user's legal name - `Company` → multi-line copyright with the company name and a confidentiality notice - `Client / Government / Open-source` → no copyright header (use this for work-for-hire, public-domain, or permissively