td-guide

Name: td-guide
Availability: InStock
Author: guigpap

Define structured TouchDesigner network building and debugging with MCP and Claude.

1|Updated Mar 18, 2026

Search Tags:#debugging #mcp #network-design #touchdesigner #operator-patterns #td-guide

Ready to run

npx skills add https://github.com/GuiGPaP/TD_starter_pack --skill td-guide

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: td-guide
Source: https://github.com/GuiGPaP/TD_starter_pack/tree/main/.agents/skills/td-guide
Command: npx skills add https://github.com/GuiGPaP/TD_starter_pack --skill td-guide

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

TouchDesigner workflows can be intricate and error-prone when coordinating operator layouts, rendering pipelines, and MCP-powered automation; this guide provides a structured framework to help users build, reason about, and maintain reliable TD networks with Claude-driven interactions.

Core Features & Use Cases

Establishes consistent patterns for operator creation, layout, and data routing across SOP/POP/TOP/DAT/COMP, enabling scalable network design.
Covers project indexing, per-node context access, and shader/workflow guidance (td-glsl/td-python) to streamline development and debugging.
Use cases include building repeatable TD projects, diagnosing operator errors, and enabling MCP-based automation and exploration with Claude.

Quick Start

Use this guide to start building a TouchDesigner workflow managed by MCP and Claude.

Frequently Asked Questions about td-guide

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I debug TouchDesigner networks using MCP and Claude?▼

Debugging TouchDesigner networks with MCP and Claude requires a structured approach that enforces guardrails, reference usage, and API patterns to ensure safe, repeatable project diagnosis across operator families.

What is the best way to structure TouchDesigner operator layouts for automation?▼

The best way to structure TouchDesigner operator layouts for automation is to apply consistent patterns for operator creation, layout, and data routing across SOP, POP, TOP, DAT, and COMP families to enable scalable network design.

Can I use MCP to manage TouchDesigner shader workflows and project indexing?▼

Yes, MCP can manage TouchDesigner shader workflows and project indexing by providing per-node context access, td-glsl and td-python shader guidance, and structured project indexing to streamline development and exploration with Claude.

How does per-node context retrieval work in TouchDesigner MCP automation?▼

Per-node context retrieval in TouchDesigner MCP automation works by indexing project structures and applying reference usage and API patterns, allowing Claude to access specific node contexts for accurate reasoning and debugging.

Do I need specific API patterns to build repeatable TouchDesigner projects with Claude?▼

Yes, building repeatable TouchDesigner projects with Claude requires enforcing specific API patterns and guardrails to coordinate operator layouts, rendering pipelines, and MCP-powered automation safely across all operator families.

Why does my TouchDesigner network fail when coordinating rendering pipelines with MCP?▼

TouchDesigner networks fail when coordinating rendering pipelines with MCP due to error-prone workflows lacking structured frameworks; applying consistent operator patterns, project indexing, and guardrails resolves these coordination issues.