スキルを探す

Build and refine TouchDesigner projects with tdmcp using context-first, visible, reversible workflows.

日本語の概要は準備中です。原文の説明を表示しています。

Scout the TouchDesigner community for what's HYPED right now — community showcases, recent tutorials, generative-AI bridges, hardware interaction trends, visual-aesthetic trends of 2025-2026 — then propose tdmcp tools that ride those trends AND are easy to build. Use whenever the user wants to brainstorm new feature ideas based on what's trending in TouchDesigner, asks for 'hype' or 'trending' features, asks 'what are people doing in TD right now / what's hot / what's hype', wants tools inspired by community trends, asks to scout TD trends/aesthetics/integrations, or says things like 'ideias hype', 'novas ideias', 'o que está em alta', 'criar ferramentas para o que está bombando', 'tendências do TouchDesigner'. Also for follow-ups: refresh, rescout one surface, re-rank under another profile, deepen a trend, or filter for buildable-easy items. This is an EXTERNAL trend ideation harness — complementary to tdmcp-feature-discovery (which is INTERNAL gap analysis). It produces `_workspace/hype-scout/HYPE_TOOL_BACKLOG.md` ranked by Hype × Build-Ease; it does NOT build. Once a feature is chosen from the backlog, hand it to tdmcp-pipeline.

日本語の概要は準備中です。原文の説明を表示しています。

Orchestrate any tdmcp test-coverage work: run the coverage harness, inspect coverage gaps, plan focused Vitest/msw or bridge tests, delegate coverage writers, verify coverage deltas, and re-run gates. Use whenever the user asks to raise coverage, add broad regression coverage, create a test harness, improve tests, re-run a coverage wave, or fix a coverage gate.

日本語の概要は準備中です。原文の説明を表示しています。

Study a merged or shipped tdmcp implementation and extract reusable learnings: code improvements, runtime/UX lessons, test gaps, docs updates, roadmap items, and harness changes. Use when the user asks to learn from a completed feature/project/PR/build, analyze what can be improved from an implementation, or turn a real installation experience into actionable tdmcp improvements. This is a post-implementation learning harness; it does not replace tdmcp-pipeline for building or tdmcp-quality-audit for broad repo audits.

日本語の概要は準備中です。原文の説明を表示しています。

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.

日本語の概要は準備中です。原文の説明を表示しています。

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.

日本語の概要は準備中です。原文の説明を表示しています。

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.

日本語の概要は準備中です。原文の説明を表示しています。

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.

日本語の概要は準備中です。原文の説明を表示しています。

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).

日本語の概要は準備中です。原文の説明を表示しています。

How to author one new tdmcp MCP tool the house way — the file shape (XImpl + registerX), the Python-bridge pattern (buildPayloadScript/parsePythonReport over executePythonScript), the result helpers (errorResult/guardTd/jsonResult/structuredResult), fail-forward error handling, ESM/.js + Biome style, and the offline msw unit test that proves it. Load this whenever building, extending, reviewing, or testing a tdmcp tool file under src/tools/** (and its test under tests/unit/**). Use it for every Phase-13 / v0.5.0 feature-build tool and any re-run after a gate failure.

日本語の概要は準備中です。原文の説明を表示しています。

How to add a page to the tdmcp VitePress docs site so it builds, gets a clean URL, and lands in the right nav — including the repo's partial-translation convention (only the artist guide is EN+PT; reference/legal pages are English). Use when authoring the privacy policy or any new docs page for tdmcp.

日本語の概要は準備中です。原文の説明を表示しています。

Apply fail-closed consent, scope, undo, and verification rules to TouchDesigner mutations made with tdmcp.

日本語の概要は準備中です。原文の説明を表示しています。

Write focused tdmcp tests for one assigned coverage gap. Use for Vitest/msw unit tests, integration tests, bridge tests, CLI/config/resource tests, and regression tests that should raise coverage without weakening behavior.

日本語の概要は準備中です。原文の説明を表示しています。

Consolidate the five tdmcp surveyor reports into one prioritized FEATURE_BACKLOG.md — dedupe cross-surface overlaps, reconcile every candidate against the roadmap (NEW vs planned vs extension), rank by a selectable impact×effort weighting profile into P0/P1/P2 (high-confidence first), and emit per-surface tables + a recommended-next shortlist that hands straight to the build pipeline. Use when a td-synthesizer agent is consolidating surveys during the feature-discovery harness.

日本語の概要は準備中です。原文の説明を表示しています。

Consolidate the td-trend-scout reports under `_workspace/hype-scout/` into one prioritized HYPE_TOOL_BACKLOG.md — dedupe trends across surfaces, vet each candidate against the real tdmcp codebase (layer fit, operator coverage, bridge work), rank by Hype × Build-Ease, and emit a 'Ready for tdmcp-pipeline' top-5. Use when a td-hype-synthesizer agent is consolidating scouts at the end of the tdmcp-hype-scout harness.

日本語の概要は準備中です。原文の説明を表示しています。

Scout ONE external surface of the TouchDesigner community for what's HYPED in 2025-2026 that could become a tdmcp tool. Use when a td-trend-scout sub-agent is assigned a surface (community-showcase, tutorials, generative-ai, hardware-interactive, or vfx-aesthetics) during the tdmcp-hype-scout harness — produces `_workspace/hype-scout/01_scout_<surface>.md` with cited trend candidates ranked by hype intensity, recency, and build-ease in tdmcp.

日本語の概要は準備中です。原文の説明を表示しています。

Orchestrates the AI-Controlled Party mixer/Soundcraft Ui24R design team. Use whenever the user wants to design, update, refine, re-run, or implement-plan the Soundcraft Ui24R scene-arming expansion, mixer-aware AI party, operator-approved mixer cues, snapshots/cues/show control, Companion bridge, or any follow-up based on prior mixer design results. Produces a spec for tdmcp-pipeline; does not implement runtime code.

日本語の概要は準備中です。原文の説明を表示しています。

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.

日本語の概要は準備中です。原文の説明を表示しています。

Review, harden, and test the safety policy for AI-Controlled Party mixer/Soundcraft Ui24R scene arming. Use for approval gates, blocked mixer operations, hazardous request handling, venue validation, bypass attempts, QA, risk review, or follow-up safety changes.

日本語の概要は準備中です。原文の説明を表示しています。

Design the MixerSceneIntent, approval state, JSON schema, CLI examples, audit entries, and tests for AI-Controlled Party mixer/Soundcraft Ui24R scene arming. Use whenever a task mentions mixer scenes, Ui24R snapshots/cues, operator-approved mixer control, show-director contract updates, schema updates, dry-run CLI shape, or follow-ups that revise this contract.

日本語の概要は準備中です。原文の説明を表示しています。

Design the Soundcraft Ui24R adapter boundary for AI-Controlled Party: dry-run, Bitfocus Companion, direct Node bridge, connection health, config, failure handling, and live-validation gates. Use whenever a task mentions Soundcraft, Ui24R, snapshots, cues, Companion, soundcraft-ui-connection, mixer bridge, or revising the adapter design.

日本語の概要は準備中です。原文の説明を表示しています。

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.

日本語の概要は準備中です。原文の説明を表示しています。

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.

日本語の概要は準備中です。原文の説明を表示しています。