[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7DNBMEHS4ZYVQCZTDQAM69H":3,"skill-same:01M7DNBMEHS4ZYVQCZTDQAM69H":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":6,"ownerHtmlUrl":31,"ownerBlogUrl":32,"ownerDescription":33,"updatedAt":34,"install":35,"resources":48},"01M7DNBMEHS4ZYVQCZTDQAM69H","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.","DragonBallerZ\u002Fdragon-ide","DragonBallerZ","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F199459338?v=4","01M7DN83GSDPNQH3ACEV21SKTQ","Z McDragon","01M7DN83HDR4KMJAMTCB5S4DCJ",12,"MIT","https:\u002F\u002Fgithub.com\u002FDragonBallerZ\u002Fdragon-ide\u002Fblob\u002Fmain\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`** — read for ownership and interface contracts. Update it only when those contracts change; behavior and regressions belong in focused tests.\n\n## Key Folders\n\n| Folder | What |\n|--------|------|\n| `src\u002Fvs\u002Fworkbench\u002Fcontrib\u002Fchat\u002Fcommon\u002F` | `ICustomizationHarnessService`, `ISectionOverride`, `ICustomizationItemProvider` — shared interfaces |\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 harness behavior declaratively (hidden sections, button overrides, item providers, agent gating). See spec for the stable ownership contract.\n- **`ISectionOverride`** — per-section button customization (command invocation, root file creation, type labels, file extensions).\n- **`ICustomizationItemProvider`** \u002F **`ICustomizationItem`** — 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 `ICustomizationItem` or `ICustomizationItemProvider` 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` | `ICustomizationItem` |\n\nWhen adding fields to `ICustomizationItem`, 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 typecheck-client && 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`** — read for ownership and interface contracts. Update it only when those contracts change; behavior and regressions belong in focused tests.\n\n## Key Folders\n\n| Folder | What |\n|--------|------|\n| `src\u002Fvs\u002Fworkbench\u002Fcontrib\u002Fchat\u002Fcommon\u002F` | `ICustomizationHarnessService`, `ISectionOverride`, `ICustomizationItemProvider` — shared interfaces |\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 harness behavior declaratively (hidden sections, button overrides, item providers, agent gating). See spec for the stable ownership contract.\n- **`ISectionOverride`** — per-section button customization (command invocation, root file creation, type labels, file extensions).\n- **`ICustomizationItemProvider`** \u002F **`ICustomizationItem`** — 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 `ICustomizationItem` or `ICustomizationItemProvider` 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` | `ICustomizationItem` |\n\nWhen adding fields to `ICustomizationItem`, 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 typecheck-client && 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","af285532414d1fa855b4360d86103c12253e6f2f",".github\u002Fskills\u002Fchat-customizations-editor",0,"https:\u002F\u002Fgithub.com\u002FDragonBallerZ\u002Fdragon-ide","https:\u002F\u002Fgithub.com\u002FDragonBallerZ","https:\u002F\u002Fwww.velloralabs.com","Building Dangerously Disruptive Technology. ","2026-10-23 14:19:51",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add DragonBallerZ\u002Fdragon-ide --skill chat-customizations-editor",{"tool":41,"command":42},"bunx","bunx skills add DragonBallerZ\u002Fdragon-ide --skill chat-customizations-editor",{"tool":44,"command":45},"pnpm","pnpm dlx skills add DragonBallerZ\u002Fdragon-ide --skill chat-customizations-editor","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FDragonBallerZ\u002Fdragon-ide\u002Fblob\u002Fmain\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},"01M7DNGQPVJGHW226R8PS3R31F","update-skills","Create or update repository skills and instructions when major learnings are discovered during a session. Use when the user says \"learn!\", when a significant pattern or pitfall is identified, or when reusable domain knowledge should be captured for future sessions.","https:\u002F\u002Fgithub.com\u002FDragonBallerZ\u002Fdragon-ide\u002Fblob\u002Fmain\u002Fsrc\u002Fvs\u002Fsessions\u002Fskills\u002Fupdate-skills\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},"01M7DNGP5XJWV3CG63DVS6NR8Y","update-pr","Update the pull request for the current session. Use when the user wants to push new changes to an existing PR.","https:\u002F\u002Fgithub.com\u002FDragonBallerZ\u002Fdragon-ide\u002Fblob\u002Fmain\u002Fsrc\u002Fvs\u002Fsessions\u002Fskills\u002Fupdate-pr\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},"01M7DNGJEMNJZR24NBJ7MF5V8R","troubleshoot","Investigate unexpected behavior in the current Copilot agent session by analyzing its event log. Use when the user asks why something happened, why a request was slow, why a tool was or was not used, or why instructions\u002Fskills\u002Fagents did not load.","https:\u002F\u002Fgithub.com\u002FDragonBallerZ\u002Fdragon-ide\u002Fblob\u002Fmain\u002Fsrc\u002Fvs\u002Fsessions\u002Fskills\u002Ftroubleshoot\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},"01M7DNGFVCVMFN5J4ZKV27CDR1","sync","Sync the current session branch with its upstream branch, or publish the current session branch to a remote. Use when the user asks to sync a branch, pull latest changes, rebase onto upstream, push current branch, publish branch, or set upstream.","https:\u002F\u002Fgithub.com\u002FDragonBallerZ\u002Fdragon-ide\u002Fblob\u002Fmain\u002Fsrc\u002Fvs\u002Fsessions\u002Fskills\u002Fsync\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},"01M7DNGC9GE8EKQED3ZR3KAJ0K","sync-upstream","Update a stale session branch by rebasing onto the latest origin. Use when the upstream has moved significantly and the session needs to catch up, resolving conflicts by preserving upstream changes and adapting session work to fit.","https:\u002F\u002Fgithub.com\u002FDragonBallerZ\u002Fdragon-ide\u002Fblob\u002Fmain\u002Fsrc\u002Fvs\u002Fsessions\u002Fskills\u002Fsync-upstream\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},"01M7DNG9NJNG1QPJB6C3GFDHVS","merge","Merge changes from the topic branch to the merge base branch. Use when the user wants to merge their session's work back to the base branch.","https:\u002F\u002Fgithub.com\u002FDragonBallerZ\u002Fdragon-ide\u002Fblob\u002Fmain\u002Fsrc\u002Fvs\u002Fsessions\u002Fskills\u002Fmerge\u002FSKILL.md",[],[]]