Personal · Meta — structuring the Claude system
Claude setup: documentation, onboarding and Knowledge Hub
Context
I needed to document the logic of the Claude setup (.md files, projects, two accounts) for two reasons: hand the system off to a friend just getting started (Romain / Ballard), and give myself a centralized journal to build on session after session.
What was built
- Full explanation of the file system:
CLAUDE.md,CLAUDE-strat.md,CLAUDE-dev.md,histoire_cobra.md,claude-cobra-odoo.md - Distinction between Claude Chat vs Claude Code and when to use each
- Conditional extension-loading logic
- Complete email for Romain (Ballard): explanation of the system + a ready-to-use prompt for his
CLAUDE.mdand his company DNA file - 3 reusable prompts (session summary, onboarding a new Claude, context extraction)
- Full brief for Claude Code to build this repo
What was tricky
- The "automatic sync" Claude ↔ GitHub isn't natively feasible — the semi-manual solution (summary → copy-paste → git push) is more than enough
- The public/private distinction on GitHub Pages isn't real auth — "unlisted" is assumed, fine for non-sensitive
.mdfiles
Stack
Markdown, GitHub Pages, static HTML/CSS — a structuring and documentation session.
What this illustrates
Claude used as a meta-tool — not to produce code, but to document a practice, pass it on, and lay the foundations for a system that improves over time. Compound Engineering applied to itself.