https://www.anthropic.com/engineering/claude-code-best-practices https://www.anthropic.com/engineering/claude-code-best-pract... See: 6. Uplevel with multi-Cla

https://www.anthropic.com/engineering/claude-code-best-practices https://www.anthropic.com/engineering/claude-code-best-pract... See: 6. Uplevel with multi-Claude workflows Since Claude Code is a Terminal utility, and it can call other utilities including itself, it's possible to have one Claude prompt that orchestrates multiple other Claude prompts. So the main prompt can have a global CLAUDE.md that understands high-level tasks, while the other prompts understand better how to write, test, store, test or run code. e.g.: High level prompt that has a general CLAUDE.md plus description of a feature and it's edge cases as input. You discuss the design, then you execute the design, by passing to a specific code writing prompt that implements and writes tests. Then a second prompt will start running the tests, and will call another coding prompt to fix stuff if needed. Finally the main prompt tells you either it's stuck, or the feature works as expected.