How to structure a project's files.

The order, the cap, the categories, the naming, the refresh schedule. This card is the SKELETON. Resource 04 is the CONTENT rules. Use them together.

The upload order · first in

about-me.md / founder profile

The WHO. Always first.

Voice file

The HOW IT SOUNDS. Voice as a file, not a vibe.

2–3 GOLD samples

Your best work only. The model treats your examples as the bar. Upload mid work, get mid work back.

One offer / product doc

The WHAT.

One distilled knowledge file

Testimonials, FAQs, objections — only if the project's job needs it.

The cap3–5 files for v1. Earn additions through use, not anxiety. And stay under ~12 files total — that's the line where Claude stops reading everything and starts searching (see Resource 04).

Categorize like a database

Name files for what the SEARCH needs to find. If you can't say which category a file belongs to, it doesn't belong in the project.

Named for search

brand-voice.md · offers-current.md · gold-samples.md · testimonials-distilled.md · objections-pricing.md

Invisible to search

notes.md · doc1.md · stuff.md · final-FINAL-v2.md · untitled.md

The refresh cadence

File type	Refresh when
Voice / founder profile	Quarterly, or after any positioning shift
Offers + pricing	THE DAY they change. Non-negotiable — stale pricing is a liability.
Gold samples	When you produce something better. Swap, don't stack.
Distilled knowledge	Monthly — feed it the new distillations
Project instructions	Monthly review — same calendar slot as your Instructions for Claude review

The universal ruleRefresh on the FIRST of the month, or the first time an output feels off — whichever comes first. Drift in the output is a stale file waving at you.

Size is not the goal. Retrieval is the goal. A clean 5-file project beats a 30-file junk drawer every time.