A System for Claude Code to Learn Your Project Over Time

A developer on r/ClaudeAI shared a system to address Claude Code's lack of persistent context between sessions. Instead of starting from scratch each time, this setup helps Claude learn your project's conventions, architecture, and past mistakes.
The Problem and Solution
When using Claude Code, each new session loses all previous context. Claude re-reads files it already understood, repeats corrected mistakes, and ignores established patterns, requiring constant re-explanation.
The solution involves adding a few files to any repository:
CLAUDE.md- A short set of rules telling Claude how to behave. Examples include "ask before proceeding if something is unclear" and "don't run tests yourself, tell me what to run instead" (which saves money by avoiding token waste on error chasing).docs/folder - Contains short files (5-10 lines each) capturing project conventions, patterns, and architecture, organized into subfolders. An index file (docs/README.md) helps Claude quickly find the right document instead of guessing.
Three Key Prompts
- bootstrap - Pasted once when adopting an existing codebase. Claude reads your code and writes the initial documentation.
- refine - Pasted at the end of a session. Claude reflects on what happened and updates the documentation with new learnings.
- factory - Pasted when Claude does something you want to repeat. It captures the pattern as a reusable prompt.
The Workflow Loop
The process creates a continuous learning cycle: You code with Claude → session ends → you paste the refine prompt → Claude updates the docs → you commit → next session starts smarter. Since the documentation lives in git, everyone on your team benefits from it, and it works with any tech stack.
Practical Tips from Implementation
- Explicitly tell Claude not to run build/test commands to avoid burning tokens chasing errors. Instead, have it tell you what commands to run.
- Use specific numbers in rules (e.g., "pause if changing 3+ files") rather than vague terms like "pause for complex tasks," as Claude wastes time interpreting ambiguity.
- An index file for your docs folder pays off immediately by preventing Claude from opening random files hoping to find relevant information.
The system is free and open source, available at saas-vibe.
📖 Read the full source: r/ClaudeAI
👀 See Also

Claude Code at Scale: How Agentic Search Avoids RAG Failure Modes in Large Codebases
Claude Code uses agentic file-system traversal instead of embedding-based RAG, eliminating stale index issues. The article details five extension points (CLAUDE.md, hooks, skills, plugins, MCP) and the harness-as-model philosophy for multi-million-line repos.

Homebutler: MCP Server for Multi-Server Homelab Management via Claude
Homebutler is a Go binary with a built-in MCP server that lets Claude manage multiple servers over SSH without installing agents on remote machines. It provides 9 tools including system status monitoring, Docker container management, port scanning, and alert rules.

sandboxd: Open-Source Tool to Run Multiple Claude Code Agents in Isolated Containers
sandboxd is an open-source (MIT) tool that runs each Claude Code project in its own Docker container with isolated workspace, Claude Code session, and preview URL. It supports parallel agents, auto-sleep, and keeps API keys out of containers.
Balloon That Pops When Claude Finishes: Physical Agent UI with whisper.cpp
A desktop balloon inflates as you speak a task, then floats across your screen while Claude Code runs the agent. Transcription runs locally via whisper.cpp, agents use your existing Claude Code login. Open source.