Quartz 5

Every Claude Code Hack I Know (March 2026)

Properties1
tagsclaude-code, agentic-workflow

3 min read

Summary

A practitioner’s workflow guide from a heavy Claude Code user running 4-6 parallel sessions daily, with 70 plan files and 263 commits in 30 days. The core workflow: always create plan.md before any implementation (/ce:plan), run parallel sessions for independent workstreams, use voice input (Monologue/WhisperFlow) for all prompting, and treat plan files as persistent checkpoints that survive context loss. The article covers settings, tooling choices, and real-world examples including open source contributions and a Disney World trip planner built at a soccer field.

一位每日運行 4-6 個平行 session 的重度使用者分享的工作流指南。核心循環：/ce:plan（研究+規劃）→ /ce:work（實施）→ 音頻輸入（Monologue）+ Zed 即時同步。計劃檔案是跨 session 的持久檢查點；並行 session 依賴 bypass permissions 實現自主運行。

Key Points

  • Core rule: always /ce:plan before any implementation unless it is literally a one-line change; plan.md is the checkpoint that survives context loss
  • 4-6 parallel Ghostty sessions: one planning, one implementing previous plan, one researching, one debugging — context-switch between them
  • skipDangerousModePermissionPrompt: true + defaultMode: bypassPermissions in settings.json are required for autonomous parallel sessions
  • Sound hook on Stop event (afplay /System/Library/Sounds/Blow.aiff) signals which session finished — necessary when running 4-6 at once
  • Zed autosave every 500ms + Claude watching filesystem = Google Docs-like real-time collaboration between human edits and Claude Code
  • /last30days skill searches Reddit/X/YouTube/HN/Polymarket in parallel for fresh community knowledge before planning
  • Mac Mini + tmux for remote Claude Code sessions (airplane wifi drops disconnect laptop sessions but not remote sessions)
  • Research loop: /last30days → /ce:plan (grounded in fresh community data) → /ce:work

Insights

The ratio inversion — from 80% coding / 20% planning to 80% planning / 20% coding — is the central workflow claim and matches what high-output solo developers report. The Granola (meeting transcript) → /ce:plan flow that cross-referenced the existing codebase and prior strategy files to generate a product proposal is an underappreciated pattern: meeting context + codebase context + historical strategy files produces better proposals than any of these sources alone. The Mac Mini + tmux for handling airplane connectivity is a specific but practical infrastructure insight.

Connections

Raw Excerpt

“Traditional dev is 80% coding, 20% planning. This flips it… The thinking happens in the plan. The execution is mechanical.”

Graph View