Layout da bancada de agentes — abrange a estrutura fixa do layout, configuração de grade, visibilidade de partes, modal do editor, barra de título, rodapé da barra lateral e requisitos de implementação. Use ao implementar funcionalidades ou corrigir problemas no layout da bancada de agentes.
Este skill define o layout fixo e a estrutura da bancada de trabalho para agentes de IA, abrangendo a configuração de grade, visibilidade de partes, modal do editor, barra de título, rodapé da barra lateral e requisitos de implementação. Ele é útil para desenvolvedores que trabalham em ambientes como Claude Code, Cursor ou Codex, fornecendo uma base consistente para criar ou modificar interfaces de agente. O skill documenta como organizar visualmente os componentes da bancada, garantindo que partes como o editor, a barra lateral e o título sejam exibidas ou ocultadas corretamente. Ao seguir as diretrizes deste layout, os desenvolvedores podem implementar novos recursos ou corrigir problemas de interface de forma padronizada, mantendo a integridade estrutural da experiência do usuário do agente.
npx skills add https://github.com/microsoft/vscode/tree/main/skills/agent-sessions-layoutInstalled? Explore more Produtividade e Colaboração skills: steipete/gemini, steipete/gh-issues, steipete/skill-creator · View all 6 →
Layout da bancada de agentes — abrange a estrutura fixa do layout, configuração de grade, visibilidade de partes, modal do editor, barra de título, rodapé da barra lateral e requisitos de implementação. Use ao implementar funcionalidades ou corrigir problemas no layout da bancada de agentes.
This repo contains 10 individual skills — each has its own dedicated page.
Primary accessibility skill for VS Code. REQUIRED for new feature and contribution work, and also applies to updates of existing UI. Covers accessibility help dialogs, accessible views, verbosity settings, signals, ARIA announcements, keyboard navigation, and ARIA labels/roles.
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.
Gemini CLI one-shot prompts, summaries, generation, skills, hooks, MCP, or Gemma routing.
Fetch GitHub issues, select candidates, spawn background fix agents, open PRs, and optionally process PR review comments.
Create, edit, audit, tidy, validate, or restructure AgentSkills and SKILL.md files.
Search, install, update, sync, or publish agent skills with the ClawHub CLI and registry.
Delegate coding work to Codex, Claude Code, or OpenCode as background workers; not simple edits or read-only code lookup.
List, configure, authenticate, call, and inspect MCP servers/tools with mcporter over HTTP or stdio.