aicxlisted

## When To Use Pull historical context from previous AI sessions for this project. We are looking for the _why_, not just a blind dump of _how_. ## Canonical Orientation Gate For repo-specific work, run or consume the `vc-init` procedure before turning AICX memory into a recommendation. `Loctree:loctree` is the default structural perception skill for that pass; use it to produce or refresh the Code-Derived Application Map before trusting older intent. If fresh `vc-init` evidence is absent, perform the init pass first and treat repo-specific recommendations as blocked until repo truth exists. AICX explains why prior agents moved. Loctree and current repo gates decide whether that intent is still true. ## Repository Work Doctrine For repository work, start with Loctree as the map: use `loct context`, `loct occurrences`, `loct body`, and `loct find --literal` before broad manual search. Use AICX for intent and session context. Use rg/grep as fallback or local magnifier, not as a replacement for structural mapping. If Loctree fails or misses a surface, append feedback to `~/.vibecrafted/loctree/loctree-fail.md`. ## The toolset: 1. `aicx` (cli) and `aicx-mcp` (stdio and streamable-http): a)the mcp reference: - `mcp_aicx_aicx_rank` Rank stored AI session chunks by content quality. Shows signal density, noise ratio, and quality labels (HIGH/MEDIUM/LOW/NOISE) per chunk. Use --strict to filter noise. - `mcp_aicx_aicx_search` Fuzzy search across stored AI session c