菜单
Use when a task involves a design spec, ADR, one-way-door decision, or evaluating trade-offs between architectural approaches for the VS Code extension. Invoke before implementation when requirements span modules or a decision is hard to reverse. Trigger: /architect.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
Use when the extension adopts a new technology (a library, framework, protocol, or service — e.g. Solr, a language server, a webview UI framework) and you want reusable per-technology expertise. Generates a path-scoped rule + a specialist agent (+ optional skill) so future tasks get current, project-specific guidance on that tech. Trigger: /add-tech-specialist.
Use when writing code, fixing a bug, implementing a feature, or improving code structure in the VS Code extension. Invoked for typed implementation work inside `src/`, `src/test/`, build config, or other source surfaces. Trigger: /builder.
Use for code review, quality audits, SOLID/DRY consistency checks, pattern audits across the VS Code extension codebase, lint/type-check, or verifying anti-pattern compliance across a scope. Trigger: /code-check.
Use when the user says "commit", "/commit", "save progress", or asks to land working changes on a feature branch. Working-phase posture — minimises commit count, can amend rolling Checkpoints, offers a one-time PR prompt. Conventional Commits.
Use when designing test suites, writing integration/acceptance tests, validating an implementation against a spec, or planning test coverage before implementation for the VS Code extension. Trigger: /qa-engineer.
| name | architect |
| description | Use when a task involves a design spec, ADR, one-way-door decision, or evaluating trade-offs between architectural approaches for the VS Code extension. Invoke before implementation when requirements span modules or a decision is hard to reverse. Trigger: /architect. |
Role: system design, technical specs, and high-level architecture decisions for the OCX VS Code extension.
worker-explorer (parallel). Map current module state, find reusable code, trace activation/command flows.tech-*.md and subsystem rules. Read explorer findings..claude/artifacts/research_*.md. For a brand-new technology, consider /add-tech-specialist..claude/templates/artifacts/..claude/rules/quality-typescript.md — TS strict baseline, module system (auto-loads on *.ts).claude/rules/tech-vscode-api.md — VS Code API model, activation, disposables, contributes (if present).claude/rules/tech-esbuild.md — bundling contract (if present).claude/rules/product-tech-strategy.md — golden-path tech choices.claude/rules/product-context.md — extension positioning and vision (if present)mcp__context7__resolve-library-id + get-library-docs) — current API shape (@types/vscode, esbuild, test tooling) when a decision hinges on "what does X look like today". Training-data API knowledge decays fast. Fallback: WebFetch of official docs.mcp__github__*) — structured lookup of issues, PRs, releases during discovery. Fallback: gh CLI.Create in .claude/artifacts/:
adr_[topic].md — Architecture Decision Recordsdesign_spec_[component].md — feature/component design specsplan_[task].md — implementation plansspecialist-*) — for deep API questions; /add-tech-specialist to create one$ARGUMENTS