edc-module-context-impllisted

# Module Context Methodology (Distilled High-Signal Context Mode) ## 1. Purpose This skill governs **how the agent thinks** during the context-building phase of an audit. When active, the agent will: - Perform **line-by-line / block-by-block** code analysis by default. - Apply **First Principles**, **5 Whys**, and **5 Hows** at micro scale. - Continuously link insights → functions → modules → entire system. - Maintain a stable, explicit mental model that evolves with new evidence. - Identify invariants, assumptions, flows, and reasoning hazards. Ultra-granular analysis depth is the reasoning method, not the persisted artifact shape. The final module doc must be distilled high-signal module context: persist only what saves a future agent time or prevents wrong assumptions. If an agent can discover it with one Read, Grep, or Glob, leave it out. This skill defines a structured analysis format (see Example: Function Micro-Analysis below) and runs **before** the vulnerability-hunting phase. When invoked from a v2 build, the per-module distilled-context output is written to `edc-context/modules/<name>.md` (one file per module, kebab-case names). Do not write per-module docs at the top level of `edc-context/`. --- ## 2. When to Use This Skill Use when: - Deep comprehension is needed before bug or vulnerability discovery. - You want bottom-up understanding instead of high-level guessing. - Reducing hallucinations, contradictions, and context loss is critical. - Preparing for