请问HN：如何将代理工具与代码仓库分离？
我对如何将代理的框架和代码分开感兴趣，比如理想情况下使用不同的代码库。<p>基于规范的开发对我来说进展非常顺利，伴随着大量的代理和技能等。<p>然而，我发现 .Claude/memory/<i>、docs/</i>、.specify/*、hooks 和扩展、上下文管理工具等，有时变得和代码库本身一样难以管理。<p>而且，这一切都混在同一个代码库里。难道这不是一种反模式吗？<p>有没有更好的方法来解决这个问题（或者说还没有）？还是说这是下一个需要发展的人工智能前沿？
查看原文
I’m interested in any approaches or ideas for how to keep agent harness and code separate, like ideally separate repos.<p>Spec driven development is going really well for me, along with a swarm of agents and skills etc.<p>However, I’m seeing .Claude/memory/<i>, docs/</i>, .specify/*, hooks and extensions, context management tools etc becoming as much an overhead to manage as the codebase itself sometimes.<p>Also, it’s all mixed in together, in the same repo. Surely this is an anti-pattern.<p>Are there better ways to do this (yet)? Or is this the next AI frontier to evolve?