/
FIELD MANUAL · 36 HACKS
★ Saved 0
A working guide for power users

Thirty‑six ways to bend Claude Code to your will.

From the very first /init to running fleets of agents on a remote VPS — a curated field guide of thirty‑six practical hacks, organized from beginner to power user. Filter by level, search the lot, bookmark the keepers.

36×
Hacks · ranked & explained
3↗
Skill levels · beginner → power
11/
Slash commands covered
∞⚡
Hours of trial & error saved
I.
Foundations · 01 → 10

Setup, context, and a habit of asking better questions.

Hacks 10
Read time ~6 min
II.
Workflows · 11 → 22

Parallelism, custom skills, and feedback loops that actually close.

Hacks 12
Read time ~9 min
III.
Power · 23 → 36

Always‑on agents, fleet orchestration, thinking at scale.

Hacks 14
Read time ~11 min
Five takeaways

The whole manual, distilled into five ideas.

01 / Context

Context is the whole game.

Most quality and cost wins come from feeding the model less, not more. Compact at 60%, route via CLAUDE.md, and clear between unrelated tasks.

02 / Reasoning

Plan, ask, then act.

Plan mode, the ask‑user tool, and ultra‑think turn one‑shots into deliberate work. Make Claude reach ~95% confidence before it writes a line.

03 / Parallelism

Run things side‑by‑side.

Sub‑agents, agent teams, and Git work trees let you split exploration, research, and execution into parallel lanes that don't collide.

04 / Memory

CLAUDE.md is the project's brain.

Treat it like a living document. Refresh it with every lesson learned, route deeper docs from it, keep it under ~200 lines.

05 / Reach

Push past the editor.

Screenshots, Chrome DevTools, headless CI runs, CLI data tools, VPS hosting, phone control — Claude Code becomes a build/test/deploy/monitor partner, not just a code assistant.