How to Organize Claude Code for Product

A product manager's field manual for turning Claude Code from a chat-style tool into a persistent, compounding filing system. The central claim: past the basics, your results stop depending on how well you prompt and start depending on how well you file. A good prompt improves one session; a good file improves every session after it.

The author packages their personal workspace as a public GitHub template — claude-code-pm-starter — with three folders corresponding to three rates of change: context/ (slow: product facts, users, positioning), projects/ (medium: briefs vs. task lists), and operations/ (fast: dated meeting notes, status updates). MCPs sit at the fast end for live data; files hold stable truth.

Six practices make it compound: default to the workspace every day and "bank what you learned" after each task; sort files by rate of change, not topic; let Claude maintain the map (CLAUDE.md, kept small — "the map points, the files carry"); turn repeated verbs into skills while nouns live in files; file every correction once ("if you've said it twice, it belongs in a file"); and ask Claude before assuming something is too technical.

The payoff is quiet: shorter prompts, fewer corrections, and sessions that start mid-work rather than at the beginning of a job description.