Start 1 7

Setup

Read .claude/skills/_shared/teaching-rules.md and follow it for everything below.

cp -rn .claude/skills/start-1-2/assets/scenario/* . 2>/dev/null || true

Lesson 1.7: CLAUDE.md (Project Memory)

Let me show you a problem.

Imagine you close this session and start a new session tomorrow.

You'd have to re-explain everything: Basecamp Coffee, the loyalty program, the quiz idea...

That's exhausting. And wasteful. Those poor tokens.

STOP: Have you experienced this with ChatGPT or other AI tools?

USER: Yes / Definitely

Introducing CLAUDE.md

There's a solution. It's called CLAUDE.md.

It's a special file I read automatically every session. You put it at the root of your project folder.

Every time you start Claude Code, I read it first.

It's like giving me real memory.

STOP: This is the killer feature that makes Claude Code feel like a real assistant instead of a forgetful chatbot. You set the context once, and I know it forever. No more "as I mentioned earlier" or re-explaining your project every session. Make sense?

USER: Yes

The Constitution Metaphor

Think of it like this: CLAUDE.md = constitution, your prompts = legislation.

The constitution sets the foundation. Your prompts are the day-to-day decisions.

STOP: Quiz - what if they conflict? What wins?

USER: CLAUDE.md / Constitution

Exactly! CLAUDE.md wins. It's the higher authority.

What Goes in CLAUDE.md

So what should you put in a CLAUDE.md?

• Program status and goals - like our turnaround mission
• Key metrics to track - the numbers from our CSV
• Stakeholder map - Dana, leadership, store managers
• Brand voice and constraints - how Basecamp talks
• The solution we're building - the Coffee Personality Quiz

Basically, everything I need to know to be useful immediately.

STOP: Think of CLAUDE.md as the briefing doc you'd give a new team member. What do they need to know to be helpful on day one? That's what goes in here. Ready to build one?

USER: Yes

Build the CLAUDE.md Together

Let's build the CLAUDE.md together with Basecamp Coffee context.

STOP: Ask me to create a CLAUDE.md file that captures everything we've learned about Basecamp Coffee, the loyalty program problem, and our solution.

USER: Types command asking to create CLAUDE.md

ACTION: Create a CLAUDE.md file at the root OF THE WHOLE REPO with:

• Project overview (Basecamp Coffee loyalty program turnaround)
• The problem (program has no personality, engagement is terrible)
• The solution (Coffee Personality Quiz)
• Key metrics to track
• Stakeholders (Dana, leadership, store managers)
• Brand voice summary
• What's been done so far
• Next steps

STOP: Look at the file. Does it capture everything important?

USER: Yes / Suggests additions

[If suggestions: incorporate them and update the file]

CLAUDE.md Hierarchy

One more thing: You can have multiple CLAUDE.md files, which work together.

Here's how it works:

~/.claude/CLAUDE.md          ← Global (your preferences everywhere)
~/projects/
  basecamp-coffee/
    CLAUDE.md                ← Project-level (this project's context)
    analysis/
      CLAUDE.md              ← Directory-level (specific rules for analysis work)

They stack from general to specific. More specific ones override more general ones.

So your global preferences apply everywhere, but project-specific context adds on top.

As you can see, I've been using CLAUDE files to guide all of these lessons!

STOP: This means you can set your personal preferences once (like "I prefer concise responses" or "always use bullet points") and they'll apply to every project. Then each project adds its own context. It's how you build a truly personalized AI assistant. Make sense?

USER: Yes

Wrap-up

Meta skill: Creating persistent context so Claude remembers important information across sessions.

The key insight: Instead of re-explaining who you are, what you're working on, and what matters every time - you write it once and Claude knows it forever.

Where else this applies:

• Your personal "life OS" - goals, values, current priorities, how you like to work. Claude knows YOU.
• Client projects - each client gets a CLAUDE.md with their brand voice, key contacts, project history
• Writing a book or long content - characters, plot points, style guide, what's been established
• Side business - your offerings, pricing, customer personas, brand voice
• Job search - target roles, companies you're interested in, your story, salary requirements
• Any ongoing project where context matters

Next up: In 1.8, we celebrate everything you've learned and I'll tease some advanced features coming in future modules - skills, MCP connections, browser control. Plus, we'll preview Module 2 where you actually BUILD the Coffee Personality Quiz.

STOP: Ready for 1.8?

USER: Yes / /start-1-8

Important Notes for Claude

• Create real CLAUDE.md: Actually create the file at the project root with comprehensive content
• Hash symbol demo: The # rule should actually work for the session
• Hierarchy explanation: Make the file tree visual and clear
• Incorporate suggestions: If student suggests additions to CLAUDE.md, actually add them

Success Criteria

• Student understands the problem CLAUDE.md solves (re-explaining context)
• Student understands the constitution metaphor (CLAUDE.md > prompts)
• Student helped create a CLAUDE.md for the Basecamp project
• Student tried the # dynamic rules feature
• Student understands the CLAUDE.md hierarchy (global → project → directory)
• CLAUDE.md file created at project root
• Student is ready for 1.8

ACTION: Before wrapping up, record this lesson as complete by running this WITHOUT NARRATING the raw output:

fspm progress complete cc-everyone-1-7

If it fails because the fspm CLI isn't installed, follow the teaching rules' missing-CLI guidance: tell the learner progress tracking needs the FSPM CLI, offer to install it, and continue the wrap-up either way.

Then close out with the student's options, in natural language (never as a command list):

• Mention they can leave feedback on this lesson anytime — if they have some, collect it conversationally and submit it with the CLI (see teaching rules).
• Remind them, briefly and only if it fits the moment, that they can always ask for a recap, a quiz on what they just did, a saved note, or where they stand in the course.
• End with the next step: when you're ready for the next lesson, use /clear first, then:

/start-1-8