中文 | English
How does Claude Code grow beyond the main loop into product-layer systems like skills, multi-agent work, memory, and cost tracking?
python examples/l6_advanced.pyskills/coordinator/tools/AgentTool/tools/SyntheticOutputTool/memdir/cost-tracker.ts
SYNTHETIC_OUTPUT_TOOL_NAMEcreateSyntheticOutputToolMEMORY.mdcost
- which capabilities are really “prompt reuse as a product feature”
- how structured output locks the boundary around multi-agent work
- why memory behaves like an index instead of a growing log dump
The demo compresses several advanced mechanisms into one file. The real source keeps them decoupled and lets the session orchestration compose them.
- What are the boundaries between skills, tools, and commands?
- Why should the coordinator not inspect worker intermediate state?
- Why is memory closer to a directory index than a long-term chat transcript?