What problem does it solve? Working on the Agents Window in a VS Code-based codebase requires respecting strict layering rules, provider-neutral contracts, and observable-based state models. This Skill routes contributors to the correct specification and enforces architectural boundaries so changes to src/vs/sessions stay consistent and reviewable. ## Core Features & Use Cases - Core principles enforcement: Preserves layer direction (vs/sessions may import vs/workbench, never the reverse), keeps shared code provider-neutral, and models session state with observables rather than events. - Specification routing: Maps each change area (layout, automations, providers, mobile, sessions list) to its authoritative specification file so you read only what is relevant. - Proportional validation and spec edit gate: Directs you to run the smallest applicable checks (unit tests, valid-layers-check, type checking) and blocks specification edits unless an ownership, interface, lifecycle, or persistence contract genuinely changes. - Use Case: When adding a new Sessions sidebar grouping feature, use this Skill to identify SESSIONS_LIST.md as the owning spec, trace existing tests, implement through the correct sessions.*.main.ts entry point, and run focused unit tests plus the layer check. ## Quick Start Use the sessions skill to plan and implement my change to the Agents Window sidebar under src/vs/sessions.
