accessibility은(는) 무엇을 하나요?
VS Code를 위한 기본 접근성 스킬입니다. 새로운 기능 및 기여 작업에 필수이며, 기존 UI 업데이트에도 적용됩니다. 접근성 도움말 대화상자, 접근 가능한 뷰, 상세 설정, 신호, ARIA 알림, 키보드 탐색 및 ARIA 레이블/역할을 다룹니다.
VS Code를 위한 기본 접근성 스킬입니다. 새로운 기능 및 기여 작업에 필수이며, 기존 UI 업데이트에도 적용됩니다. 접근성 도움말 대화상자, 접근 가능한 뷰, 상세 설정, 신호, ARIA 알림, 키보드 탐색 및 ARIA 레이블/역할을 다룹니다.
이 스킬은 VS Code에서 접근성 관련 작업을 수행하는 개발자와 AI 에이전트를 위한 필수 도구입니다. 새로운 기능 개발이나 기존 UI 업데이트 시 반드시 활성화되어야 하며, 접근성 도움말 대화상자, 접근 가능한 뷰, 상세 설정, 신호, ARIA 알림, 키보드 탐색 및 ARIA 레이블/역할 등 다양한 접근성 영역을 포괄합니다. 주로 VS Code 확장 및 코어 개발 환경에서 사용되며, SKILL.md 문서에 따라 명확한 지침을 제공하여 접근성 표준을 준수하도록 돕습니다. 이 스킬을 통해 AI 에이전트는 접근성 관련 코드 변경, UI 구성 요소 검토 및 접근성 문제 해결을 효과적으로 수행할 수 있습니다.
npx skills add https://github.com/microsoft/vscode/tree/main/skills/accessibilityVS Code를 위한 기본 접근성 스킬입니다. 새로운 기능 및 기여 작업에 필수이며, 기존 UI 업데이트에도 적용됩니다. 접근성 도움말 대화상자, 접근 가능한 뷰, 상세 설정, 신호, ARIA 알림, 키보드 탐색 및 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".