Claude Code Workflow
The Problem
Every new Claude session starts from zero. You explain the project, re-establish conventions, repeat corrections you already gave. It's like onboarding a new developer every hour.
The System
A set of conventions, templates, and decision frameworks that sit on top of Claude Code's native features rather than reinventing them:
- CLAUDE.md — Project architecture, conventions, and learned rules. Auto-loaded every session.
- soul.md — Communication style and working preferences. How Claude should talk and think.
- Skills/ — Decision frameworks (should I build this? ship or iterate? MVP ready?) that auto-trigger from their
description frontmatter — you state intent, the right framework fires.
- Knowledge/ — Technical learnings from past sessions (Cloudflare runtime choices, payment integration notes).
- settings.json (Hooks) — Guardrails that run inside the session: inject the last handover on start, block a force-push, nudge a rule-capture on stop.
- MEMORY.md — An index for Claude Code's native file-based memory: the durable facts that survive across sessions.
- DASHBOARD.md / HANDOVER.md — Cross-project priorities, and the per-session baton (read it, overwrite it, hand off — never delete the only copy).
How It Works
Each session opens already knowing where the last one left off (a SessionStart hook injects HANDOVER.md), picks up the next step, and writes corrections back as learned rules. Mistakes don't repeat. Context compounds.
The "Learned Rules" pattern is the key: every time Claude gets corrected, it writes the trigger, correct behavior, and date into CLAUDE.md. Next session, that rule is loaded automatically. Standing facts graduate to native Memory so they're recalled even without reading the file.
Results
Battle-tested across 12+ projects — AI memorial platforms, podcast pipelines, trading dashboards, payment integrations. The same system scales from a weekend hack to a multi-month production app.
It's open source and kept current: I re-audit it against Claude Code on a cadence (a fast-moving CLI breaks assumptions in weeks, not years) and log every change in the CHANGELOG.
View the repo on GitHub · View the full presentation