Day 12

Module 2 Review

Finalize your CLAUDE.md, test every section, and create a reusable template.

0 / 7 tasks

The perfect CLAUDE.md

A great CLAUDE.md is like a great onboarding document: it tells a new team member (or AI) everything they need to work effectively from day one. It should be discoverable, specific, and maintained like code.

Final review checklist

markdown

- [ ] Project description is 2-3 sentences, accurate
- [ ] Tech stack lists all key dependencies with versions
- [ ] Directory structure is documented with purpose of each folder
- [ ] Code style covers naming, formatting, imports
- [ ] Rules section has 'Always' and 'Never' blocks
- [ ] Custom commands are defined and tested
- [ ] Common tasks are documented (how to run tests, start dev server)
- [ ] Environment variables are listed
- [ ] Authentication/auth patterns are explained
- [ ] CI/CD context is accurate

Practice Tasks

0 / 7

Audit your CLAUDE.md medium

Go through your CLAUDE.md and verify every section is accurate and up to date.

Test all custom commands medium

Run every custom command you've defined and refine any that need improvement.

Create a CLAUDE.md template medium

Extract the best patterns into a reusable template for new projects.

Get colleague feedback hard

Have a colleague read your CLAUDE.md and identify anything unclear or missing.

Commit to version control easy

Commit CLAUDE.md with a detailed commit message explaining the key decisions.

Write a CLAUDE.md for a new project hard

Start a new small project and write its CLAUDE.md from scratch, applying today's lessons.

Measure the difference medium

Compare Claude's output quality on a task with vs without your CLAUDE.md. Document the differences.

← Day 11: Advanced Patterns ↑ Module overview Module 3: Plan & Loop Modes →