Tag: Claude Code
All the articles with the tag "Claude Code".
-
Stop Re-Introducing Your Project to AI Every Session: A Project Passport with AGENTS.md, CLAUDE.md, and memory
AGENTS.md is the de facto standard in 2026, CLAUDE.md is still Claude Code's richer format, and project memory holds a different class of information altogether. Stitch them into a "Project Passport" so every new session begins with the AI clearing customs in seconds instead of asking you to paste context again.
-
Loop Engineering: From Writing Prompts to Designing Loops That Run Agents for You
The "Loop Engineering" term Addy Osmani popularized in June isn't a replacement for prompt engineering — it's about swapping you out as "the person who hits enter" and turning you into "the person who designs the loop". Walks through the five components plus a state, and the three debts Osmani is really worth remembering for (verification debt / comprehension debt / cognitive surrender) — and along the way, why I disagree with him placing loop above the harness.
-
Two Days with Claude Fable 5: The 5 Things Every API Integrator Actually Has to Change
Anthropic shipped Fable 5 on 6/9, swapping the Opus/Sonnet/Haiku naming for Fable/Mythos. But the things that actually force every Claude API integrator to touch code aren't the names — they're the new stop_reason refusal, the forced adaptive thinking, and the "you must wire up a fallback model" architecture. After two days driving it inside Claude Code, here's the integration-side detail you need.
-
Prompt, Context, Harness, Agentic: The Four Nested Layers of LLM Apps — and Knowing Which One You're Stuck In
Prompt engineer, context engineer, harness engineer, agentic engineer — these aren't four competing job titles. They're nested layers of concern, from a single instruction to an entire autonomous system. Understand how the four layers relate, and you'll know exactly which one you're optimizing every time you get stuck.
-
Letting Claude Code Touch My Real-Money Trading Code: The Lines I Refused to Cross
I've spent 10 months using Claude Code on a real-money futures trading project. This is an honest retrospective: the AI never touched the money directly (I'm not that bold), but it did write code on the critical order/stop-loss/close-position paths. Here are the boundaries I held, where AI genuinely helped, and the moments I had to take over.
-
7 "Anti-AI-Tone" Principles I Distilled After Writing 80+ Blog Posts with Claude Code
Roughly 70% of posts blog080-166 on this blog were written with Claude Code's help, yet readers almost never notice. Here are the 7 "anti-AI-tone" principles I distilled — the goal isn't to make AI sound less like AI, it's to make AI sound like you. Includes the automated check script from my blog-preflight Skill.
-
Claude Code Multi-Agent Orchestration Plugins Compared 2026: Choosing Between Ruflo, Maestro, Claude Octopus, and Codex Peer Review
A head-to-head comparison of multi-agent orchestration plugins: Ruflo calls itself the "leading Claude orchestration platform" but underdelivers in execution, Maestro stays lightweight, Claude Octopus runs reviews across 8 models in parallel, and Codex Peer Review gates merges behind three sequential reviewers. From architecture to measured token costs — a decision framework for indie developers.
-
Claude Code Workflow Plugins Compared (2026): Superpowers, Shipyard, Ralph Loop, Maestro, or Karpathy CLAUDE.md?
The Claude Code ecosystem has splintered into 100+ plugins as of May. This post zooms in on the "workflow methodology" category—Superpowers, Shipyard, Ralph Loop, Maestro, and Karpathy CLAUDE.md. Design philosophy, context overhead, fit, and combination strategies, plus a decision tree for indie developers.