Show HN: We got tired of managing Claude.md files, so we built something better (opens in new tab)

(blog.codeyam.com)

4 pointsbastadanii15d ago3 comments

We built CodeYam Memory because Claude Code kept making the same mistakes on our codebase. Our claude.md files quickly got stale and maintaining by hand or with Claude wasn’t sufficient.

While digging into this we found that Claude has a native rules system that allowed us to target specific parts of our repo with path matching.

CodeYam Memory uses a background agent to review your coding session transcripts, identifies confusion patterns, and generates targeted rules with proper scoping.

Install: npm install -g @codeyam/codeyam-cli@latest

Then from your project root run: codeyam

This will launch a dashboard with further instructions for initializing CodeYam Memory.

90 sec demo on our own repo: https://youtu.be/oJ2gTb-lxbE

https://codeyam.com/

3 comments

nadis15d ago

Memory management is one of the most challenging parts of working with Claude Code; too little effort or too much, and you waste tokens and Claude gets confused.

> "We attempted to use CLAUDE.md and continue to do so. Our root-level CLAUDE.md helps communicate some of the rules of our repo, such as approaching changes via test-driven development (TDD), as well as tribal knowledge our team has internalized. However, we don’t want to overload it with information about every area of the codebase, given context window constraints and our desire to avoid confusing Claude with irrelevant details."

Having issues with Claude [dot] md seems to be a common experience, and leveraging rules and having a background agent analyze each session is a clever approach here that works well. I've found this to be incredibly helpful.

j / k navigate · click thread line to collapse