td-feature-design

Convert tdmcp feature ideas into implementable design specifications with Zod schemas.

30|6|Updated May 25, 2026
One-click install
npx skills add https://github.com/Pantani/tdmcp --skill td-feature-design
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: td-feature-design
Source: https://github.com/Pantani/tdmcp/tree/main/.agents/skills/td-feature-design
Command: npx skills add https://github.com/Pantani/tdmcp --skill td-feature-design

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Design teams often struggle to translate a nascent idea for a tdmcp feature into a concrete, implementable spec. This Skill provides a repeatable template that captures scope, interfaces, inputs, topology, bridging strategy, UI layout, risk assessment, and verification plans before any code is written.

Core Features & Use Cases

  • Capture layer target (Layer1/Layer2/Layer3) and compute the exact file path for implementation.
  • Define a Zod input schema for the feature's parameters, outline the TD network topology, and specify the bridge/Python approach.
  • Draft a UI wireframe if the feature exposes a control panel or web interface.
  • List probe-first risks, test plan, and integration notes.
  • Produce a single design artifact compatible with repository conventions, enabling a one-file implementation and test.

Quick Start

Provide a complete design document template for a new tdmcp feature, including layer choice, input schema, network topology, bridge approach, UI wireframe, risks, tests, and integration notes.

Frequently Asked Questions about td-feature-design

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

FAQPage Schema
How do I convert a feature idea into an implementable design specification?

A design specification bridges ideation and implementation by defining Zod input schemas, network topology, bridge approaches, and test plans, ensuring engineers and AI models can execute the feature directly from the document.

What should a feature design document include for one-file implementation?

It must capture layer choices, input schemas, topology, bridging strategy, UI layouts, risk assessments, and verification plans to produce a single design artifact suitable for direct execution and testing.

How do I structure a design doc for new UI components across multiple layers?

Specify the layer target, compute implementation file paths, outline network topology, and draft UI wireframes for control panels to ensure the design doc covers all necessary architectural details.

Can I define a Zod input schema and network topology before coding a feature?

Defining Zod input schemas and TD network topology beforehand allows teams to detail parameters, bridging approaches, and integration notes, creating a concrete artifact ready for engineering execution.

What is the best way to assess risks and test plans for feature design?

Listing probe-first risks, detailing test plans, and specifying integration notes in the design document ensures potential edge cases are addressed and verification plans are established early.

Does generating a feature spec require prior knowledge of repository conventions?

Adhering to repository conventions is necessary when generating a feature spec so the single design artifact can be directly handed to an engineer and an AI model for execution without integration friction.