init-project-memory

Initialize Project Memory System

You are scaffolding the .claude/ session memory system into a new project. This creates the file structure that the session-start, session-update, and session-end skills depend on.

Step 1: Pre-Flight Checks

1. Verify this is a git repository (git rev-parse --git-dir). If not, stop and tell the user — the session system is git-grounded.
2. Check if .claude/SESSION_LOG.md already exists. If it does, warn the user and ask before overwriting:

   "This project already has a session memory system. Overwrite it? (This won't touch settings.json or skills/)"

Step 2: Gather Project Info

Ask the user:

1. Project name — e.g., "Acme Widget Manager"
2. Short identifier — e.g., widget-mgr (used in headers)
3. One-line description — what the project is
4. Tech stack — e.g., "FastAPI + React + PostgreSQL + Docker" (used in CONTEXT.md template)
5. Should I create a CLAUDE.md? — if one doesn't already exist

If the user says "just use defaults" or similar, infer what you can from the repo (package.json, pyproject.toml, docker-compose.yml, etc.) and fill in reasonable defaults. Confirm before writing.

Step 3: Create Directory Structure

mkdir -p .claude

Step 4: Write Template Files

Create each file. Do NOT overwrite files that already exist (e.g., settings.json, settings.local.json, existing skills) unless the user explicitly asked to reset.

.claude/CONTEXT.md

# {{Project Name}} (`{{short-id}}`) - Project Context

> **Last Updated:** {{MM-DD-YYYY}}
> **Version:** {{version or "0.1.0"}}
> **Status:** {{status or "In development"}}

---

## What This Project Is

{{One-line description. Expand with 2-3 sentences about purpose, users, and scope.}}

---

## Technology Stack

{{Tech stack details — backend, frontend, database, infrastructure.}}

---

## Architecture Overview

{{High-level architecture. Fill in as the project takes shape.}}

---

## Development Environment

{{How to run the project locally. Commands, ports, prerequisites.}}