The Claude Code setup I actually run.

I'm a principal PM and I use Claude Code every day at work, backed by 966 memory files. This guide is that setup, page by page, written for teachers, designers, marketers and HR teams as much as for engineers.

New on Product Field Notes: The yes-boss sky

Pick your path

Guides written for the work you already do.

Start with the foundations

The pages people come back to. CLAUDE.md is the one most read.

All docs

Then learn it by doing

New to Claude? Three steps

The guided setup walks you through each one.

Open the guided setup
  1. Pick something you wantA task from your own week, not a demo. Claude learns faster from real work.
  2. Follow the setupInstall, sign in and write a first CLAUDE.md, one screen at a time.
  3. Paste a prompt, watch it goStart with a prompt that already works and change it once you see the result.

966 memory files later, here is what stuck.

The long read on running Claude Code with a memory that size: what held up, and what I threw away.

Read the essay

Latest from Product Field Notes

My Substack, where I publish most weeks: product work, AI in practice, and what broke along the way.

All posts

New guides, when they ship

One email, roughly weekly. CLAUDE.md templates, workflows I actually use, and the cut-for-length stuff that does not make the public guides. One-click unsubscribe.

Or read Product Field Notes, the Substack

Shadman Rahman

Who writes this

I'm Shadman Rahman, a principal product manager. I lead product for student experience and search at Keystone Education Group, and I trained as a designer before moving into product. I started this guide because I kept explaining the same Claude Code setup to colleagues, most of whom don't write code.

More about me