Curated topic · 13 ARTICLES
Explore practical Claude Code articles grounded in clear explanations and engineering tradeoffs.
Latest articles
Claude Code permissions use allow, ask, and deny rules, evaluated with deny first. This article covers /permissions, Bash wildcard syntax, Shift+Tab mode cycling, and settings-file precedence.
Read articleClaude Code plan mode requires approval of a plan before changing code. This covers enabling it with Shift+Tab or /plan, the three approval options, editing plans with Ctrl+G, and setting defaults.
Read articleThe Claude Code /init command analyzes your codebase and automatically generates CLAUDE.md. This covers its behavior when a file already exists, migrating Cursor and Copilot rules, interactive mode, and how to refine the generated file.
Read articleVibe Coding mishaps are decided when you write the first rule file, not when you read the code. Here are five rules for CLAUDE.md and .cursorrules covering security, duplication, architecture, completion criteria, and scope, with example wording.
Read articleA harness is the execution loop wrapped around a model. We cover its components—tools, permissions, context management, and feedback—the reason agent performance is determined by the product of model intelligence and harness quality, and what makes a good harness.
Read articleWhen using AI coding tools, you often repeat the same instructions: “Use this format for commit messages” or “Follow this checklist before deployment.”
Read articleIn earlier installments, we explored ways to conserve context: clear history at each work boundary (Part 3) and keep fixed overhead short (Part 4). Yet some tasks remain too large to handle. A typical example is, “Figure out how payment logic flows through this codebase.” A diligent agent would read dozens of files, and as we saw in Part 1, everything it reads accumulates in context. By the time the investigation is complete, no context remains for the actual work that knowledge enables—changing the code.
Read articleIn Part 3, we saw how to clear conversation history with /clear. But checking the remaining context immediately afterward shows it is not at 100%. Run /context in Claude Code and the reason becomes clear: the system prompt, tool definitions, CLAUDE.md, and tools registered by MCP servers already consume tens of thousands of tokens…
Read articleThe previous two posts completed the diagnosis. The context window is finite (Part 1), and filling it does not mean everything is used; performance actually declines as it grows (Part 2). The prescription is clear: manage context. Coding agents, including Claude Code, provide /clear and /compact for this purpose…
Read articleThere are more ways than ever to extend AI coding tools: connect tools with MCP, register procedures with Skills, and delegate work to subagents.
Read articleWhen using Claude Code in a project, two needs arise: “Always follow this rule” and “Remember what we discovered last time.”
Read articleOne of the questions developers ask most often in communities these days is, "Which should I use, Claude Code or Codex?" I’ve paid for Claude for about a year and Codex for more than six months, using both every day, including the recently released Claude Fable 5 and GPT-5.6 Sol…
Read articleThis is probably the question that comes up most often in developer communities these days: "Which one should I actually use—Claude Code, Cursor, or Copilot?"
Read article