菜单
LSP-driven debugging patterns for TypeScript codebases. Complements the general debugging methodology in the harness `systematic-debugging` skill. Use in Phase 3-4 escalation scenarios or when investigating unexpected behavior.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use BEFORE any solo/low-blast creative work — designing a feature, component, behavior change, or this harness itself — to turn an idea into an approved design through a lightweight collaborative dialogue. The solo counterpart to /team-brainstorm (which owns multi-file / cross-cutting / product / architecturally-uncertain work). Harness-owned; do NOT invoke any external brainstorming skill.
6-phase verification system (+ an opt-in human comprehension quiz gate) with checkpoint support and pass@k metrics. Use in Phase 4-5 of team workflow, before creating PRs, or after completing feature implementations. Covers build, type check, lint, test, security scan, diff review, a human-understanding gate, checkpoints, and evaluation metrics.
Multi-agent team workflow orchestration with 5 phases, escalation loops, and TDD enforcement. Use when /team or /team-run commands are invoked. Coordinates Team Leader, Architects (FE/BE/Infra), UI/UX Master, Designers (TDD developers), and Testers through Planning → UI/UX → Gate → Implementation → Verification → Final Review.
Model routing (incl. per-agent Workflow / ultracode routing), effort levels, context efficiency, and compaction strategy. Use when spawning agents, authoring Workflow fan-outs, selecting models, choosing effort levels, or managing context window pressure.
Git worktree management, cascade method for multiple instances, and scaling guidelines. Use when planning parallel agent work, managing worktrees, or deciding when to scale instances.
Analyze project structure, conventions, and patterns to generate a project profile. Use when /team-init is invoked or when team agents need to understand the codebase. Scans package.json, config files, source code patterns, and test setup to produce structured profiles in .claude/project-profile/.
| name | debug |
| description | LSP-driven debugging patterns for TypeScript codebases. Complements the general debugging methodology in the harness `systematic-debugging` skill. Use in Phase 3-4 escalation scenarios or when investigating unexpected behavior. |
This skill covers LSP-accelerated debugging patterns specific to this harness. For the full systematic debugging methodology (reproduce → narrow → hypothesize → test), use the systematic-debugging skill.
systematic-debugging skill for the reproduction stephover to check inferred types against assumptionsincomingCalls / outgoingCalls to map the flowstack.md → "Build & Verify") + project test command; confirm no regression| Symptom | First LSP operation | Second (if needed) |
|---|---|---|
X is not a function | goToDefinition on X — is it exported? | findReferences — is everyone importing the same symbol? |
Cannot read property Y of undefined | hover on the object — what's the inferred type? | goToDefinition on the type — does it declare Y? |
| Type mismatch after refactor | findReferences on the changed type | goToImplementation on interfaces — any implementer missed? |
| Downstream code broken unexpectedly | incomingCalls on the changed function | Check each caller manually |
| Stale cache / wrong data | findReferences on store/query key | Confirm every call site uses the same key |
| Unfamiliar function signature | hover for signature | documentSymbol for neighboring helpers |
When a bug looks like a type-system or dependency-injection failure rather than ordinary logic — a cascading "property does not exist" flood, an intermittent context/i18n/inject crash, or an opaque deserialization error on a bulk request — read resources/ts-structural-traps.md BEFORE rewriting logic. These have non-obvious structural causes (inference cycles, context-scoped singleton init order, deserialization caps) with near-zero-runtime-change fixes; diagnosing them as logic bugs wastes hours.
systematic-debugging skill)stack.md → "Build & Verify") before declaring the fix completefindReferences to confirm no orphaned callersFor non-TypeScript investigation patterns, fall back to the systematic-debugging skill.