Author disclosure upfront: I wrote this. It’s free, MIT-licensed, no paid tier, no signup, no email gate. Source: https://github.com/the-good-pixel/learn-agentic-working Spent the last year using Claude Code daily across pretty much every kind of work — feature development, cross-repo bug hunts, CI babysitting, but also reconciling Stripe payouts, drafting PRDs from meeting notes, weekly Google Ads reviews, and a Playwright + Remotion demo-video pipeline. Wrote down what worked and what didn’t. Site: https://the-good-pixel.github.io/learn-agentic-working/ Things in it that might be relevant here specifically: Architecture model the book leans on: You → Orchestrator → Model → Connector → Real app . The orchestrator (Claude Code) is what you actually type into; it consults the model and dispatches tool calls. Most beginner material treats the model as the front door, which sets the wrong mental model. Chapter on skills (what they are, when to write one, how to write one from a conversation rather than authoring by hand). Chapter on parallel worktrees / sub-agents and when they’re worth the setup cost. Chapter on ship-pr style workflows — pushing → CI → AI-review-comment iteration → mergeable. Tool-neutral: every chapter cites Codex / OpenCode / Cursor / Gemini CLI equivalents alongside Claude Code. Most curious to hear: Does the “You → Orchestrator → Model → Connector” mental model resonate, or does it miss something? For people running parallel Claude Code worktrees on one machine — what did you wish someone had told you on day one? (Asking because Ch. 16 covers this and I want to know what’s missing.) Honest critique > stars. submitted by /u/True_Butterscotch611
Originally posted by u/True_Butterscotch611 on r/ClaudeCode