project-awareness

原文涵盖的主题

• Project Awareness: Three-Layer Context Architecture
• The Three Layers
• Layer 1: Constitution (CLAUDE.md — always loaded, 150-200 lines)
• Layer 2: Subsystem Docs (.claude/awareness/subsystems/.md — loaded on demand)
• Layer 3: Structural Map (.claude/awareness/structural-map.md — loaded on demand)
• Bootstrap Protocol (First Time Setup)
• Phase 1: Reconnaissance
• Phase 2: Subsystem Identification

You cannot hold an entire non-trivial codebase in one context window. Stop trying. Instead, maintain a structured knowledge system that gives you the 30,000-foot view always, subsystem details on demand, and a compressed structural map for navigation. The project's CLAUDE.md is the "hot memory." It loads on every session start. It contains: What the project IS (2-3 sentences) Module/subsystem inventory (name + one-line purpose each) Key architectural invariants (the rules that must NEVER be violated) Design tensions (known conflicts in the architecture, e.g., "block cache is 4K but AG headers are 512-byte sectors — every write to block 0 must use sector granularity") Routing table: which subsystem doc to load for which task Build/test commands The [AWARENESS] marker with metadata (last update, coverage stats) This document is the SINGLE MOST IMPORTANT artifact. If an agent does nothing else, reading this document should prevent the most common mistakes. Each major subsystem gets its own document. These are the "domain expert" docs. They contain: What the subsystem does and its public API Internal architecture (key data structures, state machines, flows) Invariants specific to this

这里只展示节选，请以完整原文和当前要求为准。