# CLAUDE.md

*This is "the Script": the doc Claude reads first, every session. The file stays named CLAUDE.md (that is the filename Claude Code loads); we call it the Script in the workshop. Keep it thin: who you are, how you work, where things live. Detail goes in the folders, not here.*

## Who I am
I run paid creative for direct-response brands. My work is hooks, ad copy, statics, and the strategy underneath. Replace this line with your own niche and role. (Edit it directly. Once the /vault-setup skill is installed, it will interview you and fill this in for you.)

## How I work
- Show me an example before writing. I work from swipes and past winners, not blank prompts.
- Hook first. Body copy only after the hook survives a stress test.
- For anything client-facing: decide the shape, build it, then check it. For throwaways, fast and loose is fine.
- When a move works twice, we promote it into memory. When something breaks, we fix the rule, not just today's output.
- Use my voice and my swipes, not the model's average.

## Where my stuff lives (open when relevant)
Reference (feeds the work):
- Memory map: memory-map.md
- Concept notes: concepts/
- Voice rules: brand/voice.md
- Swipes to model, by mechanism: swipes/
- What worked and why: winners/
- What died and why: losers/
- Repeatable plays: workflows/
- A specific client's context and rules: clients/{name}.md
- Human-readable skill guide: skills/Skills.md

Production (what I make):
- Written work (hooks, headlines, long-form): copy/
- Visual work (statics, video): creatives/

Flow:
- Unsorted drop zone: inbox/
- Daily notes: daily/
- Finished or retired work: archive/

What to promote into memory vs ignore: the-data-dictionary.md (read it; it is the rule for what compounds).
When creating a durable note, include a short `Related:` line with useful Obsidian links, for example `Related: [[Promotion]] [[Workbench vs Memory]]`.
The real Claude Code skill instructions live in `.claude/skills/`. Obsidian hides dot folders, so use `skills/Skills.md` when you want to see the skill map.

## Rules that bite
- Never invent a client result, number, or quote. If it is not in the client file, ask me.
- If you are unsure what good looks like, ask for an example before guessing.
- SAVE work into copy/ or creatives/. PROMOTE the lesson (why it won or died) into winners/, losers/, brand/, or workflows/. Two moves, not one. Never delete from archive/.
- At the end of a session, ask me what is worth promoting into memory and where it goes. That is how the workspace compounds.
