Tag: claude-code
All the articles with the tag "claude-code".
-
A Reusable Kit for Solo Development — CLAUDE.md Constitution File + 2-Agent Workflow
Solo development has no reviewer, PM, or QA. This setup encodes those roles into (1) a CLAUDE.md constitution file and (2) two sub-agents — code-writer and code-reviewer — so the machine enforces discipline. Pulled from a recent project's refined setup, keeping only the parts portable to other projects — a CLAUDE.md skeleton, a 6-step 2-agent workflow with 3 operating modes (review-only / finalize / review-and-finalize), agent prompt templates, and a project-agnostic checklist of working principles. Permission scope is deliberately split (writer has no git, reviewer has no Write) so every commit always passes through a review gate. You can drop this into a new project in 5 minutes.
-
The Day Claude Code Suddenly Stopped Working — the 529 Overloaded Error and the Existence of status.claude.com
I turned on Claude Code in the morning as usual, but agent calls kept failing with a 'server overloaded' error. A short troubleshooting log tracking down the cause through API Docs, a developer group chat, and status.claude.com — turned out to be a temporary overload on Anthropic's server side.
-
Managing AI Sessions in Vibe Coding — How to Split Common vs. Specialized Instructions
A problem I ran into managing multiple Claude Code sessions like company departments: instruction management. I worked out how much should live in the common CLAUDE.md, and where the line is for splitting off specialized CLAUDE.md files in each working folder.
-
When department-specific Claude Code sessions don't follow instructions — putting CLAUDE.md in the actual working folder
While running multiple Claude Code sessions split by role in one project, the frontend session kept using git commands. Moving the instructions from the 'department folder' to the 'actual working folder' fixed it.