Guides implementation of the Agents window architecture in the VS Code sessions layer.
npx skills add https://github.com/voidful/Aixlarity --skill sessions-voidful
Please help me install this Agent Skill. Skill: sessions Source: https://github.com/voidful/Aixlarity/tree/main/aixlarity-ide/.github/skills/sessions Command: npx skills add https://github.com/voidful/Aixlarity --skill sessions-voidful
src/vs/sessions/) need to respect strict layering rules, fixed layout constraints, custom menu IDs, and spec documents that must stay in sync with code. This Skill provides the architectural map and development guidelines so changes land in the right place without violating dependency rules. ## Core Features & Use Cases - Layering and dependency rules: Enforces that vs/sessions may import from vs/workbench and below, but never the reverse, validated with npm run valid-layers-check. - Architecture reference: Documents the folder structure, fixed layout parts (Titlebar, Sidebar, Chat Bar, Auxiliary Bar, Panel, modal editors), the AgentSessionsChatWidget wrapper with deferred session creation, custom Menus.* IDs, and context keys. - Development workflows: Covers how to add contributions under contrib/<feature>/browser/, register entry points, override services, and validate changes with npm run compile-check-ts-native and unit tests. - Use Case: When adding a new sidebar view to the Agents window, follow the guidelines to place it in contrib/, register it with WindowVisibility.Sessions, use Menus.SidebarTitle instead of shared MenuId.*, and update LAYOUT.md with a Revision History entry. ## Quick Start Ask the agent to implement a new feature or fix a bug in the Agents window under src/vs/sessions while following the sessions architecture guidelines.High-intent search queries and answers about installing and using this skill.
Place feature contributions under contrib/<featureName>/browser/ and register them by importing in sessions.desktop.main.ts or sessions.common.main.ts. Core workbench code like layout and parts goes in browser/, and views should use WindowVisibility.Sessions.
vs/sessions may import from vs/workbench, vs/editor, vs/platform, and vs/base, but vs/workbench must never import from vs/sessions. Run npm run valid-layers-check to verify the dependency rules are not violated.
No, the Agents window defines its own menu IDs in browser/menus.ts via the Menus export. Always use Menus.* equivalents such as Menus.ChatBarTitle or Menus.SidebarFooter instead of shared MenuId.* constants.
Run npm run compile-check-ts-native for a repo-wide TypeScript compilation check and npm run valid-layers-check for layering. Do not run tsc directly; use scripts/test.sh for unit tests with an optional --grep filter.
AgentSessionsChatWidget wraps the core ChatWidget with deferred session creation, so the UI is interactive before any session exists and the session is created on first message send. Initial session options travel atomically with the first request.
LAYOUT.md is the authoritative layout specification for the Agents window, and the guidelines require keeping specs in sync with implementation. Any layout change must add a dated entry to the Revision History table at the bottom of LAYOUT.md.
jimehGuides implementation and review of Agents Window changes under src/vs/sessions.
posit-devRuns VS Code integration tests via test-integration scripts with filtering options.
microsoftDefine and enforce structural layout and part visibility for the Agent Sessions workbench.
aadorianImplement Agent Sessions window architecture changes with spec-driven validation.