📄 中文摘要
在使用 Claude Code 进行开发时，许多开发者面临一个共同的问题：在长时间的项目中，架构和设计决策往往无法保持一致。随着项目的推进，开发者在头脑中形成的架构和决策在新的会话中无法被 Claude Code 记住，导致代码逐渐偏离最初的设计。尽管代码在功能上没有出现问题，测试也通过了，但最终的代码与预期架构不符。这种情况并非 Claude Code 的问题，而是上下文管理的问题，随着项目的延续，这一问题会愈发严重。
如何使用 Claude Code 构建生产级工具 - 并在数周的会话中保持架构的一致性
📄 English Summary
How I Built a Production-Grade Tool with Claude Code - And Kept the Architecture Honest Across Weeks of Sessions
Developers using Claude Code often encounter a significant challenge when working on long-term projects: maintaining architectural consistency. After spending considerable time developing a project, the architecture and design decisions reside solely in the developer's mind. When starting a new session, Claude Code lacks memory of previous sessions, leading to a gradual drift from the original design. Although the code may function correctly and pass tests, it no longer aligns with the intended architecture. This issue is not specific to Claude Code but rather a context management problem that worsens as the project progresses.