테스트 설계, 취약점 진단, 품질 보증 (1.3만건)
Orchestrates the dedicated Kinect wall harp implementation team. Use whenever the user asks to build, implement, continue, fix, QA, document, or ship the Kinect wall harp, Kinect v2 wall-depth harp, FreenectTD depth-blob hand tracking, projected wall strings, pluck synth harp, or this feature's Layer 1 tool/recipe/docs. Use this before the generic tdmcp-pipeline for this feature.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Release tdmcp: write the Keep-a-Changelog entry, bump the SemVer version across every manifest, then (autonomously, per project policy) commit, tag, and push — gated on a td-qa PASS, with hard git safety rails. Use when releasing/shipping/cutting a tdmcp version, writing the CHANGELOG, bumping the version, or tagging a release.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Verification methodology and gate checklist for the tdmcp Connectors Directory submission — run the docs build, build and inspect the .mcpb bundle, sweep for stale .dxt references, and cross-check the form-answer draft against the real requirements. Use to validate the submission package before a human submits, by executing commands and quoting evidence, not by trusting that work was done.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Quality-assure integrated tdmcp features: run the four PR gates + recipe/bridge tests, cross-boundary coherence checks (tool schema↔CLI↔docs↔registry, operator↔createable, bridge↔client), and live TouchDesigner validation (preview + post-cook error check) when the bridge is reachable. Use when validating/QA-ing/testing tdmcp tools, checking a feature actually cooks in TD, verifying CLI matches a tool, or gating a release.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Implement ONE tdmcp tool from a spec — the canonical file pattern (Zod schema + …Impl + register… ToolRegistrar), a bridge Python payload via buildPayloadScript, and an offline msw unit test — touching only new files, never shared registries. Use when coding/implementing/writing a tdmcp tool, generator, effect, control, CHOP/TOP/SOP builder, or Python bridge work, especially when several features are built in parallel.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Build a tdmcp TouchDesigner-bridge vertical slice the house way — promote an op from /api/exec to a first-class REST endpoint (e.g. POST /api/connect, GET /api/logs, node_detail flags), add its typed method in src/td-client/touchDesignerClient.ts, its Zod envelope in src/td-client/validators.ts, rewire the tool(s) to prefer the endpoint with an exec fallback, and write py_compile + td/tests unittest + offline msw client tests. Use when adding/changing a bridge REST endpoint, editing td/, extending node_detail/get_bridge_logs, promoting connect/disconnect/param-modes/DAT-text off exec, or doing any exec→REST work — especially the td-depth bridge-robustness backlog. Honors probe-live discipline when TouchDesigner is offline.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Orchestrates the tdmcp Anthropic Connectors Directory (Desktop Extension / MCPB) submission prep — designs the package, writes the privacy page, migrates .dxt→.mcpb, drafts all form answers, and QAs the result. Use for ANY work on the tdmcp directory/marketplace submission, including re-runs after a rejection ("update the submission", "redo the form answers", "re-migrate the bundle", "fix the privacy page", "the directory rejected us"). Drives a 4-agent pipeline (architect → docs-author ∥ bundle-engineer → QA).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Turn a GitHub issue into a tested fix on a branch with an open PR: read the issue as the contract, find the root cause, write the failing test first, fix, prove it, review the diff against the issue, push and open the PR only after GO. Merging stays with pb-ship. Use for "fix issue 42", "bug fix from this issue", "turn this issue into a PR".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Comprehensive guide to auditing web content against WCAG 2.2 guidelines with actionable remediation strategies.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
To test local web applications, write native Python Playwright scripts.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Run a security sweep over one repo: secrets, dependencies and the diff, a security review and a silent-failure hunt, one deduped and ranked findings report, issues filed for blocking findings only after GO, each one handed to pb-bug-fix. Use for "security sweep", "audit this repo", "check for leaked secrets and vulnerable deps".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when implementing any feature or bugfix, before writing implementation code
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Diagnose and audit SEO issues affecting crawlability, indexation, rankings, and organic performance.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when implementing, integrating, upgrading, debugging, or answering anything involving third-party APIs, libraries, frameworks, CLIs, cloud services, model or provider SDKs, fast-moving product behavior, unfamiliar repo docs or specs, errors that may indicate API drift, or high-stakes auth, security, billing, data, migration, deployment, compliance, or privacy behavior. Forces a docs pass before coding from memory.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
A relentless interview to sharpen a plan or design before committing to an approach. Use on any "grill me" or "grill this plan" trigger phrase, when the user asks to stress-test a decision, plan or design, and before handing a finished plan off to a startcycle run or a plan-canvas review.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
General-purpose browser automation skill. Use when a task needs custom Playwright code — end-to-end testing, scraping a JS-rendered page, or driving a browser interactively — executed via this skill's universal executor rather than a one-off script.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Expert capability for robust, stealthy, and efficient browser automation using Playwright Go.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Experimental workflow for auditing recurring feedback, telemetry, errors, and brittle delivery paths to find systemic fixes. Use for periodic or requested cross-source lookbacks, not routine single-item intake.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when facing 2+ independent tasks — "in parallel", "independent tasks", "multiple unrelated failures", "different test files or subsystems" — that can be worked on without shared state or sequential dependencies. Dispatch one agent per independent slice, each with only the context it needs, even when the user did not ask for subagents explicitly.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Comprehensive security auditing, diff analysis, defensive checklists, and vulnerability testing.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.