CLAUDE.md
Stop explaining your business every time
If you keep repeating your audience, writing preferences, and folder rules, put those essentials in CLAUDE.md. Claude Code loads this instruction file when you work in that project.
Markdown (.md) is plain text with simple formatting, so you can edit it in Obsidian.
Copy this starting example
This example is for a marketing workspace. Adapt the business description and paths to your own files.
# Business
We help service businesses implement AI marketing workflows.
Our content should lead relevant prospects toward an implementation call.
# Sources
Before writing, read notes/current-offer.md and notes/audience.md.
Use notes/customer-evidence.md for supported examples and claims.
If a required source is missing, ask instead of inventing details.
# Writing
Keep explanations short, concrete, and useful.
Use one practical example per concept.
Never invent results, testimonials, or pricing.
# Output
Save each campaign under campaigns/<topic>/.
Keep research and drafts with that campaign.
# Review
Check claims against sources and verify links.
Show the finished draft before sending or publishing.
The source paths above are examples. Replace them with files that actually exist in your workspace.
Where to save it
Save a file named exactly CLAUDE.md at the top of your marketing project. If you run Claude Code from your Obsidian vault, that can be the vault root.
Open Claude Code in that folder. Run /context and check Memory files to confirm it loaded.
This guide, 04-claude-md.md, is a reference chapter. Its filename does not make it an active instruction file. Official setup guide.
Give each thing one home
| Keep in | What belongs there |
|---|---|
| CLAUDE.md | Short standing rules and pointers to sources |
| Obsidian notes | Offer details, audience research, examples |
| Skills | Procedures such as writing a lead magnet |
| Connected apps | Current tasks, contacts, and campaign results |
For example, maintain pricing in your offer source and tell Claude to read it. Copying prices into several instruction files creates conflicting versions.
Your first check
Start a fresh session and ask Claude to identify the offer source, output folder, and publishing rule. Then try one small draft.
When the same correction repeats, improve the relevant instruction. Keep the file short. Instructions guide behavior; permission settings or hooks are needed for enforced restrictions.
Continue
Previous: Claude Code
Next: MCP and Connectors
Want this set up for your business?
We turn these workflows into working marketing and sales systems.