Semantic Memory Assimilation

🧠 Semantic Memory Assimilation (V3.1 Skill)

Directive: Do not guess the structure of the user's project. Do not assume file locations. Read the dynamically generated memory.

When analyzing a codebase, you must pull your context directly from the V3 AST-aware sync outputs located in paths.memory (memory/global/).

1. Context Acquisition Targets

Before planning any architectural or coding task, check these ground-truth files:

1. architecture.md: Contains the physical directory layout, framework detection results, and language-specific Lines of Code (LOC) counts.
2. api-contracts.md: Contains exactly which routes (Express, Next.js, FastAPI, etc.) are physically registered in the AST.
3. dependencies.md: Contains the exhaustive list of production packages and their exact verified versions from package.json, requirements.txt, or Cargo.toml.

2. Hallucination Prevention

• Never assume a route exists just because the user asks about it. Verify it against api-contracts.md.
• Never suggest installing a package before checking dependencies.md to see if it (or an equivalent) is already installed.
• Always reference the specific framework versions (e.g., "Since architecture.md shows Next.js 14, we will use App Router").

3. Integration with the Antigravity Baseline

Combine this memory assimilation with the @Antigravity-Directive.md:

1. Read AST memory.
2. Formulate a Tree-of-Thought plan based only on the registered facts.
3. Yield execution back to the IDE AI (Cursor/Copilot) via MCP.