[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7BTER46XJCEMAT97XA5FANX":3,"skill-same:01M7BTER46XJCEMAT97XA5FANX":49},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":26,"commitSha":27,"skillDirectory":28,"forksCount":29,"repositoryHtmlUrl":30,"repositoryHomepageUrl":31,"ownerHtmlUrl":32,"ownerBlogUrl":6,"ownerDescription":33,"updatedAt":34,"install":35,"resources":48},"01M7BTER46XJCEMAT97XA5FANX","chat-customizations-editor",null,"Use when working on the Chat Customizations editor — the management UI for agents, skills, instructions, hooks, prompts, MCP servers, and plugins.","YYC-Cube\u002FYYC3-Knowledge-Base","YYC-Cube","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F235006543?v=4","01M79J2PH4SWD2X0825X6PN748","yyc3","01M79J2PHVK3F6ZBYT8K2SCZCW",1,"MIT","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-IDE-编辑器内核\u002FYYC3-IDE-编辑器内核-vscode\u002F.github\u002Fskills\u002Fchat-customizations-editor\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: chat-customizations-editor\ndescription: Use when working on the Chat Customizations editor — the management UI for agents, skills, instructions, hooks, prompts, MCP servers, and plugins.\nmetadata:\n  allowed-tools: Bash(npx @playwright\u002Fcli:*)\n---\n\n# Chat Customizations Editor\n\nSplit-view management pane for AI customization items across workspace, user, extension, and plugin storage. Supports harness-based filtering (Local, Copilot CLI, Claude).\n\n## Spec\n\n**`src\u002Fvs\u002Fsessions\u002FAI_CUSTOMIZATIONS.md`** — always read before making changes, always update after.\n\n## Key Folders\n\n| Folder | What |\n|--------|------|\n| `src\u002Fvs\u002Fworkbench\u002Fcontrib\u002Fchat\u002Fcommon\u002F` | `ICustomizationHarnessService`, `ISectionOverride`, `IStorageSourceFilter` — shared interfaces and filter helpers |\n| `src\u002Fvs\u002Fworkbench\u002Fcontrib\u002Fchat\u002Fbrowser\u002FaiCustomization\u002F` | Management editor, list widgets (prompts, MCP, plugins), harness service registration |\n| `src\u002Fvs\u002Fsessions\u002Fcontrib\u002Fchat\u002Fbrowser\u002F` | Sessions-window overrides (harness service, workspace service) |\n| `src\u002Fvs\u002Fsessions\u002Fcontrib\u002Fsessions\u002Fbrowser\u002F` | Sessions tree view counts and toolbar |\n\nWhen changing harness descriptor interfaces or factory functions, verify both core and sessions registrations compile.\n\n## Key Interfaces\n\n- **`IHarnessDescriptor`** — drives all UI behavior declaratively (hidden sections, button overrides, file filters, agent gating). See spec for full field reference.\n- **`ISectionOverride`** — per-section button customization (command invocation, root file creation, type labels, file extensions).\n- **`IStorageSourceFilter`** — controls which storage sources and user roots are visible per harness\u002Ftype.\n- **`IExternalCustomizationItemProvider`** \u002F **`IExternalCustomizationItem`** — internal interfaces (in `customizationHarnessService.ts`) for extension-contributed providers that supply items directly. These mirror the proposed extension API types.\n\nPrinciple: the UI widgets read everything from the descriptor — no harness-specific conditionals in widget code.\n\n## Extension API (`chatSessionCustomizationProvider`)\n\nThe proposed API in `src\u002Fvscode-dts\u002Fvscode.proposed.chatSessionCustomizationProvider.d.ts` lets extensions register customization providers. Changes to `IExternalCustomizationItem` or `IExternalCustomizationItemProvider` must be kept in sync across the full chain:\n\n| Layer | File | Type |\n|-------|------|------|\n| Extension API | `vscode.proposed.chatSessionCustomizationProvider.d.ts` | `ChatSessionCustomizationItem` |\n| IPC DTO | `extHost.protocol.ts` | `IChatSessionCustomizationItemDto` |\n| ExtHost mapping | `extHostChatAgents2.ts` | `$provideChatSessionCustomizations()` |\n| MainThread mapping | `mainThreadChatAgents2.ts` | `provideChatSessionCustomizations` callback |\n| Internal interface | `customizationHarnessService.ts` | `IExternalCustomizationItem` |\n\nWhen adding fields to `IExternalCustomizationItem`, update all five layers. The proposed API `.d.ts` is additive-only (new optional fields are backward-compatible and do not require a version bump).\n\n## Testing\n\nComponent explorer fixtures (see `component-fixtures` skill): `aiCustomizationListWidget.fixture.ts`, `aiCustomizationManagementEditor.fixture.ts` under `src\u002Fvs\u002Fworkbench\u002Ftest\u002Fbrowser\u002FcomponentFixtures\u002F`.\n\n### Screenshotting specific tabs\n\nThe management editor fixture supports a `selectedSection` option to render any tab. Each tab has Dark\u002FLight variants auto-generated by `defineThemedFixtureGroup`.\n\n**Available fixture IDs** (use with `mcp_component-exp_screenshot`):\n\n| Fixture ID pattern | Tab shown |\n|---|---|\n| `chat\u002FaiCustomizations\u002FaiCustomizationManagementEditor\u002FAgentsTab\u002F{Dark,Light}` | Agents |\n| `chat\u002FaiCustomizations\u002FaiCustomizationManagementEditor\u002FSkillsTab\u002F{Dark,Light}` | Skills |\n| `chat\u002FaiCustomizations\u002FaiCustomizationManagementEditor\u002FInstructionsTab\u002F{Dark,Light}` | Instructions |\n| `chat\u002FaiCustomizations\u002FaiCustomizationManagementEditor\u002FHooksTab\u002F{Dark,Light}` | Hooks |\n| `chat\u002FaiCustomizations\u002FaiCustomizationManagementEditor\u002FPromptsTab\u002F{Dark,Light}` | Prompts |\n| `chat\u002FaiCustomizations\u002FaiCustomizationManagementEditor\u002FMcpServersTab\u002F{Dark,Light}` | MCP Servers |\n| `chat\u002FaiCustomizations\u002FaiCustomizationManagementEditor\u002FPluginsTab\u002F{Dark,Light}` | Plugins |\n| `chat\u002FaiCustomizations\u002FaiCustomizationManagementEditor\u002FLocalHarness\u002F{Dark,Light}` | Default (Agents, Local harness) |\n| `chat\u002FaiCustomizations\u002FaiCustomizationManagementEditor\u002FCliHarness\u002F{Dark,Light}` | Default (Agents, CLI harness) |\n| `chat\u002FaiCustomizations\u002FaiCustomizationManagementEditor\u002FClaudeHarness\u002F{Dark,Light}` | Default (Agents, Claude harness) |\n| `chat\u002FaiCustomizations\u002FaiCustomizationManagementEditor\u002FSessions\u002F{Dark,Light}` | Sessions window variant |\n\n**Adding a new tab fixture:** Add a variant to the `defineThemedFixtureGroup` in `aiCustomizationManagementEditor.fixture.ts`:\n```typescript\nMyNewTab: defineComponentFixture({\n    labels: { kind: 'screenshot' },\n    render: ctx => renderEditor(ctx, {\n        harness: CustomizationHarness.VSCode,\n        selectedSection: AICustomizationManagementSection.MySection,\n    }),\n}),\n```\n\nThe `selectedSection` calls `editor.selectSectionById()` after `setInput`, which navigates to the specified tab and re-layouts.\n\n### Populating test data\n\nEach customization type requires its own mock path in `createMockPromptsService`:\n- **Agents** — `getCustomAgents()` returns agent objects\n- **Skills** — `findAgentSkills()` returns `IAgentSkill[]`\n- **Prompts** — `getPromptSlashCommands()` returns `IChatPromptSlashCommand[]`\n- **Instructions\u002FHooks** — `listPromptFiles()` filtered by `PromptsType`\n- **MCP Servers** — `mcpWorkspaceServers`\u002F`mcpUserServers` arrays passed to `IMcpWorkbenchService` mock\n- **Plugins** — `IPluginMarketplaceService.installedPlugins` and `IAgentPluginService.plugins` observables\n\nAll test data lives in `allFiles` (prompt-based items) and the `mcpWorkspace\u002FUserServers` arrays. Add enough items per category (8+) to invoke scrolling.\n\n### Exercising built-in grouping\n\nThe list widget regroups items from the default chat extension under a \"Built-in\" header. Three things must be in place for fixtures to exercise this:\n1. Include `BUILTIN_STORAGE` in the harness descriptor's visible sources\n2. Mock `IProductService.defaultChatAgent.chatExtensionId` (e.g., `'GitHub.copilot-chat'`)\n3. Give mock items extension provenance via `extensionId` \u002F `extensionDisplayName` matching that ID\n\nWithout all three, built-in regrouping silently doesn't run and the fixture only shows flat lists.\n\n### Editor contribution service mocks\n\nThe management editor embeds a `CodeEditorWidget`. Electron-side editor contributions (e.g., `AgentFeedbackEditorWidgetContribution`) are instantiated automatically and crash if their injected services aren't registered. The fixture must mock at minimum:\n- `IAgentFeedbackService` — needs `onDidChangeFeedback`, `onDidChangeNavigation`, `onDidAddFeedback`, `onDidConvertFeedback`, `onDidAddReply`, `onDidSubmitFeedback` as `Event.None`\n- `ICodeReviewService` — needs `getReviewState()` \u002F `getPRReviewState()` returning idle observables\n- `IChatEditingService` — needs `editingSessionsObs` as empty observable\n- `IAgentSessionsService` — needs `model.sessions` as empty array\n\nThese are cross-layer imports from `vs\u002Fsessions\u002F` — use `\u002F\u002F eslint-disable-next-line local\u002Fcode-import-patterns` on the import lines.\n\n### CI regression gates\n\nKey fixtures have `blocksCi: true` in their labels. The `component-fixtures.yml` GitHub Action captures screenshots on every PR to `main` and **fails the CI status check** if any `blocks-ci`-labeled fixture's screenshot changes. This catches layout regressions automatically.\n\nCurrently gated fixtures: `LocalHarness`, `McpServersTab`, `McpServersTabNarrow`, `AgentsTabNarrow`. When adding a new section or layout-critical fixture, add `blocksCi: true`:\n\n```typescript\nMyFixture: defineComponentFixture({\n    labels: { kind: 'screenshot', blocksCi: true },\n    render: ctx => renderEditor(ctx, { ... }),\n}),\n```\n\nDon't add `blocksCi` to every fixture — only ones that cover critical layout paths (default view, section with list + footer, narrow viewport). Too many gated fixtures creates noisy CI.\n\n### Screenshot stability\n\nScrollbar fade transitions cause screenshot instability — the scrollbar shifts from `visible` to `invisible fade` class ~2 seconds after a programmatic scroll. After calling `revealLastItem()` or any scroll action, wait for the transition to complete before the fixture's render promise resolves:\n\n```typescript\nawait new Promise(resolve => setTimeout(resolve, 2400));\n\u002F\u002F Then optionally poll until .scrollbar.vertical loses the 'visible' class\n```\n\n### Running unit tests\n\n```bash\n.\u002Fscripts\u002Ftest.sh --grep \"applyStorageSourceFilter|customizationCounts\"\nnpm run compile-check-ts-native && npm run valid-layers-check\n```\n\nSee the `sessions` skill for sessions-window specific guidance.\n\n## Debugging Layout in the Real Product\n\nComponent fixtures use mock data and a fixed container size. Layout bugs caused by reflow timing, real data shapes, or narrow window sizes often **don't reproduce in fixtures**. When a user reports a broken layout, debug in the live Code OSS product.\n\nFor launching Code OSS with CDP and connecting `@playwright\u002Fcli`, see the **`launch` skill**. Use `--user-data-dir \u002Ftmp\u002Fcode-oss-debug` to avoid colliding with an already-running instance from another worktree.\n\n### Navigating to the customizations editor\n\nAfter connecting, use `snapshot` to find the \"Open Customizations\" button (in the Chat panel header), then click it. To switch sections, use `eval` with a DOM click since sidebar items aren't interactive refs:\n\n```bash\nnpx @playwright\u002Fcli eval \"(() => { const items = [...document.querySelectorAll('.section-list-item')]; items.find(el => el.textContent?.includes('MCP'))?.click(); })()\"\n```\n\n### Inspecting widget layout\n\n`@playwright\u002Fcli eval` wraps the expression in `() => (...)` — use an IIFE for multi-statement code. Use `document.title` as a return channel:\n\n```bash\nnpx @playwright\u002Fcli eval \"(() => { const w = document.querySelector('.mcp-list-widget'); \\\n  const lc = w?.querySelector('.mcp-list-container'); \\\n  const rows = lc?.querySelectorAll('.monaco-list-row'); \\\n  document.title = 'DBG:rows=' + (rows?.length ?? -1) \\\n    + ',listH=' + (lc?.offsetHeight ?? -1) \\\n    + ',seStH=' + (lc?.querySelector('.monaco-scrollable-element')?.style?.height ?? '') \\\n    + ',wH=' + (w?.offsetHeight ?? -1); })()\"\nnpx @playwright\u002Fcli eval \"document.title\" 2>&1\n```\n\nKey diagnostics:\n- **`rows`** — fewer than expected means `list.layout()` never received the correct viewport height.\n- **`seStH`** — empty means the list was never properly laid out.\n- **`listH` vs `wH`** — list container height should be widget height minus search bar minus footer.\n\n### Common layout issues\n\n| Symptom | Root cause | Fix pattern |\n|---------|-----------|-------------|\n| List shows 0-1 rows in a tall container | `layout()` bailed out because `offsetHeight` returned 0 during `display:none → visible` transition | Defer layout via `DOM.getWindow(this.element).requestAnimationFrame(...)` |\n| Badge or row content clips at right edge | Widget container missing `overflow: hidden` | Add `overflow: hidden` to the widget's CSS class |\n| Items visible in fixture but not in product | Fixture uses many mock items; real product has few | Add fixture variants with fewer items or narrower dimensions (`width`\u002F`height` options) |\n\n### Fixture vs real product gaps\n\nFixtures render at a fixed size (default 900×600) with many mock items. They won't catch:\n- **Reflow timing** — the real product's `display:none → visible` transition may not have reflowed before `layout()` fires\n- **Narrow windows** — add narrow fixture variants (e.g., `width: 550, height: 400`)\n- **Real data counts** — a user with 1 MCP server sees very different layout than a fixture with 12\n","# Chat Customizations Editor\n\nSplit-view management pane for AI customization items across workspace, user, extension, and plugin storage. Supports harness-based filtering (Local, Copilot CLI, Claude).\n\n## Spec\n\n**`src\u002Fvs\u002Fsessions\u002FAI_CUSTOMIZATIONS.md`** — always read before making changes, always update after.\n\n## Key Folders\n\n| Folder | What |\n|--------|------|\n| `src\u002Fvs\u002Fworkbench\u002Fcontrib\u002Fchat\u002Fcommon\u002F` | `ICustomizationHarnessService`, `ISectionOverride`, `IStorageSourceFilter` — shared interfaces and filter helpers |\n| `src\u002Fvs\u002Fworkbench\u002Fcontrib\u002Fchat\u002Fbrowser\u002FaiCustomization\u002F` | Management editor, list widgets (prompts, MCP, plugins), harness service registration |\n| `src\u002Fvs\u002Fsessions\u002Fcontrib\u002Fchat\u002Fbrowser\u002F` | Sessions-window overrides (harness service, workspace service) |\n| `src\u002Fvs\u002Fsessions\u002Fcontrib\u002Fsessions\u002Fbrowser\u002F` | Sessions tree view counts and toolbar |\n\nWhen changing harness descriptor interfaces or factory functions, verify both core and sessions registrations compile.\n\n## Key Interfaces\n\n- **`IHarnessDescriptor`** — drives all UI behavior declaratively (hidden sections, button overrides, file filters, agent gating). See spec for full field reference.\n- **`ISectionOverride`** — per-section button customization (command invocation, root file creation, type labels, file extensions).\n- **`IStorageSourceFilter`** — controls which storage sources and user roots are visible per harness\u002Ftype.\n- **`IExternalCustomizationItemProvider`** \u002F **`IExternalCustomizationItem`** — internal interfaces (in `customizationHarnessService.ts`) for extension-contributed providers that supply items directly. These mirror the proposed extension API types.\n\nPrinciple: the UI widgets read everything from the descriptor — no harness-specific conditionals in widget code.\n\n## Extension API (`chatSessionCustomizationProvider`)\n\nThe proposed API in `src\u002Fvscode-dts\u002Fvscode.proposed.chatSessionCustomizationProvider.d.ts` lets extensions register customization providers. Changes to `IExternalCustomizationItem` or `IExternalCustomizationItemProvider` must be kept in sync across the full chain:\n\n| Layer | File | Type |\n|-------|------|------|\n| Extension API | `vscode.proposed.chatSessionCustomizationProvider.d.ts` | `ChatSessionCustomizationItem` |\n| IPC DTO | `extHost.protocol.ts` | `IChatSessionCustomizationItemDto` |\n| ExtHost mapping | `extHostChatAgents2.ts` | `$provideChatSessionCustomizations()` |\n| MainThread mapping | `mainThreadChatAgents2.ts` | `provideChatSessionCustomizations` callback |\n| Internal interface | `customizationHarnessService.ts` | `IExternalCustomizationItem` |\n\nWhen adding fields to `IExternalCustomizationItem`, update all five layers. The proposed API `.d.ts` is additive-only (new optional fields are backward-compatible and do not require a version bump).\n\n## Testing\n\nComponent explorer fixtures (see `component-fixtures` skill): `aiCustomizationListWidget.fixture.ts`, `aiCustomizationManagementEditor.fixture.ts` under `src\u002Fvs\u002Fworkbench\u002Ftest\u002Fbrowser\u002FcomponentFixtures\u002F`.\n\n### Screenshotting specific tabs\n\nThe management editor fixture supports a `selectedSection` option to render any tab. Each tab has Dark\u002FLight variants auto-generated by `defineThemedFixtureGroup`.\n\n**Available fixture IDs** (use with `mcp_component-exp_screenshot`):\n\n| Fixture ID pattern | Tab shown |\n|---|---|\n| `chat\u002FaiCustomizations\u002FaiCustomizationManagementEditor\u002FAgentsTab\u002F{Dark,Light}` | Agents |\n| `chat\u002FaiCustomizations\u002FaiCustomizationManagementEditor\u002FSkillsTab\u002F{Dark,Light}` | Skills |\n| `chat\u002FaiCustomizations\u002FaiCustomizationManagementEditor\u002FInstructionsTab\u002F{Dark,Light}` | Instructions |\n| `chat\u002FaiCustomizations\u002FaiCustomizationManagementEditor\u002FHooksTab\u002F{Dark,Light}` | Hooks |\n| `chat\u002FaiCustomizations\u002FaiCustomizationManagementEditor\u002FPromptsTab\u002F{Dark,Light}` | Prompts |\n| `chat\u002FaiCustomizations\u002FaiCustomizationManagementEditor\u002FMcpServersTab\u002F{Dark,Light}` | MCP Servers |\n| `chat\u002FaiCustomizations\u002FaiCustomizationManagementEditor\u002FPluginsTab\u002F{Dark,Light}` | Plugins |\n| `chat\u002FaiCustomizations\u002FaiCustomizationManagementEditor\u002FLocalHarness\u002F{Dark,Light}` | Default (Agents, Local harness) |\n| `chat\u002FaiCustomizations\u002FaiCustomizationManagementEditor\u002FCliHarness\u002F{Dark,Light}` | Default (Agents, CLI harness) |\n| `chat\u002FaiCustomizations\u002FaiCustomizationManagementEditor\u002FClaudeHarness\u002F{Dark,Light}` | Default (Agents, Claude harness) |\n| `chat\u002FaiCustomizations\u002FaiCustomizationManagementEditor\u002FSessions\u002F{Dark,Light}` | Sessions window variant |\n\n**Adding a new tab fixture:** Add a variant to the `defineThemedFixtureGroup` in `aiCustomizationManagementEditor.fixture.ts`:\n```typescript\nMyNewTab: defineComponentFixture({\n    labels: { kind: 'screenshot' },\n    render: ctx => renderEditor(ctx, {\n        harness: CustomizationHarness.VSCode,\n        selectedSection: AICustomizationManagementSection.MySection,\n    }),\n}),\n```\n\nThe `selectedSection` calls `editor.selectSectionById()` after `setInput`, which navigates to the specified tab and re-layouts.\n\n### Populating test data\n\nEach customization type requires its own mock path in `createMockPromptsService`:\n- **Agents** — `getCustomAgents()` returns agent objects\n- **Skills** — `findAgentSkills()` returns `IAgentSkill[]`\n- **Prompts** — `getPromptSlashCommands()` returns `IChatPromptSlashCommand[]`\n- **Instructions\u002FHooks** — `listPromptFiles()` filtered by `PromptsType`\n- **MCP Servers** — `mcpWorkspaceServers`\u002F`mcpUserServers` arrays passed to `IMcpWorkbenchService` mock\n- **Plugins** — `IPluginMarketplaceService.installedPlugins` and `IAgentPluginService.plugins` observables\n\nAll test data lives in `allFiles` (prompt-based items) and the `mcpWorkspace\u002FUserServers` arrays. Add enough items per category (8+) to invoke scrolling.\n\n### Exercising built-in grouping\n\nThe list widget regroups items from the default chat extension under a \"Built-in\" header. Three things must be in place for fixtures to exercise this:\n1. Include `BUILTIN_STORAGE` in the harness descriptor's visible sources\n2. Mock `IProductService.defaultChatAgent.chatExtensionId` (e.g., `'GitHub.copilot-chat'`)\n3. Give mock items extension provenance via `extensionId` \u002F `extensionDisplayName` matching that ID\n\nWithout all three, built-in regrouping silently doesn't run and the fixture only shows flat lists.\n\n### Editor contribution service mocks\n\nThe management editor embeds a `CodeEditorWidget`. Electron-side editor contributions (e.g., `AgentFeedbackEditorWidgetContribution`) are instantiated automatically and crash if their injected services aren't registered. The fixture must mock at minimum:\n- `IAgentFeedbackService` — needs `onDidChangeFeedback`, `onDidChangeNavigation`, `onDidAddFeedback`, `onDidConvertFeedback`, `onDidAddReply`, `onDidSubmitFeedback` as `Event.None`\n- `ICodeReviewService` — needs `getReviewState()` \u002F `getPRReviewState()` returning idle observables\n- `IChatEditingService` — needs `editingSessionsObs` as empty observable\n- `IAgentSessionsService` — needs `model.sessions` as empty array\n\nThese are cross-layer imports from `vs\u002Fsessions\u002F` — use `\u002F\u002F eslint-disable-next-line local\u002Fcode-import-patterns` on the import lines.\n\n### CI regression gates\n\nKey fixtures have `blocksCi: true` in their labels. The `component-fixtures.yml` GitHub Action captures screenshots on every PR to `main` and **fails the CI status check** if any `blocks-ci`-labeled fixture's screenshot changes. This catches layout regressions automatically.\n\nCurrently gated fixtures: `LocalHarness`, `McpServersTab`, `McpServersTabNarrow`, `AgentsTabNarrow`. When adding a new section or layout-critical fixture, add `blocksCi: true`:\n\n```typescript\nMyFixture: defineComponentFixture({\n    labels: { kind: 'screenshot', blocksCi: true },\n    render: ctx => renderEditor(ctx, { ... }),\n}),\n```\n\nDon't add `blocksCi` to every fixture — only ones that cover critical layout paths (default view, section with list + footer, narrow viewport). Too many gated fixtures creates noisy CI.\n\n### Screenshot stability\n\nScrollbar fade transitions cause screenshot instability — the scrollbar shifts from `visible` to `invisible fade` class ~2 seconds after a programmatic scroll. After calling `revealLastItem()` or any scroll action, wait for the transition to complete before the fixture's render promise resolves:\n\n```typescript\nawait new Promise(resolve => setTimeout(resolve, 2400));\n\u002F\u002F Then optionally poll until .scrollbar.vertical loses the 'visible' class\n```\n\n### Running unit tests\n\n```bash\n.\u002Fscripts\u002Ftest.sh --grep \"applyStorageSourceFilter|customizationCounts\"\nnpm run compile-check-ts-native && npm run valid-layers-check\n```\n\nSee the `sessions` skill for sessions-window specific guidance.\n\n## Debugging Layout in the Real Product\n\nComponent fixtures use mock data and a fixed container size. Layout bugs caused by reflow timing, real data shapes, or narrow window sizes often **don't reproduce in fixtures**. When a user reports a broken layout, debug in the live Code OSS product.\n\nFor launching Code OSS with CDP and connecting `@playwright\u002Fcli`, see the **`launch` skill**. Use `--user-data-dir \u002Ftmp\u002Fcode-oss-debug` to avoid colliding with an already-running instance from another worktree.\n\n### Navigating to the customizations editor\n\nAfter connecting, use `snapshot` to find the \"Open Customizations\" button (in the Chat panel header), then click it. To switch sections, use `eval` with a DOM click since sidebar items aren't interactive refs:\n\n```bash\nnpx @playwright\u002Fcli eval \"(() => { const items = [...document.querySelectorAll('.section-list-item')]; items.find(el => el.textContent?.includes('MCP'))?.click(); })()\"\n```\n\n### Inspecting widget layout\n\n`@playwright\u002Fcli eval` wraps the expression in `() => (...)` — use an IIFE for multi-statement code. Use `document.title` as a return channel:\n\n```bash\nnpx @playwright\u002Fcli eval \"(() => { const w = document.querySelector('.mcp-list-widget'); \\\n  const lc = w?.querySelector('.mcp-list-container'); \\\n  const rows = lc?.querySelectorAll('.monaco-list-row'); \\\n  document.title = 'DBG:rows=' + (rows?.length ?? -1) \\\n    + ',listH=' + (lc?.offsetHeight ?? -1) \\\n    + ',seStH=' + (lc?.querySelector('.monaco-scrollable-element')?.style?.height ?? '') \\\n    + ',wH=' + (w?.offsetHeight ?? -1); })()\"\nnpx @playwright\u002Fcli eval \"document.title\" 2>&1\n```\n\nKey diagnostics:\n- **`rows`** — fewer than expected means `list.layout()` never received the correct viewport height.\n- **`seStH`** — empty means the list was never properly laid out.\n- **`listH` vs `wH`** — list container height should be widget height minus search bar minus footer.\n\n### Common layout issues\n\n| Symptom | Root cause | Fix pattern |\n|---------|-----------|-------------|\n| List shows 0-1 rows in a tall container | `layout()` bailed out because `offsetHeight` returned 0 during `display:none → visible` transition | Defer layout via `DOM.getWindow(this.element).requestAnimationFrame(...)` |\n| Badge or row content clips at right edge | Widget container missing `overflow: hidden` | Add `overflow: hidden` to the widget's CSS class |\n| Items visible in fixture but not in product | Fixture uses many mock items; real product has few | Add fixture variants with fewer items or narrower dimensions (`width`\u002F`height` options) |\n\n### Fixture vs real product gaps\n\nFixtures render at a fixed size (default 900×600) with many mock items. They won't catch:\n- **Reflow timing** — the real product's `display:none → visible` transition may not have reflowed before `layout()` fires\n- **Narrow windows** — add narrow fixture variants (e.g., `width: 550, height: 400`)\n- **Real data counts** — a user with 1 MCP server sees very different layout than a fixture with 12\n",{"name":5,"metadata":24,"description":7},{"allowed-tools":25},"Bash(npx @playwright\u002Fcli:*)","main","87afe6ce96220accf50a345dea46784c8c9f210e","YYC3-IDE-编辑器内核\u002FYYC3-IDE-编辑器内核-vscode\u002F.github\u002Fskills\u002Fchat-customizations-editor",0,"https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base","https:\u002F\u002Fkb.yyc3.top\u002F","https:\u002F\u002Fgithub.com\u002FYYC-Cube","万象归元于云枢 | 深栈智启新纪元","2026-11-10 10:37:32",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill chat-customizations-editor",{"tool":41,"command":42},"bunx","bunx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill chat-customizations-editor",{"tool":44,"command":45},"pnpm","pnpm dlx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill chat-customizations-editor","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-IDE-编辑器内核\u002FYYC3-IDE-编辑器内核-vscode\u002F.github\u002Fskills\u002Fchat-customizations-editor\u002FSKILL.md",true,[],[50,57,64,71,78,85],{"skillNo":51,"name":52,"nameZh":6,"description":53,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":54,"categories":55,"keywords":56,"publishedAt":19},"01M7CTDWHERCXPQCP0K03A86AS","vercel-sandbox","Run agent-browser + Chrome inside Vercel Sandbox microVMs for browser automation from any Vercel-deployed app. Use when the user needs browser automation in a Vercel app (Next.js, SvelteKit, Nuxt, Remix, Astro, etc.), wants to run headless Chrome without binary size limits, needs persistent browser sessions across commands, or wants ephemeral isolated browser environments. Triggers include \"Vercel Sandbox browser\", \"microVM Chrome\", \"agent-browser in sandbox\", \"browser automation on Vercel\", or any task requiring Chrome in a Vercel Sandbox.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Fvercel-sandbox\u002FSKILL.md",[],[],{"skillNo":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":19},"01M7CTD8D2BNJY54S65M47HEJA","slack","Interact with Slack workspaces using browser automation. Use when the user needs to check unread channels, navigate Slack, send messages, extract data, find information, search conversations, or automate any Slack task. Triggers include \"check my Slack\", \"what channels have unreads\", \"send a message to\", \"search Slack for\", \"extract from Slack\", \"find who said\", or any task requiring programmatic Slack interaction.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Fslack\u002FSKILL.md",[],[],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":19},"01M7CTCSSB8ZP3Q58C3YZDZK1W","electron","Automate Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify, etc.) using agent-browser via Chrome DevTools Protocol. Use when the user needs to interact with an Electron app, automate a desktop app, connect to a running app, control a native app, or test an Electron application. Triggers include \"automate Slack app\", \"control VS Code\", \"interact with Discord app\", \"test this Electron app\", \"connect to desktop app\", or any task requiring automation of a native Electron application.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Felectron\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":19},"01M7CTCBJY76688V4DCZGWFHGQ","dogfood","Systematically explore and test a web application to find bugs, UX issues, and other problems. Use when asked to \"dogfood\", \"QA\", \"exploratory test\", \"find issues\", \"bug hunt\", \"test this app\u002Fsite\u002Fplatform\", or review the quality of a web application. Produces a structured report with full reproduction evidence -- step-by-step screenshots, repro videos, and detailed repro steps for every issue -- so findings can be handed directly to the responsible teams.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Fdogfood\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":19},"01M7CTC4H0FFGVEAQR9PA4GA1A","agent-browser","Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to \"open a website\", \"fill out a form\", \"click a button\", \"take a screenshot\", \"scrape data from a page\", \"test this web app\", \"login to a site\", \"automate browser actions\", or any task requiring programmatic web interaction.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Fagent-browser\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":19},"01M7CTBKVFYBG78FDSABSDJTTQ","shadcn","Manages shadcn components and projects — adding, searching, fixing, debugging, styling, and composing UI, including chat interfaces. Provides project context, component docs, and usage examples. Applies when working with shadcn\u002Fui, component registries, presets, --preset codes, or any project with a components.json file. Also triggers for \"shadcn init\", \"create an app with --preset\", \"switch to --preset\", and for building a design system or applying a DESIGN.md or brand spec to shadcn\u002Fui.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-UI-界面组件\u002FYYC3-UI-界面组件-ui\u002Fskills\u002Fshadcn\u002FSKILL.md",[],[]]