Technical
Claude Code in a Team of One: Workflows That Survived Four Months
Solo consultants live and die by their workflows. I am one person delivering backend APIs, frontend sites, and WordPress handoffs for multiple clients simultaneously. Four months in, Claude Code has become my second brain. Here is what actually works day to day.
The Morning Context Load
I start every client session by pointing Claude Code at the project's CLAUDE.md file. That single file encodes the conventions, the stack, the client name abstraction rules, and the deployment targets. Without it, every session starts from zero and I waste 20 minutes reorienting the agent.
The rule I follow: if I explain something twice to Claude in one week, it belongs in CLAUDE.md. This is the discipline that turns a fresh agent into a senior teammate in three turns.
The Commit-Before-Deploy Rule
I never deploy uncommitted Claude-generated code. Ever. The rule exists because Claude gets 95 percent of things right and 5 percent spectacularly wrong, and you cannot tell which is which without a diff to review. Every deploy starts with a clean git status.
# My actual daily workflow
git status # clean?
claude # start session
# ... work ...
git diff # review
git add -p # stage selectively
git commit -m 'feat: ...' # commit
vercel --prod # now deployWhat I Stopped Doing
I stopped asking Claude to write tests after the fact. It generates tests that pass, not tests that catch bugs. Now I write the test signature myself, then let Claude fill in the body. That small shift doubled the value of my test suite.
I also stopped running long autonomous sessions. Claude is better as a collaborator than as an autonomous worker. Thirty-minute focused sessions with clear acceptance criteria beat three-hour free-form sessions every time.
The tool has matured and so has my use of it. See the Claude Code best practices for the official patterns, but the ones above are earned from shipping real code.
RELATED READING
The Consulting Shift I Am Making In Year Two
After a year of writing and building, my consulting practice is changing shape. Shorter engagements. Sharper outcomes.
ReadThe Frontend Shift: Shipping Less JavaScript In Year Two
A year ago I reached for Next.js for everything. This year I often reach for nothing.
ReadThe Serverless Lesson I Would Write On A Sticky Note
After a year of shipping serverless projects, one rule explains most of the wins and all of the losses.
Read