Simple explanation
Welcome to Day 9. Yesterday you created your CLAUDE.md file. Today you make it actually useful. Most people create this file and put three vague lines in it. Then wonder why Claude Code still makes mistakes. The difference between a weak CLAUDE.md and a powerful one comes down to six specific things. Thing 1 — Your exact color values Do not write "warm cream background." Write the actual color code. When you built your site, Claude Code chose specific colors. Find them and write them down. Ask Claude Code: "What are the exact color codes currently used in my project? List the background color, text color, accent color, and button color." Copy those codes into your CLAUDE.md. Now Claude Code will use exactly those colors every time — not its own interpretation. Thing 2 — Your font names Same principle. Ask Claude Code: "What fonts are currently used in my project?" Add those exact font names to CLAUDE.md. Thing 3 — Your no-go zones Every project has parts that are finished and must not be touched. Write them down explicitly. "Never modify the homepage hero section unless specifically asked." Be specific. Vague rules get ignored. Specific rules get followed. Thing 4 — Your writing voice If Claude Code ever writes text for your site — what should it sound like? Example: "Write in short sentences. Plain English. No jargon. Friendly but professional. Talk directly to the reader using you." Thing 5 — Your workflow rules Tell Claude Code exactly how you want it to work with you. "Always use Plan Mode before changing more than one file." "Always tell me which files you changed after every task." These rules turn Claude Code from an unpredictable builder into a disciplined one. Thing 6 — What you are building next Add a section called Current Goal and update it at the start of each week. "Current goal: build the contact page and add email capture to the homepage." This gives Claude Code context before every session so it understands the direction — not just the individual task.
What to do
Open your CLAUDE.md file. Work through each of the 6 things and add your real project details. For the color codes — ask Claude Code first: "What are the exact hex color codes currently used in my project? List background, text, accent, button, and border colors." For the fonts — ask: "What font families and weights are currently used in my project?" For the no-go zones — walk through your site mentally. What is finished? What should never change? Write those down. For the writing voice — read three paragraphs of your existing site content. What tone do you hear? Describe it in 2-3 sentences. For workflow rules — think about what frustrates you most in Claude Code sessions. Write a rule that prevents it. For the Current Goal — write one sentence about what you plan to build this week. Then start a brand new Claude Code session (do not continue an existing one). Watch how differently it responds when it already knows everything about your project from the very first message.
Copy-paste prompt
Read my CLAUDE.md file carefully. Confirm you have loaded it by listing: my project overview in one sentence, my exact color codes, my font names, my top 3 no-go zones, my workflow preferences, and my current goal. Do not make any changes — just confirm what you have loaded.
Course note
Key takeaway
Vague CLAUDE.md rules get ignored. Specific ones get followed. Exact color codes, font names, explicit no-go zones, a writing voice description, workflow rules, and a current goal — those six things transform the file from a placeholder into a genuine project memory.