component-fixtures
Use when creating or updating component fixtures for screenshot testing or their shared infrastructure, or when designing UI components to be fixture-friendly. Covers fixture file structure, theming, service setup, CSS scoping, async rendering, validation, and common pitfalls.
Install
With your agent
Install OMGSkills skill "microsoft/vscode:component-fixtures" into this agent's normal skills directory: call the OMGSkills MCP get_install_plan tool for your agent and run the script it returns (it installs only the pinned commit and verifies SKILL.md), and stop if MCP or the pin is unavailable. Do not overwrite or change existing skills without asking me.
Manual command
git clone https://github.com/microsoft/vscode /tmp/vscode && ln -s /tmp/vscode/.github/skills/component-fixtures ~/.claude/skills/component-fixturesFrom README
Component Fixtures Component fixtures render isolated UI components for visual screenshot testing via the component explorer. Fixtures live in src/vs/workbench/test/browser/componentFixtures/ and are auto-discovered by the Vite dev server using the glob src//.fixture.ts. Use tools mcpcomponent-exp to list and screenshot fixtures. If you cannot see these tools, inform the user to them on. Running Fixtures Locally Start the component explorer server: run the Component Explorer Server task Use the mcpcomponent-explistfixtures tool to see all available fixtures and their URLs Use the mcpcomponent-expscreenshot tool to capture screenshots programmatically File Structure Each fixture file exports a default defineThemedFixtureGroup(...). The file must end with .fixture.ts.
More from this repo
agent-host-logs
Used to analyze Agent Host debug log exports.
chat-customizations-editor
Used when working on the Chat Customizations editor — the management UI for agents, skills, instructions, hooks,...
act-on-feedback
Act on user feedback attached to the current session.