skills.rest
jimeh
jimehCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

sessions

Guides implementation and review of Agents Window changes under src/vs/sessions.

Updated Apr 14, 2026
Search Tags:#vscode#architecture#code review#sessions#layering#workbench#agents window
One-click install
npx skills add https://github.com/jimeh/hucode --skill sessions-jimeh
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sessions
Source: https://github.com/jimeh/hucode/tree/main/.github/skills/sessions
Command: npx skills add https://github.com/jimeh/hucode --skill sessions-jimeh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Working on the Agents Window in a VS Code fork requires respecting strict layering rules, provider-neutral abstractions, and a large set of architecture specifications; this Skill routes contributors to the right specification and enforces the core principles before code changes. ## Core Features & Use Cases - Architecture routing: Maps each change area (layout, automations, providers, mobile, sidebar) to its authoritative specification file under src/vs/sessions. - Layering and contract enforcement: Ensures vs/sessions never gets imported by vs/workbench, keeps providers behind ISession/IChat, and routes contributions through sessions.*.main.ts entry points. - Specification edit gate: Defines when an authoritative spec may be updated versus when behavior belongs in regression tests and code comments. - Use Case: When adding a feature to the Sessions sidebar, use this Skill to identify SESSIONS_LIST.md as the owning spec, trace existing tests, and validate with focused unit tests plus valid-layers-check. ## Quick Start Use the sessions skill to plan and implement my change to the Agents Window sidebar under src/vs/sessions.

Frequently Asked Questions about sessions

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I make changes to the Agents Window in src/vs/sessions?▼

Start with src/vs/sessions/README.md, then read only the specification matching your change area, such as SESSIONS.md or LAYOUT.md. Trace the existing implementation and tests, apply the core principles, and validate with the smallest relevant checks.

What layering rules apply between vs/sessions and vs/workbench?▼

The vs/sessions layer may import vs/workbench and lower layers, but vs/workbench must never import vs/sessions. Run npm run valid-layers-check whenever imports or module ownership change to verify the boundary.

When should I update an architecture specification versus writing a test?▼

Update a specification only when ownership, an interface or lifecycle contract, a state machine, persistence, or a cross-component invariant changes. Bug fixes, styling, telemetry fields, and algorithm details belong in regression tests and code comments instead.

How do session providers stay decoupled from shared Sessions code?▼

Providers expose state through the provider-neutral ISession and IChat interfaces, and non-provider contributions must not import provider implementations. Provider-specific decisions stay inside the provider's own directory under contrib/providers.

What validation should I run after a Sessions change?▼

Run the smallest checks covering the change: focused unit tests for affected behavior, valid-layers-check for import changes, targeted type checking for TypeScript edits, and integration or E2E tests for cross-process or UI work.

Related Skills

Explore More Software Engineering Skills→
posit-devposit-dev
4.2k

integrated-browser

Explains the architecture and mental model of the VS Code integrated browser.

Official
Advanced
PacificStudioPacificStudio
264

land

Enforce CI and branch-state checks before merging Git changes.

Official
Intermediate
AradotsoAradotso
2

claude-code-agent-architecture

Analyze Claude Code CLI Agent architecture, telemetry, and tool control mechanisms.

Official
Advanced
agencia-conversionagencia-conversion
49

spec-driven

Convert compound SEO requests into spec, plan, and result-check artifacts.

Official
Intermediate