Setting up a new Mac for Claude Code work, end-to-end
From unboxed Mac to first Claude Code session in 90 minutes. Every step, every command, every config — the complete walkthrough.
22 posts
From unboxed Mac to first Claude Code session in 90 minutes. Every step, every command, every config — the complete walkthrough.
Sometimes an agent goes way past scope and modifies things it shouldn't have. Here's the rollback playbook — git-based, fast, low-stress.
Claude Code's memory feature is powerful but easy to misuse. The pattern that scales — what to put in global memory, what to put per-project, what to never persist.
AI agents produce diffs that look right and are subtly wrong. Here's the structured review checklist that catches the drift before it ships.
When an AI agent has access to your whole repo, it doesn't read your whole repo. Here's how to choose what enters context, what stays out, and how that decision affects output quality.
AI agents fail in specific ways. The right debugging response depends on the failure mode. Here's the structured protocol that catches drift fast.
Five parallel agents produce a lot of output. The trick is summarizing what mattered without reading every commit. Here's the daily routine.
cmux turns one terminal window into a tile of independent agent sessions. Here's how to wire it up, name your sessions, and integrate it with a file manager so context never gets lost.
Prompt engineering peaked. Context engineering — what's in the agent's working memory, what's not — is the 2026 leverage point. Here's the practical playbook.
Naming AI sessions feels trivial until you have 50 of them. The convention that scales — and the patterns that break.
Both tools edit files. They have very different opinions about which files, how many at once, and where their working memory lives. Here's the honest comparison from someone who runs both daily.
Every new AI project needs the same handful of bootstrap files. Skipping them costs an hour each session. Here are the seven templates that pay back immediately.
Three AI coding tools that overlap on the surface but optimize for different workflows. Here's the decision tree for picking the right one per task.
Claude skills are reusable agent capabilities. They're powerful — but writing one for the wrong workflow is wasted effort. Here's the practical guide.
Inheriting code is easier with an LLM if you ask the right questions in the right order. The 4-step process that surfaces the architecture in under an hour.
Three different ways to keep parallel AI agents from stepping on each other. Each has a place; getting the choice right per task saves real conflicts.
Aider and Claude Code both do agent-style coding from a terminal. They diverge on git workflow, model flexibility, and edit precision. The honest comparison for refactor work.
CLAUDE.md is the most-undervalued AI productivity tool. A good one saves hours per week; a generic one is dead weight. Here's what makes the difference.
Stop pasting the same instructions into every chat. Here's a battle-tested layout for a personal prompt library that you can grep, version-control, and share between Claude Code, Cursor, and Codex.
Model Context Protocol matured in 2025-2026. Here are the seven MCP servers that earn their setup cost for AI dev workflows.
Running five Claude Code sessions on one Mac without losing track is a workflow problem, not an AI problem. Here's the layout that survives daily use.
A directory layout, naming convention, and pane-routing strategy for running multiple Claude Code sessions on macOS without losing your place.