tdmcp: Instructions file for Codex

@/Users/pantani/.codex/RTK.md

Harness: repo quality audit

• When asked for a complete audit, to test all commands, improve repo/code quality, find security/usability/flow failures, identify refactors, add missing tests, continue a previous audit, or verify whether the repo is ready, use the tdmcp-quality-audit skill.
• The quality team is defined in .claude/agents/ and mirrored for Codex in .codex/agents/; the skill is mirrored in .claude/skills/tdmcp-quality-audit/ and .agents/skills/tdmcp-quality-audit/.
• Keep findings evidence-backed with PASS / FAIL / UNVERIFIED buckets, and do not report TouchDesigner or hardware-dependent checks as passing unless they were actually run.

Visual layout integrity

• Never allow accidental overlap between UI elements, generated project components, nodes, cards, controls, text, canvases, media, or visual assets.
• When creating new projects, tools, docs previews, dashboards, diagrams, or frontend screens, keep the composition organized with explicit spacing, stable grids or flex layouts, responsive constraints, and predictable stacking order.
• Treat any element that covers, invades, clips, or visually competes with another as a defect to fix before delivery, unless the overlap is explicitly requested and intentionally designed.
• Verify relevant desktop, mobile, or preview states when a change affects visual layout.

TouchDesigner node layout

• Never create TouchDesigner operators, COMPs, generated project components, or bridge-managed nodes in a stacked pile. This applies inside tdmcp_bridge, inside every generated container, and to any node created through Layer 1, Layer 2, Layer 3, recipes, bridge endpoints, raw Python snippets, docs examples, or tests.
• Every operator creation path must assign explicit, deterministic layout coordinates immediately after creation (nodeX/nodeY or the local equivalent). Do not rely on TouchDesigner's default drop position, inherited cursor position, or repeated 0,0 placement.
• Arrange generated networks by clear roles and data flow: inputs/control nodes on the left or top, processing chains in ordered rows or columns, outputs/previews on the right or bottom, with enough spacing that names, viewers, flags, and parameter panels remain readable.
• Use stable spacing constants, grid helpers, or existing auto-layout helpers when creating multiple nodes. If a tool creates a variable number of nodes, compute positions from indexes and roles so the layout remains organized at every count.
• Treat duplicate or near-duplicate node coordinates, clipped node labels, or visually crowded generated networks as defects. Fix the layout before reporting the work complete.
• When changing any node-creation code, verify the resulting TouchDesigner network layout by inspecting coordinates, running the relevant layout helper/test, or checking a live/preview network when available.