skills.rest
Tyrizx
TyrizxOFFICIAL
Explore all skills by this author →
GitHub

sessions

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Working on the VS Code Agents Window requires navigating a layered architecture, multiple provider contracts, and many authoritative specifications; this Skill routes contributors to the right specification and enforces the core architectural principles before code changes are made. ## Core Features & Use Cases - Architecture guardrails: Enforces layer direction rules, provider-neutral shared code, observable-based state modeling, and Sessions-owned menu registration. - Specification routing: Maps each change area (layout, sessions list, mobile, providers, AI customizations) to its authoritative specification document under src/vs/sessions. - Proportional validation workflow: Directs contributors to run focused unit tests, layer checks, and targeted type checking based on the scope of the change. - Use Case: When adding a feature to the Copilot Chat session provider, use this Skill to identify the owning specification, confirm layer ownership, implement against the provider contract, and run the smallest relevant validation checks. ## 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 VS Code Agents Window?▼

Start with src/vs/sessions/README.md, then read only the specification matching your change area, such as SESSIONS.md for the model or LAYOUT.md for workbench parts. Trace the existing implementation and tests before editing, and validate with focused unit tests.

What layering rules apply to src/vs/sessions code?▼

The vs/sessions layer may import vs/workbench and lower layers, but vs/workbench must never import vs/sessions. Shared Sessions code must stay provider-neutral, and non-provider contributions must not import provider implementations.

When should I update a specification document in src/vs/sessions?▼

Update a specification only when component ownership, an interface or lifecycle contract, a state machine, persistence, or a cross-component invariant changes. Bug fixes, styling, copy, telemetry fields, and settings defaults belong in code and focused tests, not specifications.

How should session and chat state be modeled in the Agents Window?▼

Model mutable session and chat state with observables so consumers derive UI state reactively. Use events only for notifications, never as a parallel state model or for control flow.

Which validation checks should I run after a Sessions change?▼

Run the smallest checks covering the change: focused unit tests for affected behavior, npm run valid-layers-check when imports or module ownership change, and targeted type checking or integration tests for TypeScript or cross-process work.

Related Skills

Explore More Software Engineering Skills→
NVIDIANVIDIA
2.8k

cuopt-installation-developer

Set up a cuOpt development environment for source builds and tests.

Official
Advanced
ascerra-fullsend-rehearsalascerra-fullsend-rehearsal

fix-review

Analyze pull request review comments, implement fixes, run tests, and commit changes.

Official
Advanced
wfvuewfvue
3

tailwind-design-system

Create a Tailwind v4 design system with CSS-first tokens and CVA components.

Community
Advanced
forcedotcomforcedotcom
1.0k

external-consumers

Tracks external repositories consuming Salesforce VS Code extension APIs to assess breaking changes.

Official
Intermediate