01
CLAUDE CODE: PARTNER
AI-native development.
Not AI-assisted.
Partnership, not delegation.
02
The Partnership Model
Not "using AI" — partnering with AI.
- You bring: intent, judgment, domain knowledge
- Claude brings: execution, pattern recognition, tirelessness
- Together: systems that neither could build alone
The goal isn't to replace you. It's to amplify you.
03
"The best for the most for the least."— Charles and Ray Eames
04
┌─────────────────────────────────────────────────────────────────────────┐ │ │ │ WHAT CLAUDE CODE HAS ACCESS TO │ │ Philosophy baked into context │ │ │ │ ┌──────────────────┬──────────────────────────────────────────────┐ │ │ │ CLAUDE.md │ Project philosophy, conventions, patterns │ │ │ ├──────────────────┼──────────────────────────────────────────────┤ │ │ │ .claude/rules/ │ Domain-specific patterns and constraints │ │ │ ├──────────────────┼──────────────────────────────────────────────┤ │ │ │ MCP Servers │ Cloudflare, Beads, filesystem, browser │ │ │ ├──────────────────┼──────────────────────────────────────────────┤ │ │ │ Hooks │ Pre-commit, post-edit, validation │ │ │ ├──────────────────┼──────────────────────────────────────────────┤ │ │ │ Skills │ /audit-canon, /deploy, /harness-spec │ │ │ └──────────────────┴──────────────────────────────────────────────┘ │ │ │ │ Claude doesn't just execute. It understands the philosophy. │ │ │ └─────────────────────────────────────────────────────────────────────────┘
Context is everything. Philosophy shapes execution.
05
CLAUDE.md
Philosophy baked into context.
- The Subtractive Triad (DRY → Rams → Heidegger)
- The Hermeneutic Circle (.ltd → .io → .space → .agency)
- Code Mode preferences (when to use tools vs code)
- Domain commands and conventions
Claude reads this before every session. It becomes the shared language.
06
CLAUDE.md Structure
# CREATE SOMETHING Monorepo
## Philosophy: The Subtractive Triad
| Level | Discipline | Question | Action |
|----------------|------------|-----------------|-----------|
| Implementation | DRY | Built before? | Unify |
| Artifact | Rams | Earns place? | Remove |
| System | Heidegger | Serves whole? | Reconnect |
## Architecture
packages/
space/ → createsomething.space (Practice)
io/ → createsomething.io (Research)
agency/ → createsomething.agency (Services)
ltd/ → createsomething.ltd (Philosophy)This file is the contract between you and Claude.
07
.claude/rules/
Breakdowns become patterns.
cloudflare-patterns.md— D1, KV, Workers, Pagescss-canon.md— Tailwind for structure, Canon for aestheticsbeads-patterns.md— Task tracking across sessionssveltekit-conventions.md— Route and component patterns
Every breakdown you repair becomes a rule Claude follows.
08
Rules Example: css-canon.md
# CSS Canon
**Principle**: Tailwind for structure, Canon for aesthetics.
## Layout Utilities (Keep)
flex, grid, items-*, justify-*, p-*, m-*, gap-*
## Design Utilities (Avoid) → Use Canon
| Tailwind | Canon Token |
|--------------|--------------------------|
| rounded-md | var(--radius-md) |
| bg-white/10 | var(--color-bg-surface) |
| text-white/60| var(--color-fg-tertiary) |
## Token Reference
--space-md: 1.618rem /* Golden ratio */
--duration-micro: 200msClaude applies these rules automatically.
09
┌─────────────────────────────────────────────────────────────────────────┐ │ │ │ MCP SERVERS │ │ Direct access to infrastructure │ │ │ │ ┌──────────────────┬──────────────────────────────────────────────┐ │ │ │ Cloudflare │ D1 queries, KV operations, R2 storage │ │ │ │ │ Workers deployment, Pages deployment │ │ │ ├──────────────────┼──────────────────────────────────────────────┤ │ │ │ Beads │ bd create, bd ready, bd close, bd sync │ │ │ ├──────────────────┼──────────────────────────────────────────────┤ │ │ │ Filesystem │ Read, Write, Edit, Glob, Grep │ │ │ ├──────────────────┼──────────────────────────────────────────────┤ │ │ │ Browser │ WebFetch, WebSearch │ │ │ └──────────────────┴──────────────────────────────────────────────┘ │ │ │ │ Claude doesn't shell out. It calls APIs directly. │ │ │ └─────────────────────────────────────────────────────────────────────────┘
Infrastructure access without infrastructure commands.
10
Hooks
Automatic validation at key moments.
- Pre-commit: Type checking, linting, tests
- Post-edit: Format, validate, sync
- Session start: Prime context, check Beads
Hooks run automatically. You don't think about them.
11
Hooks Example
# .claude/settings.json
{
"hooks": {
"PreToolUse": [
{
"matcher": "Write|Edit",
"hooks": ["pnpm exec tsc --noEmit"]
}
],
"PostToolUse": [
{
"matcher": "Write|Edit",
"hooks": ["bd sync"]
}
]
}
}Validation happens automatically. The tool recedes.
12
Skills
Reusable workflows invoked by name.
/audit-canon— Check CSS for Canon compliance/deploy— Generate deployment commands/harness-spec— Create harness specification/audit-voice— Check content for Voice compliance
Complex workflows become simple commands.
13
┌─────────────────────────────────────────────────────────────────────────┐ │ │ │ PLUGINS │ │ Install philosophy into your Claude Code │ │ │ │ ┌──────────────────┬──────────────────────────────────────────────┐ │ │ │ Canon │ Design system enforcement │ │ │ │ │ DRY → Rams → Heidegger in every review │ │ │ ├──────────────────┼──────────────────────────────────────────────┤ │ │ │ Hermeneutic │ Code review through Subtractive Triad │ │ │ │ Review │ Three-pass methodology │ │ │ ├──────────────────┼──────────────────────────────────────────────┤ │ │ │ Voice Validator │ Content against Five Principles │ │ │ │ │ Clarity, Specificity, Honesty, Useful │ │ │ ├──────────────────┼──────────────────────────────────────────────┤ │ │ │ Understanding │ UNDERSTANDING.md files │ │ │ │ Graphs │ Minimal dependency graphs for navigation │ │ │ └──────────────────┴──────────────────────────────────────────────┘ │ │ │ │ → createsomething.io/plugins │ │ │ └─────────────────────────────────────────────────────────────────────────┘
Philosophy made executable. Install in one command.
14
┌─────────────────────────────────────────────────────────────────────────┐ │ │ │ THE DEVELOPMENT LOOP │ │ │ │ ┌─────────┐ │ │ │ READ │ │ │ │ context │ │ │ └────┬────┘ │ │ │ │ │ ▼ │ │ ┌─────────┐ ┌─────────┐ ┌─────────┐ │ │ │ REPAIR │◀────────│ PLAN │────────▶│ EXECUTE │ │ │ │ patterns│ │approach │ │ changes │ │ │ └────┬────┘ └─────────┘ └────┬────┘ │ │ │ │ │ │ │ ┌─────────┐ │ │ │ └─────────────▶│ VERIFY │◀─────────────┘ │ │ │ results │ │ │ └─────────┘ │ │ │ │ Breakdowns loop back to REPAIR. Patterns feed future READs. │ │ │ └─────────────────────────────────────────────────────────────────────────┘
Read → Plan → Execute → Verify → Repair
15
Zuhandenheit in Practice
When Claude Code works, it disappears.
- You think about the feature, not the prompts
- You think about the architecture, not the syntax
- You think about the user, not the deployment
The partner recedes. The work remains.
16
Installation
# 1. Clone the monorepo
git clone [email protected]:createsomethingtoday/create-something-monorepo.git
# 2. Install dependencies
pnpm install
# 3. Generate Cloudflare types
pnpm --filter=space exec wrangler types
# 4. Start development
pnpm dev --filter=space
# Claude Code reads CLAUDE.md automatically.
# Rules apply. MCP servers connect. Hooks run.
# The partnership begins.Install once. Partner indefinitely.