What problem does it solve? When implementing features or fixing issues in the Agents workbench layout, developers risk breaking the fixed grid structure, desynchronizing the layout specification from the code, or misusing shared workbench APIs instead of the agent session-specific parts. ## Core Features & Use Cases - Spec-First Workflow: Directs you to read the authoritative layout specification at src/vs/sessions/LAYOUT.md before making any changes, and to keep it in sync with every code modification. - Implementation Rules: Enforces nine layout principles, including fixed part positions, panel spanning the right section, no-op methods for unsupported features, and separate storage keys for agent session parts. - Key File Map: Provides a reference table of all layout-related files, from workbench.ts and menus.ts to individual part classes like sidebarPart.ts and chatBarPart.ts. - Use Case: When adding a new part to the Agents workbench, follow the guidelines to place it in the right section's horizontal branch, use agent session menu IDs, and update the LAYOUT.md revision history. ## Quick Start Use the agent-sessions-layout skill to add a new part to the Agents workbench right section while keeping LAYOUT.md in sync.
