If it is not on disk, it does not exist

The single habit that separates a system from a good afternoon: every rule gets written to a file, never left in the chat.

6 min read

Level 0

Curious

0 XP

150 XP to ApprenticeNo streak yet0 badges0% done

Here is the failure mode that gets everyone. You spend an hour teaching Claude your style. It finally gets it. The article is great.

Then you close the window. Tomorrow you start again from zero.

Everything you taught it lived in the conversation. Conversations end. Files do not.

The durability rule

A rule agreed in chat and never written to a file does not exist. Not "is at risk". Does not exist. Treat it that way and the habit becomes automatic.

What a real system looks like

This is the folder the rest of the course is drawn from. It is a working article system that has shipped over a hundred pieces across ten clients. Nothing here is a toy.

article system

~/writing

·CLAUDE.mdthe orchestrator

▾.claude/

▾skills/

·write-non-listicle/SKILL.mdguides, how-tos

·write-listicle-best/SKILL.mdroundups

·write-listicle-alternatives/SKILL.md

·write-listicle-examples/SKILL.md

·update-article/SKILL.mdrefresh a live post

·proofread-article/SKILL.md5 passes

·seo-finalize/SKILL.md

▾agents/

·article-researcher.md

·screenshot-capturer.md

▾references/

·styling.mdthe anti-slop list

·research-library.mdevery stat, and where it was used

·tools-index.mdevery tool we verified

·system-audit.pychecks the rules agree

·article-check.pychecks the draft

▾Clients/

▾<client>/_system/

·knowledge-base.mdwhat they sell, verified

·style-overrides.mdonly real differences

·competitors.md

One orchestrator, seven skills, two subagents, five reference files, one folder per client. Every rule has exactly one home.

Why the split matters

You could put all of this in one giant file. People try. It falls apart for a boring reason: the file gets too long to read, so nobody reads it, so rules get added twice and start to disagree.

The split gives every rule one home:

Kind of rule	Where it lives	Example
Applies to everything	`CLAUDE.md`	No em dashes anywhere
How prose should sound	`references/styling.md`	Delete "delve", "crucial", "seamless"
One kind of article	that type's `SKILL.md`	Roundups need a comparison table
One client only	`Clients/<name>/_system/`	This client never says "we"

When you are not sure where a rule goes, ask how many things it applies to. That answers it.

What went wrong2026-07-17

The rule that was only half written down

The system moved from three proofreading passes to five. The change went into the main file. But the proofreading skill still had the old count spelled out in words further down, and a search for the number "3" missed it completely. For a while the system was telling itself two different things about how many checks to run.

Cost: Two articles proofread to the old standard before anyone noticed.

The rule that came out of it. After changing a rule, search for the spelled-out version too. Then open the file and look at it. A change you have not seen on disk is a change you have not made.

Challenge

Where does the rule go?

30 XP+8 perfect

A client tells you their brand name must never appear in the first paragraph. Where does that rule get written?

Pick the file.

Do this now

Make the folders. Two minutes, and it is the whole foundation.

mkdir -p .claude/skills references
touch CLAUDE.md references/styling.md

2
Open a past session and find one rule you taught Claude that is not written anywhere.
There is always at least one. Usually it is a formatting rule you have re-explained four times.
3
Paste it into CLAUDE.md as a single bullet. Then close the file and open it again to confirm it saved.
That last step sounds silly. It is the step the war story above was about.

Finished reading?

Mark it done to bank the XP and keep your streak alive. Any challenges on this page score separately, so you can come back for a perfect run later.