- Ruby 86.5%
- Python 7.7%
- HTML 4.3%
- Shell 1.3%
- JavaScript 0.1%
| Filename | Latest commit message | Latest commit date |
|---|---|---|
| .claude | ||
| .claude-plugin | ||
| .codex/skills | ||
| .sdlc | ||
| bin | ||
| docs | ||
| lib | ||
| plugins | ||
| test | ||
| .dochygiene-rules.json | ||
| .gitignore | ||
| .graphifyignore | ||
| .pbm.yml | ||
| .rubocop.yml | ||
| CLAUDE.md | ||
| graphify-interview | ||
| indydevdan-agentic-engineering-overview-video.txt | ||
| memory-systems-compared060326 | ||
| README.md | ||
cc-os — Cross-Project Memory for Claude Code
A personal memory system for Claude Code, designed for a multi-client freelancer. The system captures knowledge across projects and surfaces it automatically at the start of each Claude Code session.
Status
The memory plugin is live and working. Design documentation lives in docs/.
Both episodic memory (memsearch) and semantic/knowledge memory (Graphify + Obsidian vault)
are active.
What it does for you
- Injects vault context at session start — Claude sees your SecondBrain graph summary, your conventions, and today's journal path before you type the first message.
- Surfaces project structure on demand — run one command to build a graph of any project; Claude can then query it for patterns, architecture, and conventions.
- Remembers conventions automatically —
memory-writestores evergreen knowledge (coding patterns, client rules, recurring decisions) in the correct vault location with proper tags. - Stays fresh without a daemon — the vault graph rebuilds in the background when stale; vault writes immediately invalidate the timestamp so the next session picks up changes.
- Keeps project repos clean — all indexes are build artifacts (
graphify-out/); nothing is committed to project repos.
Refactoring a Ruby codebase with CRC
/os-sdlc:crc-refactor renames and moves every Ruby file in a codebase so that
each file is named for its one job and sits in the directory of the concept that calls it.
Use it when a codebase has grown by accretion and you can no longer guess what a file does
from its name or path. It runs unattended: it writes a ledger with a job sentence and a
verdict for every file, applies renames and moves in small green batches, and records each
decision for you to review. The test suite is the proof, so no behavior changes. It has run
on os-backlog and os-sdlc. The plan and records live in docs/crc/.
User guide
See docs/USER-GUIDE.md for setup, onboarding new projects, using the skills, and known limitations.
Directory layout
| Path | Contents |
|---|---|
docs/memory-system/ |
Architecture, ADRs, build plan, Graphify evaluation |
docs/graphify/ |
Verified Graphify command handbook |
docs/crc/ |
CRC refactor plan, ledgers, and run records |
docs/USER-GUIDE.md |
Practical usage guide |
openspec/ |
Spec-driven change management (changes, specs) |
graphify-interview, memory-systems-compared060326 |
Raw source transcripts (do not cite as fact) |