Claude Code Daily Tips Series
As a daily Claude Code user for the last 6 months, I’ve learned a lot about Claude Code and agentic coding in general. Trying this thing where I share 1 thing per day. I’m posting on LinkedIn but I’ll update this post with each tip.
Get these tips and more delivered to your inbox. Subscribe at lawrencewu.substack.com
Day 1 - /insights command
I tried the new /insights command in Claude Code in one of my main projects. It analyzed the last 30 days of messages in my project, identified how I work, noted “impressive things” I did, where things went wrong, suggested existing Claude Code features to try which included recommendations to updates to my CLAUDE.md, and new Custom Skills and Hooks to try.
Also neat to see all of the messages, tool calls and sessions labeled by type along with the distribution of my response time and how often I am “Multi-Clauding.” Finally, all those days of micro’ing while playing Starcraft and Warcraft III are paying off.
Day 2 - Standardize on AGENTS.md
If you use more than one coding agent like Claude Code and Codex, it’s helpful to standardize on one AGENTS.md. This is a file that gets loaded into the model’s system prompt and is great for steering the model. Claude Code hasn’t chosen to standardize yet and still uses at CLAUDE.md
Solution: Have CLAUDE.md with one line:
@AGENTS.mdThen just keep your AGENTS.md updated.
Codex will use AGENTS.md as normal. Claude Code will load CLAUDE.md and then load AGENTS.md because it’s referred to.
In Claude Code, if you type /memory, you should see under Project Memory your AGENTS.md referenced.
Day 3 - Self-Improving AGENTS.md/CLAUDE.md
Claude Code, codex and other agents will load AGENTS.md or CLAUDE.md into it’s context (really it’s system prompt) with every message. I’ve recently started being better about updating this file anytime I want to steer the coding agent. For example if the coding agent makes a mistake, for example if it forgets to add the region into a GCP URL, I started manually adding an instruction to my AGENTS.md, “when returning VertexAI URLs, they need location/{region}, here’s an example of one: {put your example url here}”. This worked, Claude Code stopped writing wrong URLs.
I then started creating sections in my AGENTS.md for different types of areas, e.g. data, machine learning, VertexAI, or Big Query to organize these conventions and gotchas.
Then I realized I could just prompt Claude Code to update my AGENTS.md for me. “can you update my AGENTS.md in the relevant section to not do that again?” This worked well, I often had to move what Claude wrote into the right place though.
Then I added a line to my AGENTS.md, “when you have debugged an issue, please update this file in the relevant section with the solution. This could be related to data, machine learning, VertexAI, or Big Query,” That way, Claude Code will periodically update my AGENTS.md
I also saw Anthropic has an official CLAUDE.md management plugin that has a skill for automating this too here. Reading about their plugins is very inspirational on what is possible now: https://github.com/anthropics/claude-plugins-official.
/plugin install claude-md-management@claude-plugin-directoryThen you can trigger the single skill that is part of the plugin called claude-md-improver:
/claude-md-management:revise-claude-md
Day 4 - Auto Memory
Before talking about Claude Code’s auto memory feature, one thing to remember is you can use Claude Code itself to do a lot of its own configuration. This is rather meta like a 3-D printer printing pieces for itself. One example is you can ask Claude Code “can you search my previous claude messages for things i should add to my global CLAUDE.md?”
Another memory related feature that was added as of version 2.1.32 of Claude Code is Auto Memory. See Claude Code’s docs here: https://code.claude.com/docs/en/memory#manage-auto-memory
If you ask Claude Code to remember something it’ll write to a project specific memory folder in a markdown file here: ~/.claude/projects/<project>/memory/. These memories will be used across sessions in your current project. Though only the first 200 lines of the auto memories will be loaded.
From the official docs: “The directory contains a MEMORY.md entrypoint and optional topic files:
~/.claude/projects/<project>/memory/
├── MEMORY.md # Concise index, loaded into every session
├── debugging.md # Detailed notes on debugging patterns
├── api-conventions.md # API design decisions
└── ... # Any other topic files Claude creates- The first 200 lines of
MEMORY.mdare loaded into Claude’s system prompt at the start of every session. Content beyond 200 lines is not loaded automatically, and Claude is instructed to keep it concise by moving detailed notes into separate topic files. - Topic files like
debugging.mdorpatterns.mdare not loaded at startup. Claude reads them on demand using its standard file tools when it needs the information. - Claude reads and writes memory files during your session, so you’ll see memory updates happen as you work.”
If you type /memory you can see if auto memory is being used. See below for what writing this memory looks like:
