A skill file is persistent working memory for an AI agent: it records high-signal discoveries so future sessions begin with context instead of paying the same rediscovery tax. section 4.5
Use two scopes of memory:
- Repository-specific guidance records build traps, architectural gateways, known bugs, and navigation rules. section 4.5
- Global guidance records reusable investigation techniques that apply across unfamiliar codebases. section 4.5
- Keep entries short and actionable; preserve facts an agent can use without re-deriving them. section 4.5
End-of-session update
Ask the agent to place codebase-specific facts in the repository skill file and general exploration lessons in the global file, keeping every entry short and high-signal. section 4.5
# VS Code: CLAUDE.md
## Build
CRITICAL: requires Node 22.22.1 (check .nvmrc).
Node 24 breaks tree-sitter (V8 header incompatibility).
npm install && npm run compile && ./scripts/code.sh
Uses esbuild not tsc, which is why 1.1M lines compiles
in ~1 min. Electron auto-downloads on first launch.
## The gateway nobody expects
ALL file-open paths converge at ONE function:
editorService.openEditor()
src/vs/.../editor/browser/editorService.ts
Explorer, Cmd+O, extensions, command palette: all here.
If you're debugging file-open, start here, not explorer.
## URI gotchas (these WILL bite you)
URI.revive() (tab restoration, cross-process IPC)
bypasses ALL normalization and validation. URI.from()
silently fixes paths. URI.revive() doesn't. If you're
debugging weird URI state after restart, this is why.
## Code navigation
common/ = interfaces. browser/ = implementations.
ALWAYS check browser/ when you find an interface in
common/. The class is usually the same name minus the I.
## Tests
suite() / test(), NOT describe() / it().
describe/it silently passes but doesn't register tests.
node test/unit/node/index.js --run 'src/vs/...'
## [... full architecture diagram in output/vscode/]A useful skill file turns discoveries into operational warnings: required versions and commands, architectural entry points, URI behavior, and navigation conventions. section 4.5
