/ blog / tag
#claude-code
15 posts
← all postsArgus and Hephaestus: Two AI Agent Teams, One Builds, One Inspects
How I built two teams of specialized subagents in Claude Code: Hephaestus delivers software, Argus hunts bugs. Roles, coordinators, how they cooperate, and when orchestration is overkill.
Context Engineering: Why Your Agent Gets Dumber in a Long Session
Three mechanisms of context degradation (lost in the middle, instruction dilution, growing cost) and four habits that keep the token budget under control: compacting, clean starts, subagents, and pointers instead of data.
Hooks in Claude Code - the Deterministic Layer Your Agent Cannot Skip
What hooks are in Claude Code, how blocking actions with exit code 2 works, and four practical examples: blocking commits without tests, lint after every edit, a secrets guard, and session-start context.
Ultracode and Dynamic Workflows in Claude Code - what they really change for QA, architects, and development teams
What Ultracode and Dynamic Workflows in Claude Code actually are: a workflow with phases and subagents instead of a linear chat. What it changes for QA, test architects, and teams - and the cost risks involved.
The /goal command in Claude Code - a session contract that won't let the agent give up
How /goal in Claude Code enforces completion through a session-scoped Stop hook. Pros, cons, when to use it, how to phrase the condition, and why it matters for QA.
Multi-Agent Orchestration - When One Agent Is Enough
Level 10 on the Holak Scale is attractive for a CV, expensive to maintain. A skeptical take on agent teams: when you actually need many, when one well-configured agent wins, and how to spot orchestrating mediocrity.
MCP, CLI or hook - which tool when, and when MCP is overengineering
MCP is a tool, not a status. Each connector is maintenance, risk and attack surface. Criteria for when MCP pays off, when CLI / slash command / hook is better, a decision tree, and the CLI → MCP migration path.
AGENTS.md vs CLAUDE.md vs .cursorrules - Which Context File for What
Three context-file formats for AI agents aren't chaos - each has a niche. What each agent reads, what to put in each, how to keep them in sync, and what not to copy 1:1.
Claude and Codex: CLI vs Desktop vs Web - Where You Actually Ship Work
Three access channels to the same models differ in what they can touch. A practical comparison of Claude Code and Codex CLI against desktop apps and web interfaces.
Writing your own Claude Code subagent: frontmatter, prompt, deployment
Part two of the subagent series. We build a blog-post-writer agent from scratch - what to put in the frontmatter, how to write a description that actually triggers, and how to dodge two classic traps.
Advisor in Claude Code: a second opinion from a stronger model before you commit to a path
The advisor() tool forwards the full transcript to a stronger model and returns an opinion. When to call it before work, when NOT for every step, how not to turn it into endless consultation.
The prompt-master skill in Claude Code: a prompt generator for other AI tools
Instead of writing prompts to Midjourney, Sora, Suno or Cursor by hand, you have a Claude Code skill that does it. How it works, where it won't replace knowing the target tool.
Subagents in Claude Code: why orchestrate instead of writing in one window
One Claude vs many specialists invoked through Agent. Why subagents, how Claude picks which one to use, when NOT to use them, and why this isn't 'one window with more context'.
Context7 - the MCP that gives your model up-to-date docs instead of six-month-old knowledge
How one small MCP solves the biggest pain of working with LLMs on code: stale library knowledge. Setup, real-world cases, limitations.
Caveman - the plugin that cuts output tokens by 75% (and where it breaks)
How a Claude Code plugin that makes the model talk like a caveman changed my token bill - and which tasks it actually fits, which ones it quietly ruins.