Day 09 of 21
What to put in your CLAUDE.md so Claude never forgets your style
Goal: Yesterday you created your CLAUDE.md. Today you make it useful by adding the six things every non-developer should keep in it.
What to do
Get your exact color codes
Start Claude Code and type:
What are the exact hex color codes currently used in my project? List the background color, text color, accent color, button color, and border color.Add exact color codes to CLAUDE.md
Open your CLAUDE.md file. In the Design Rules section, replace your color descriptions with the exact hex codes. Example: "Background: #F5F4F0. Text: #1A1A17. Accent: #9B5C2E."
Get your exact font names
In Claude Code, type:
What font families and font weights are currently used in my project? List every font name and where it is used.Write specific no-go zones
Open CLAUDE.md. In the "What Not To Change" section, make every rule specific to your actual project. Weak: "Do not change the design." Strong: "Never change the hero section on the homepage. Never change the navigation bar font size."
Describe your writing voice
Add a new section to CLAUDE.md called "Writing Voice." Write 2-3 sentences describing how text on your site should sound. Example: "Short sentences. Plain English. No jargon. Friendly but professional. Speak directly to the reader using you."
Add a Current Goal section
Add a section called "Current Goal" to CLAUDE.md. Write one sentence about what you plan to build this week. Update this section at the start of every new week.
Test with a fresh session
Close this Claude Code session. Open a new one. Type:
Read my CLAUDE.md and confirm you have loaded it. Tell me: my exact background color code, my top no-go zone, and my current goal.Expected result
Your CLAUDE.md now has exact color codes, font names, specific no-go zones, a writing voice, workflow rules, and a current goal. A fresh session reads all of it automatically.
Key takeaway
- Vague CLAUDE.md rules get ignored. Specific ones get followed. Exact color codes, font names, explicit no-go zones, a writing voice, workflow rules, and a current goal — those six things transform the file into a genuine project memory.