Blogmark

How I use Claude Code for real engineering

via jbranchaud@gmail.com

https://www.youtube.com/watch?v=kZ-zzHVUrO4
Claude Code Matt Pocock

One of the first tips from this video that jumped out at me was one of the first rules that shows up in Matt Pocock's system CLAUDE.md file.

  • In all interactions and commit messages, be extremely concise and sacrifice grammar for the sake of concision.

My initial experience with Claude Code is that it is verbose, excessively so. To counteract that a bit, adding this as a top-level rule to Claude's memory seems very useful.

Another thing that Matt recommends having in CLAUDE.md as part of any planning mode work is:

  • At the end of each plan, give me a list of unresolved questions to answer, if any. Make the questions extremely concise. Sacrifice grammar for the sake of concision.

This gives the human a chance to clarify things and make adjustments before finalizing the plan.

Later as Claude Code gets to the end of writing the first pass of a plan, Matt gets the sense that executing on the entire plan is going to completely overrun the context window. So, he instructs CC to:

make the plan multi-phase