Less prompting.
More shipping.
Sharp guides, reusable workflows, and small tools for people doing serious work with Claude and Claude Code.
╭────────────────────────────────────────────────────────╮
│ ✦ Claude Code Field Manual // issue 001
╰────────────────────────────────────────────────────────╯
❯ Map this codebase and tell me what matters.
⏺ Reading architecture and project conventions…
⏺ Found 3 leverage points and 1 risky assumption.
✓ Context mapped. Ready to plan.
❯
// OUR THESIS
Claude is most useful when the conversation becomes a working system—with context, constraints, tools, and a definition of done.
// LATEST FIELD NOTES
Notes from the workbench.
The context file that actually survives a real codebase
A field-tested CLAUDE.md structure: commands, boundaries, architecture, and the few instructions worth keeping.
Plan mode is not ceremony. It is leverage.
Turn vague work into inspectable decisions before the first file changes. A practical loop for high-trust coding sessions.
Give the model a job, not a vibe
Prompt patterns for research, writing, and analysis that produce useful artifacts instead of agreeable fog.
// THE WORKFLOW
A better conversation
starts with a better loop.
Three repeatable moves for turning Claude Code into a calm, inspectable engineering partner.
Open the field manual/mapUnderstand an unfamiliar repository
/planTurn intent into a reviewable approach
/shipBuild, verify, and leave a clean handoff
Get the useful part.
Skip the noise.
One practical Claude workflow at a time. Early members shape the tools and field notes we build next.
newsletter.init()
C_ M_ K_ Join the founding readers.