Lesson 27 of 65 · Free to read
Day 27 ΓÇö Planning mode, CLAUDE.md, and persistent project memory.
Month 2 · Week 6 — Claude Code & Agentic CLI Coding Audience: Final-year students & early-career engineers (0–3 years) Format: Self-paced study + optional live clinic · Suggested time: 4–6 focused hours Key tools: Claude Code
Overview
CLAUDE.md and planning mode give persistent project memory: stack, commands, conventions, and “never do X”.
Learning objectives
By the end of this session, you can:
- Explain the core ideas behind: Planning mode, CLAUDE.md, and persistent project memory.
- Apply the ideas using Claude Code on a realistic task (capstone, internship, or first-job style)
- Produce the exercise deliverable with clear success criteria
- Identify common failure modes and how to recover
- Capture at least one reusable prompt, rule, or checklist for your personal library
- Decide what must remain human-reviewed for this class of work
Core concepts
CLAUDE.md contents
How to run tests, package manager, code style, PR expectations, secrets policy.
Planned builds
Require a plan artifact before multi-step features; approve the plan explicitly.
Tooling for today
Primary tools: Claude Code. Prefer official docs when APIs change. When a model invents a symbol, verify against source or docs immediately.
Practice posture
You are a final-year or early-career engineer pairing with a very fast teammate (the model): clear intent, grounded context, inspect consequential changes, keep a paper trail (commits, prompts, decisions).
Process diagram
Watch & learn
Study these free videos before or during the exercise. Each embed is chosen to reinforce today's objectives.
Course video
Course video
Worked example / case study
Scenario
Write CLAUDE.md; run a planned multi-step feature build.
Step-by-step
- Clarify the outcome in one sentence tied to the exercise below.
- Gather grounding context (files, docs, schema, acceptance checks).
- Run the primary tool(s): Claude Code.
- Produce the smallest vertical slice that proves the idea.
- Verify with a command, test, screenshot, or side-by-side comparison.
- Write down one steering note — what you told the AI when it went wrong.
Sample prompt you can adapt
Role: Senior engineer mentoring an early-career developer (pairing with me).
Task: Planning mode, CLAUDE.md, and persistent project memory.
Context: Final-year / early-career project (capstone, internship, or junior role).
Constraints:
- Match existing project patterns
- No new dependencies unless justified
- Include tests or a verification checklist
- Call out assumptions explicitly
Output: step plan first, then code/files, then verification commands.
Hands-on exercise
Primary task. Write a CLAUDE.md for your project and run a planned, multi-step feature build.
Coaching notes
Include “forbidden paths” (e.g., do not edit prisma migrations casually).
Steps
- Set up or open the workspace required by: Claude Code.
- Skim today's core concepts and watch the video(s) before prompting.
- Execute the task in small commits (or saved artifacts if no-code).
- Fill the success checklist below.
- Note one surprise and one process improvement for tomorrow.
Success criteria
- Deliverable matches the exercise description
- You can explain every AI-generated change in plain language
- Verification ran (tests, manual check, or published URL)
- At least one pitfall from this lesson was consciously avoided
- Artifact saved (repo commit, doc, or published link)
Timebox
Suggested: 90–150 minutes of focused build time after study.
Templates & checklists
| Asset | Purpose |
|---|---|
| Prompt stub | Reuse today's structure (role → task → constraints → format) |
| Verification checklist | Tests / manual QA / security skim |
| Decision log | What you delegated vs kept human |
Copy-paste prompt skeleton
## Goal
Planning mode, CLAUDE.md, and persistent project memory.
## Context files
- (list paths)
## Constraints
- Stack: (fill)
- Do not: (secrets, drive-by refactors)
## Definition of done
- Write a CLAUDE.md for your project and run a planned, multi-step feature build.
Daily reflection (3 minutes)
- What did AI do well?
- Where did it confidently fail?
- What rule will you add to your cookbook/rules file?
Common pitfalls
- Empty CLAUDE.md with only marketing language
- Plans that skip tests
- Memory that contradicts Cursor rules
Key takeaways
- Persistence beats re-explaining
- Plans are reviewable artifacts
- Align CLAUDE.md with CI reality
- Tools (Claude Code) change; the judgment skills transfer.
Resources
- Official docs for: Claude Code
- Course cookbook: keep prompts in a versioned Markdown file in your repo
- Prior days this week — skim objectives if you skipped ahead
Self-paced lesson — Mastering AI-Assisted Development & Vibe Coding — Day 27 of 65.