Leveraging Claude Code in a Structured Workflow
The author shares their workflow for using Claude Code, which involves a separation of responsibilities between a 'thinking' Claude and an 'executing' Claude, along with various automation systems to maintain context and consistency.
Why it matters
This workflow demonstrates how to effectively leverage the capabilities of Claude Code in a structured and automated manner, which can improve productivity and code quality.
Key Points
- 1Use two separate Claudes - one for analysis and prompt generation, another for code implementation
- 2Maintain comprehensive project documentation and database schema in separate files
- 3Implement logging system to capture execution details for troubleshooting
- 4Use structured XML tags in prompts to improve clarity and consistency
Details
The author has developed a workflow that leverages two separate Claude instances - one acting as a 'supervisor' (the Claude Desktop App) and another as the 'executor' (the Claude Code CLI in VS Code). The supervisor Claude reads project documentation, analyzes logs, and investigates the codebase to generate specific prompts for the executor Claude to implement. The author has also set up various automation systems, such as maintaining a CLAUDE.md file for project documentation, an EstruturaBanco.txt file for database schema, and a logging system to capture execution details. This separation of responsibilities and use of structured prompts with XML tags helps maintain consistency and avoid context loss between the two Claudes. The author reports positive results, with the project having a high number of passing unit tests and fast query performance, while keeping the codebase well-organized.
No comments yet
Be the first to comment