测试设计、漏洞检测、质量保证（1.4万 个）
Updates tdmcp docs and roadmap for newly shipped or newly merged capabilities. Use when asked to update docs, update the roadmap, reconcile release docs, document new features, sync docs with CHANGELOG/package release, refresh cookbook examples after a feature wave, re-run/continue/fix a docs-roadmap pass, or check whether docs/ROADMAP.md is current. Runs a sub-agent workflow: release audit -> roadmap/docs edit + cookbook sync -> QA.
中文简介正在准备中。当前显示原文说明。
Plan and implement native RayTK (t3kt/raytk) raymarching/SDF toolkit integration into tdmcp — beyond the existing package-manager staging, into AI-driven RayTK operator (ROP) node graphs. Use whenever the user wants to build, plan, design, implement, continue, fix, QA, or ship RayTK support: create/wire RayTK ROPs, a RayTK operator knowledge catalog, a RayTK-native raymarch/SDF scene tool, RayTK recipes, or the RayTK setup/doctor flow — including follow-ups (re-run, continue, refresh after a new RayTK release, re-QA, docs). Also triggers on 'raytk', 'raymarching toolkit', 'SDF toolkit', 't3kt', 'montar um build para o raytk', 'integrar o raytk'. This owns RayTK integration specifically; use it before the generic tdmcp-pipeline for this feature. Simple questions about RayTK can be answered directly.
中文简介正在准备中。当前显示原文说明。
Restructure and enrich the tdmcp documentation site for artists — categorized/collapsible sidebar (EN+PT), interactive goal-based guide home, new step-by-step tutorials, copy-prompt/level-badge components. Use whenever the user asks to make the docs more interactive, easier to navigate, better organized, add categories/subcategories, add tutorials, improve docs UX/IA, or for follow-ups: re-run, continue, fix QA findings, add one more tutorial, re-organize a section, or update the docs structure. NOT for syncing docs with a release (tdmcp-docs-roadmap-update) or cookbook entries (tdmcp-cookbook-examples).
中文简介正在准备中。当前显示原文说明。
Orchestrates the tdmcp feature team end-to-end: design/wireframe → build → integrate → QA → release. Use whenever the user wants to build, implement, develop, ship, or add one or more tdmcp features/tools/effects/controls/AI-prompts for TouchDesigner, or to run them through a coordinated design→develop→QA→deploy pipeline. Also use for follow-ups: re-run, continue, update, fix, or improve a feature/batch, ship the next version, or rebuild just one part of a previous run. Single feature or a whole batch.
中文简介正在准备中。当前显示原文说明。
Run or maintain the full tdmcp repo quality-audit team: command sweeps, all package/Makefile/CI gates, security review, usability/flow review, refactor/test-gap analysis, coverage hardening, QA, and follow-up fix waves. Use whenever the user asks for a complete audit, improve repo/code quality, test all commands, find security/usability failures, refactor debt, add missing tests, re-run the audit, continue a previous quality wave, or verify the repo is ready.
中文简介正在准备中。当前显示原文说明。
Drive the ENTIRE tdmcp roadmap-to-1.0 to completion as a resumable, wave-by-wave campaign — Milestone 4 (generative-AI bridge wave), Milestone 5 (mixer scene arming), and the v1.0 consolidation gates G1–G6 — routing each class of work to the right existing sub-harness. Use whenever the user wants to "implement everything / all the milestones / the whole roadmap / finish the road to 1.0", run the next milestone, close the consolidation gates, or build a long autonomous campaign across M4/M5/G1–G6. ALSO use for every follow-up: continue/resume the roadmap campaign, run the next wave, re-run a failed wave, fold in QA results, check campaign status, re-prioritize, or scope to one milestone/gate. This is the CAMPAIGN layer ABOVE tdmcp-pipeline / tdmcp-feature-lead / tdmcp-backlog-campaign — it sequences across MULTIPLE sub-harnesses (tools, mixer, coverage, docs, bridge, recipes, submission), which the generic backlog-campaign does not. For a SINGLE feature use tdmcp-pipeline; for one tool-shaped backlog file use tdmcp-backlog-campaign. Simple questions can be answered directly.
中文简介正在准备中。当前显示原文说明。
Drive a whole tdmcp feature BACKLOG to completion as resumable, wave-by-wave releases — the campaign layer ABOVE tdmcp-pipeline/tdmcp-feature-lead. Use whenever the user wants to implement an ENTIRE backlog or discovery file (e.g. _workspace/discovery*/FEATURE_BACKLOG*.md), 'all the features', many features across multiple releases, or a long autonomous build campaign, AND for every follow-up: continue/resume the campaign, run the next wave, re-run a failed wave, fold in QA results, or check campaign status. Backed by a ledger.json so re-running is idempotent (skips shipped work, resumes interrupted work) and resilient (retry-once then quarantine-and-continue). For a SINGLE feature or one small batch, use tdmcp-pipeline instead; this skill is for the whole ledger.
中文简介正在准备中。当前显示原文说明。
当用户想要在 WorkBuddy 上完成每日签到（获取签到积分）时使用此技能。若 WorkBuddy 未运行则自动启动，使用 Playwright 通过 CSS Selector 定位 DOM 元素并点击：先点击左下角用户菜单（class="user-menu"），等待 2 秒后，再点击「立即领取 →」按钮（class="daily-checkin-banner-action"）完成签到。触发关键词包括"签到"、"WorkBuddy签到"、"每日签到"、"打卡积分"等。
中文简介正在准备中。当前显示原文说明。
Use when writing or debugging C++HDL tests that mix C++ testbench models with Verilated RTL, especially reset ordering, register inputs, AXI4 responder wiring, eval sequencing, _assign/_strobe discipline, and avoiding C++/SystemVerilog simulation mismatches.
中文简介正在准备中。当前显示原文说明。
Audit a QDash branch, pull request, commit, or working-tree diff for documentation impact. Use when checking whether source changes require documentation updates or before finishing user-visible, API, configuration, deployment, or extension changes. Reports stale content, missing coverage, and broken examples; applies focused fixes only when requested. Do not use for a docs-only writing task, which belongs to the technical-docs skill.
中文简介正在准备中。当前显示原文说明。
[Deprecated] deploy safety merged. Use `cm-safe-deploy` instead.
中文简介正在准备中。当前显示原文说明。
[Deprecated] browser daemon overlap. Use `cm-browse` instead.
中文简介正在准备中。当前显示原文说明。
Use when starting any new project from scratch. Asks for project identity (name, GitHub org, Cloudflare account), detects project type, sets up design system, staging+production, i18n from day 1, SEO foundation, AGENTS.md manifest, test infrastructure, 8-gate deploy pipeline, and disciplined development workflows. Prevents wrong deploys, redundant repos, and technical debt from day 0.
中文简介正在准备中。当前显示原文说明。
Execute comprehensive client-side injection vulnerability assessments on web applications to identify XSS and HTML injection flaws, demonstrate exploitation techniques for session hijacking and credential theft, and validate input sanitization and output encoding mechanisms.
中文简介正在准备中。当前显示原文说明。
[Deprecated] quality gate now covers tests + canary. Use `cm-quality-gate` instead.
中文简介正在准备中。当前显示原文说明。
Use when translating, extracting, or mass-converting hardcoded strings to i18n t() calls. Enforces multi-pass batching, parallel-per-language dispatch, 8 audit gates, and HTML integrity checks. Battle-tested through 21+ batches and 12 bug categories from the March 2026 incidents.
中文简介正在准备中。当前显示原文说明。
Safe i18n: multi-pass batching, parallel-per-language dispatch, 8 audit gates, HTML integrity. Use for translating or mass-converting hardcoded strings to t() calls.
中文简介正在准备中。当前显示原文说明。
Use when you need visual QA, screenshots, or post-deploy smoke testing through a real browser with Playwright.
中文简介正在准备中。当前显示原文说明。
Use when implementing any feature or bugfix. Routes to the core Red-Green-Refactor loop, test quality guidance, rationalization handling, examples, or stuck-state recovery.
中文简介正在准备中。当前显示原文说明。
Use before any deployment or completion claim. Enforces test gates, evidence-based verification, and frontend safety checks. No deploy without passing. No claims without evidence.
中文简介正在准备中。当前显示原文说明。
Fallback local Playwright daemon for real-browser visual QA / screenshots / smoke. Use ONLY when the host platform has no native browser mode — prefer the host browser first.
中文简介正在准备中。当前显示原文说明。
Audit websites and landing pages for conversion issues and design evidence-based A/B tests. Use when the user mentions "landing page isn't converting", "conversion rate", "A/B test", "why visitors leave", or "objection handling". Covers funnel mapping, persuasion assets, and objection/counter-objection frameworks. For overall marketing strategy, see one-page-marketing. For usability issues, see ux-heuristics.
中文简介正在准备中。当前显示原文说明。
Bootstrap any new project: identity, design system, staging+production, i18n, SEO, test infrastructure, 8-gate deploy pipeline. Prevents tech debt from day 0.
中文简介正在准备中。当前显示原文说明。
Use to run the full sprint pipeline: brainstorm → plan → design → tdd → build → review → qa → security → ship → monitor → retro.
中文简介正在准备中。当前显示原文说明。