Build a single tdmcp tool from a specification with Zod schema and msw tests.
npx skills add https://github.com/Pantani/tdmcp --skill td-feature-build
Please help me install this Agent Skill. Skill: td-feature-build Source: https://github.com/Pantani/tdmcp/tree/main/.agents/skills/td-feature-build Command: npx skills add https://github.com/Pantani/tdmcp --skill td-feature-build
Build isolation for tool development: implement a new tdmcp tool from a full specification while touching only new files, ensuring changes are self-contained and safe to develop in parallel without modifying shared registries.
…Impl and a register… function together with a bridge payload script and offline msw unit tests, enabling isolated, repeatable builds.Create a new tool file following the canonical pattern and implement a focused unit test in isolation.
High-intent search queries and answers about installing and using this skill.
To build isolated tdmcp tools, you implement new tool files following a canonical pattern with a Zod schema, implementation function, bridge payload, and offline msw unit tests, ensuring strict isolation for parallel development without touching shared registries.
The canonical tdmcp tool-file pattern exports a pure implementation function and a register function together with a bridge payload script and offline msw unit tests, enabling isolated, repeatable builds for each tool.
You scaffold a TypeScript MCP tool by creating a new file containing a Zod schema, an implementation function, a bridge payload, and an offline msw unit test, yielding a self-contained, exportable tool ready for integration.
Yes, you can develop multiple tdmcp tools in parallel because the isolation approach enforces new-file discipline and requires no edits to shared registries or core tooling, preventing conflicts during concurrent feature development.
Yes, tdmcp tool isolation works with msw by supplying an offline msw unit test within each new tool file, allowing you to validate the implementation in a self-contained environment before integration.
You should avoid the isolated tool-file pattern when your task requires modifying existing shared registries or core tooling, as this approach enforces strict new-file discipline and does not support editing shared dependencies.
bingeli1379Generate proposal, design, specs, and tasks artifacts using SDD and DDD patterns.
PantaniCoordinate design, build, integrate, QA, and release stages for TouchDesigner feature delivery.
martinffxProvide Vitest, MSW, and typed mock patterns for TypeScript unit tests.
mrkhachaturovCreate isolated git worktrees for parallel feature development.