Letting Claude Code Handle Dependency Upgrades — A Verification Loop That Catches Breaking Changes
Once a solo project carries 30+ dependencies, the monthly upgrade run becomes a dreaded ritual. This article maps out where Claude Code can take the wheel, where humans must keep judgment, and the verification loop I use to keep breaking changes out of production.
Claude Code for Unity Game Development: Practical
Hands-on guide to using Claude Code on real Unity projects: writing CLAUDE.md for Unity, the Unity MCP server, scene-aware C# generation, PlayMode tests, and build verification.
Claude Code's TodoList Quality Comes Down to Task Granularity — Patterns That Actually Worked
The TodoList tool in Claude Code can backfire when used carelessly. Three field-tested patterns — task granularity, verification steps, and update timing — that shift the output from 'looks organized' to 'actually delivered'.
Fixed-Bid Pricing Engineering for Freelancers in the Claude Code Era
How to price fixed-bid engagements in the Claude Code era without bleeding profit — a three-layer cost model, risk buffers, and contract clauses that protect freelancers when generative AI compresses hours.
Three Minutes with /doctor: Catching Claude Code Config Drift Before It Costs You an Hour
When Claude Code acts up, the first thing to run is /doctor. It shows merged settings, MCP server status, and permission mode at a glance.
Write the Repro Test Before Delegating Bug Fixes to Claude Code
After watching Claude Code spin its wheels on ambiguous bug reports, I started writing the failing test myself before delegating. This post walks through the design principles, a concrete repro test, and the three-stage workflow I run in production.
Finishing Long-Running Claude Code Tasks: A Resilience Playbook You Can Ship
Multi-hour Claude Code jobs — bulk refactors, TypeScript migrations, mass test generation — always stop before they finish, and recovery is painful when you cannot tell what already ran. This guide ships concrete patterns: a checkpoint-driven manifest, a three-state circuit breaker, idempotent retry rules, and a freeze-and-resume protocol you can copy into your repo today.
Stabilizing Solo Revenue: A Customer Portfolio Playbook for Claude Code Consultants
After you have raised your rate, the next challenge is revenue volatility. A practical framework for solo Claude Code consultants to design a client portfolio that keeps monthly income predictable.
The Claude Design to Claude Code Handoff — A Production-Ready Playbook
A detailed field guide to chaining Claude Design and Claude Code into one workflow — prompt templates, cleanup commands, and the 12-point checklist I run before shipping.
Taking Over an Unfamiliar Codebase in One Week with Claude Code — A Maintenance Handover Playbook
When you inherit a codebase from someone who has already left, how do you use Claude Code to reach a state where you can confidently make changes in just seven days? This is the exact protocol I've repeated many times across solo projects and client work, complete with the prompts I use.
Keeping Claude Code Accurate Through Long Sessions: Signals of Context Decay and What to Do About Them
After a few hours in the same Claude Code session, output quality can quietly slip. This is a practical field guide to spotting the early signals, choosing where to end a session, and keeping a long workflow reliable.
The 12-Week Roadmap from Zero to a Monetized Claude Code Product
A week-by-week roadmap for indie developers starting from a single idea and reaching a product with paying users in 12 weeks, built around Claude Code. Includes the exact prompts I use and the mistakes I ran into along the way.