A community-driven registry for the Claude Code ecosystem. Not affiliated with Anthropic.
Are you the author? Sign in to claim
Template for using Claude Code as a planning and implementation engine across target projects. Structured context, goal-
Template for using Claude Code as a planning and implementation engine across target projects. Structured context, goal-driven workflow, growing .claude/rules, specs, and technical decisions — all tracked in one place.
This template depends on the planning-with-files skill for Claude Code. Install it before using this template.
# Recommended — Claude Code plugin
/plugin marketplace add OthmanAdi/planning-with-files
/plugin install planning-with-files@planning-with-files
Verify it's working by starting a Claude Code session — you should see the skill loaded, or type /planning-with-files to invoke it manually.
See the planning-with-files docs for alternative installation methods.
Strongly recommended: Disable auto-compact and use the
/clear→/planning-with-filesworkflow instead:
- When context gets heavy, run
/clearto flush the conversation- Run
/planning-with-filesto reboot with full context from the planning filesThis works because the planning-with-files skill includes a session-catchup script that scans previous session JSONL files to find conversation messages that happened after the last planning file update — recovering unsynced context (decisions discussed, commands run, errors hit) that haven't been written to
task_plan.md,findings.md, orprogress.mdyet. Auto-compacting silently discards that JSONL history, breaking this recovery mechanism.
claude config set --global autoCompact false
cd into it.claude/rules/project-overview.md with your architecture.claude/rules/workflow/local-dev.md with your dev setup.claude/settings.json → additionalDirectories.planning/MILESTONES.md.planning/GOALS.md and invoke /planning-with-files.
├── .claude/ # Claude Code configuration
│ ├── CLAUDE.md # Session start instructions
│ ├── settings.json # Global settings (additional dirs, permissions)
│ ├── settings.local.json # Local overrides (gitignored)
│ └── rules/ # Persistent rules loaded every session
│ ├── project-overview.md # Architecture overview (customize this)
│ ├── security.md # Security rules
│ └── workflow/ # Workflow rules
│ ├── goal-workflow.md # Goal lifecycle (start, ice, complete)
│ ├── branches.md # Branch tracking across repos
│ ├── documentation.md # What to update and when
│ ├── git.md # Branching, commits, safety
│ ├── changelog.md # CHANGELOG convention
│ └── local-dev.md # Dev setup (customize this)
│
├── .planning/ # Planning & tracking
│ ├── GOALS.md # Goal registry (active, iced, complete)
│ ├── MILESTONES.md # Project roadmap
│ ├── TECH_DECISIONS.md # Append-only technical decisions log
│ ├── BRANCHES.md # Active branches across all repos
│ ├── history/ # Completed goal archives
│ └── iced/ # Paused goal archives
│
├── specs/ # Implementation specifications
├── context/ # Domain/system context documents
├── runbooks/ # Operational procedures
├── templates/ # Document templates
│ ├── spec-template.md
│ ├── context-template.md
│ ├── tech-decision-template.md
│ └── runbook-template.md
│
├── task_plan.md # (Created by /planning-with-files for active goal)
├── findings.md # (Created by /planning-with-files for active goal)
├── progress.md # (Created by /planning-with-files for active goal)
│
├── .gitignore
└── README.md
Start Goal Complete Goal
│ │
▼ ▼
Update GOALS.md ──► /planning-with-files ──► Work phases ──► Archive to history/
│ │
│ ▼
│ task_plan.md (phases & tasks)
│ findings.md (research & discoveries)
│ progress.md (session log)
│
▼ (pause)
Move files to .planning/iced/goal-N/
GOALS.md → finds active goaltask_plan.md, findings.md, progress.md → resumes contexthistory/, updates GOALS.mdAppend-only log in .planning/TECH_DECISIONS.md. Never edit past entries — if a decision is superseded, add a new TD-XXX referencing the old one.
.claude/rules/project-overview.md — your architecture.claude/rules/workflow/local-dev.md — your dev environment.claude/settings.json — additional repo directories.planning/MILESTONES.md — your project roadmap.planning/GOALS.md — your first goalcontext/ — your domain context documentsspecs/ — your implementation specificationsThis template uses Claude Code's memory hierarchy as designed:
| Layer | File | Shared | Purpose in this template |
|---|---|---|---|
| Project memory | .claude/CLAUDE.md | Team (git) | Session start instructions, context map, @imports |
| Project rules | .claude/rules/*.md | Team (git) | Workflow rules, security, git conventions — grow these as needs emerge |
| Local memory | CLAUDE.local.md | Just you | Personal project preferences (not committed) |
| Auto memory | ~/.claude/projects/<project>/memory/ | Just you | Claude's automatic learnings per project |
Rules in .claude/rules/ are loaded automatically every session. Add new rule files as your project evolves:
.claude/rules/
├── project-overview.md # Always customize this
├── security.md # Security conventions
└── workflow/
├── goal-workflow.md # Goal lifecycle
├── branches.md # Branch tracking
├── documentation.md # What to update when
├── git.md # Git conventions
├── changelog.md # CHANGELOG format
├── local-dev.md # Dev setup (customize this)
└── your-new-rule.md # Add rules as needs emerge
Rules can be scoped to specific files using paths frontmatter:
---
paths:
- "src/api/**/*.ts"
---
# API rules that only apply when working in src/api/
CLAUDE.local.mdCreate a CLAUDE.local.md in the project root for personal preferences that shouldn't be committed (it's gitignored):
# My local preferences
- I prefer verbose test output
- My dev server runs on port 3001
- Use bun instead of npm
Starter template with CLAUDE.md memory bank system, session metrics, and subagents
Best practices and starter CLAUDE.md templates for Next.js, Python/FastAPI, and more
Persistent memory system for Claude Code — make your AI remember everything across sessions. Ready-to-use templates, zer
Curated exemplary CLAUDE.md files from public projects with analysis and patterns
