TL;DR
- Have Claude update a style or context file every time it makes a decision, so the next session inherits the work instead of relearning it.
- Build a brand voice file once and feed it to every tool, wizard, or session that produces content on your behalf.
- Wrap your documentation in a wizard so raw brain dumps get formatted, structured, and aligned to your standards automatically.
- The 30 minutes you spend documenting a workflow pays back every time you reuse it, and the payoff compounds across sessions and machines.
I built the homepage for this blog over a weekend. Color system, font stack, spacing, the whole thing. When I sat down to build the second page, Claude had no idea what I’d done.
I was used to WordPress, where styling applies automatically across pages. Claude doesn’t work like that. Every new session starts blank. Every new chat is a stranger who has never seen your work.
So I had a choice. Re-explain the design system every time I opened a session, on every computer, forever. Or get Claude to document its own decisions as it made them.
I picked the second one. It changed how I work with these tools.
The rule is simple. Every time Claude makes a decision that should persist, I tell it to write that decision down in a file I can feed back to it later. Color change? Update the Global Variables, then update the Global Style file. New component pattern? Add it to the style guide. New voice rule? Update the brand voice file.
I don’t have to remember anything. I don’t have to re-explain anything. I open a new session, attach the relevant files, and Claude is caught up in 10 seconds.
Three places this has paid off:
The Global Style file. When I make a visual change now, the change happens in one place and propagates. Last week I opened a session on my laptop instead of my desktop, attached the style file, and asked Claude to build a new page. It matched the existing site exactly. No back-and-forth. No “actually the heading font is…” corrections.
The brand voice file. This is a document that tells Claude how I write, what I stand for, words I use, words I don’t, the tone I want. Every piece of content I generate now references it. The output sounds like me on the first pass, not the fifth.
The wizards. A wizard, for anyone who hasn’t built one, is an interactive guide tailored to your needs that already knows your brand voice, your publishing guidelines, and your site’s objectives. You dump raw ideas in. It handles organization, structure, formatting, and alignment to your standards.
The wizard only works because the documentation already exists. The wizard isn’t doing the thinking. It’s applying the thinking I already did and wrote down.
Here’s the measurable payoff. I spent three days staring at a blank file trying to figure out how to structure my first blog post. Format, length, voice, beats. I was procrastinating because the decisions felt too big to make in one sitting.
Once I built the blog style guide and wrapped it in a wizard, I can now produce five blog posts in an afternoon. The newsletter is the same story. Building one used to mean days of formatting decisions. Now it’s 30 minutes from idea to draft.
The unlock wasn’t a better prompt. The unlock was that I stopped re-making the same decisions.
If you’re using Claude for anything that has a “house style,” whether that’s design, voice, code conventions, slide templates, or sales messaging, here’s the shift to make.
Stop treating each session as a fresh conversation. Start treating Claude like a contractor who needs a brief. Every time you correct it, every time you make a stylistic decision, every time you say “actually, do it this way,” that correction is documentation waiting to be written. Capture it.
Ask Claude to do the writing for you:
We just established [the rule / pattern / decision]. Update the [style file / voice file / context doc] so any future session can apply this without me re-explaining it. Write the entry in the same format as the existing entries.Then, when you have enough documentation, wrap it in a wizard. The wizard is what turns documentation from a reference doc you have to remember to use into a system that just runs.
The corporate parallel is obvious. This is why we write SOPs. This is why we have brand guidelines and style guides and onboarding decks. We document so the work doesn’t depend on the person who did it first.
Claude is the new hire who starts every Monday with no memory of last week. Treat it that way. Write the SOP. Hand it the SOP. Then get on with the work.