Master Claude Code for Production Shipping · 30 min · Claude Code

Anatomy of a Real CLAUDE.md

A CLAUDE.md nobody can prove changed anything isn't context -- it's a file that happens to sit at your repo root.

Hiring signal: Writing project context that measurably changes an AI coding tool's behavior -- not just describing your repo in prose -- is the actual skill separating power users from people who tried it once and moved on.

What you will learn

Distinguish signal from noise in project context
Write a CLAUDE.md for your own real repo
Prove it changed Claude Code's behavior with a before/after test

Introduction

By the end of this course, one real, previously-annoying task in your own repo runs end to end using only the configuration you build across these 5 lessons — a CLAUDE.md, a hook, a subagent, and (if you go that far) a CI integration, working together. Today: the file everything else builds on top of.

What You're Building

A CLAUDE.md for a repo you actually work in, verified to change Claude Code's behavior — not written once and forgotten, and not copy-pasted from someone else's project.

Unlock the full lesson

You've read the first 2 sections. The rest of this lesson covers Signal vs. noise: what actually belongs in this file, Commands, Conventions, Gotchas, Prove it, don't assume it, What you're building today — plus a hands-on lab, quiz, and project artifact.

Create a free account to unlock Phase 0 and Phase 1 of every course — no credit card.