code-navigation-systemlisted

# Code Navigation System Maintain the project's navigation artifacts so future agents can orient themselves quickly by grepping. Anchors and the code map are written for AI agents, not humans: they prioritize symbol density and keyword discoverability over prose elegance. --- ## When to Use This Skill Run at the end of a coding task, before reporting completion, when any of these is true: - A new file was added under `src/`. - A new logical section was added inside an existing file. - A section was renamed, moved between files, or removed. - A section's owned symbols changed (function added/removed/renamed, new DOM IDs/classes introduced). - The way sections connect (entry points, load order) changed. ## When to Skip This Skill - A value was tuned inside an existing section (number, color, string). - A typo was fixed. - A bug was patched without restructuring and without changing owned symbols. - Only `docs/` or [CLAUDE.md](../../../CLAUDE.md) were edited. ## Artifacts Maintained by This Skill 1. [code-map.md](../../../docs/code-map.md): section-level map of every source file. 2. [change-log.md](../../../docs/change-log.md): append-prepend chronological log. 3. Inline anchors: three-line agent-navigation header at the top of each section in source. ## Anchor Format (Agent-optimized) Each section opens with exactly three comment lines: JavaScript: ```js // === cursor-glow === // mousemove pointer-tracking radial-gradient overlay // Owns: initializeCursorGlow(), #cu