Compétence d'accessibilité principale pour VS Code. OBLIGATOIRE pour les nouvelles fonctionnalités et les contributions, et s'applique également aux mises à jour de l'interface utilisateur existante. Couvre les boîtes de dialogue d'aide à l'accessibilité, les vues accessibles, les paramètres de verbosité, les signaux, les annonces ARIA, la navigation au clavier et les étiquettes/rôles ARIA.
Cette compétence est essentielle pour tout développeur travaillant sur VS Code, qu'il s'agisse de créer de nouvelles fonctionnalités ou de contribuer au projet. Elle garantit que toutes les modifications apportées à l'interface utilisateur respectent les normes d'accessibilité, ce qui est crucial pour les utilisateurs handicapés. Elle couvre un large éventail de pratiques, depuis la mise en œuvre de boîtes de dialogue d'aide accessibles et de paramètres de verbosité jusqu'à l'utilisation correcte des annonces ARIA et de la navigation au clavier. En suivant les directives de cette compétence, les développeurs s'assurent que leur code est inclusif et conforme aux meilleures pratiques d'accessibilité, améliorant ainsi l'expérience utilisateur pour tous.
npx skills add https://github.com/microsoft/vscode/tree/main/skills/accessibilityCompétence d'accessibilité principale pour VS Code. OBLIGATOIRE pour les nouvelles fonctionnalités et les contributions, et s'applique également aux mises à jour de l'interface utilisateur existante. Couvre les boîtes de dialogue d'aide à l'accessibilité, les vues accessibles, les paramètres de verbosité, les signaux, les annonces ARIA, la navigation au clavier et les étiquettes/rôles ARIA.
This repo contains 10 individual skills — each has its own dedicated page.
Agents workbench layout — covers the fixed layout structure, grid configuration, part visibility, editor modal, titlebar, sidebar footer, and implementation requirements. Use when implementing features or fixing issues in the Agents workbench layout.
Identify all files a specific author contributed to on a branch vs its upstream, tracing code through renames. Use when asked who edited what, what code an author contributed, or to audit authorship before a merge. This skill should be run as a subagent — it performs many git operations and returns a concise table.
Use when validating Azure DevOps pipeline changes for the VS Code build. Covers queueing builds, checking build status, viewing logs, and iterating on pipeline YAML changes without waiting for full CI runs.
Guidelines for fixing unhandled errors from the VS Code error telemetry dashboard. Use when investigating error-telemetry issues with stack traces, error messages, and hit/user counts. Covers tracing data flow through call stacks, identifying producers of invalid data vs. consumers that crash, enriching error messages for telemetry diagnosis, and avoiding common anti-patterns like silently swallowing errors.
Use when making code changes to ensure they pass VS Code's hygiene checks. Covers the pre-commit hook, unicode restrictions, string quoting rules, copyright headers, indentation, formatting, ESLint, and stylelint. Run the hygiene check before declaring work complete.
Audit code for memory leaks and disposable issues. Use when reviewing event listeners, DOM handlers, lifecycle callbacks, or fixing leak reports. Covers addDisposableListener, Event.once, MutableDisposable, DisposableStore, and onWillDispose patterns.
Agents window architecture — covers the agents-first app, layering, folder structure, chat widget, menus, contributions, entry points, and development guidelines. Use when implementing features or fixing issues in the Agents window.
Ensure renamed built-in tool references preserve backward compatibility. Use when renaming a toolReferenceName, tool set referenceName, or any tool identifier. Run on ANY change to tool registration code. Covers legacyToolReferenceFullNames for tools and legacyFullNames for tool sets.
Download screenshot baselines from the latest CI run and commit them. Use when asked to update, accept, or refresh component screenshot baselines from CI, or after the screenshot-test GitHub Action reports differences. This skill should be run as a subagent.
Use when reproducing a UI bug or verifying a fix by driving a real VS Code window end to end and capturing evidence. Writes a scenario file, runs it against a dev build or installed Insiders, and produces a captioned video, per-step screenshots, a Playwright trace, and an HTML report to attach to an issue or pull request.
ElevenLabs text-to-speech with mac-style say UX.
Oracle CLI second-model review/debug/refactor/design with selected files, dry-run token checks, API or browser engine.
Capture and automate macOS UI with the Peekaboo CLI.
Generate multiple radically different interface designs for a module using parallel sub-agents. Use when user wants to design an API, explore interface options, compare module shapes, or mentions "design it twice".
Build a throwaway prototype to flesh out a design — a runnable terminal app for state/business-logic questions, or several radically different UI variations toggleable from one route.
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".