Use Component Explorer

microsoft/vscode-team-kit/component-explorer/skills/use-component-explorer

Multi-file

designOfficial

Official Provider SkillView repo

Write and update component explorer fixtures for UI work — fixtures, screenshots, visual testing. USE FOR: "create a fixture for a component", "add fixture groups or variants", "screenshots or visual testing of UI", "adding or changing UI in a component explorer project". DO NOT USE FOR: "set up or install the component explorer", "write a unit test with a test runner".

Files2 files

SKILL.md341 lines

Loading editor…

Install

Recommended

One command — your agent picks it up automatically.

Select AI agent

Select an AI agent above to see the install command.

Manual Install

More steps

Download the archive and add the files to your project manually.

Skill details

Versionv1.0.0

AuthorMicrosoft

Categorydesign

Skill IDmicrosoft/vscode-team-kit/component-explorer/skills/use-component-explorer

Files2 files

Related skills

Build HealthAnalyze VS Code rolling build health on Azure DevOps. Use when: the rolling build is red right now, you need a report for the last 100 builds, you need to identify the commit range that broke the build, you are on build champ duty, or you need a build health report.Council PlanMulti-model council planning for implementation and architecture decisions. USE FOR: "plan with council", "multi-model plan", "different perspectives on an approach", "multiple models propose plans independently", "debate approaches or compare strategies", "cross-plan a synthesis". DO NOT USE FOR: "review a diff or pull request", "answer a quick factual question".Council ReviewMulti-model council review for diffs, pull requests, and risky changes — CRITICAL after non-trivial development. USE FOR: "review a diff or pull request", "bug hunt in recent edits", "multiple models inspect the same change independently", "cross-review or debate findings between models", "review after any non-trivial development phase". DO NOT USE FOR: "plan a new implementation", "write code without a review".DebugDebug runtime-dependent bugs by generating competing hypotheses, adding temporary structured-log probes, collecting local evidence, and applying only an evidence-backed fix. Use for intermittent or timing-sensitive bugs, races, frontend/backend interaction failures, runtime-state issues, repeated speculative-fix failures, or explicit requests to instrument and collect evidence. Not for breakpoints, stepping, or variable inspection.Follow GoalGive the agent a durable objective with a verifiable stopping condition, then keep iterating across turns until that condition is met. Use when the user says 'set a goal', 'follow a goal', '/goal …', 'keep working until …', or asks for a long-running task with a clear end state (migrations, large refactors, retry-until-green loops, experiments).GoalSet, inspect, or control a durable goal — the agent keeps iterating across turns until the stop condition is met.