t-design

Generate technical designs with API interfaces, data models, and integration points.

64|6|Updated Apr 17, 2026
One-click install
npx skills add https://github.com/timzaak/web-dev-skills --skill t-design
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: t-design
Source: https://github.com/timzaak/web-dev-skills/tree/main/skills/t-design
Command: npx skills add https://github.com/timzaak/web-dev-skills --skill t-design

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generating consistent, production-ready technical designs from scattered PRD, user stories, and technical research, ensuring alignment across architecture and implementation.

Core Features & Use Cases

  • Generate API design, database schema, and implementation details for a feature.
  • Reference PRD drafts, user stories, and tech research to derive scope, constraints, and acceptance criteria.
  • Produce design artifacts compatible with the /t-design workflow and the design template.

Quick Start

Create a complete technical design document for a feature using PRD drafts, tech research, and existing code.

Frequently Asked Questions about t-design

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

FAQPage Schema
How do I generate a technical design document from PRD drafts and user stories?

Generating a technical design document from PRD drafts involves leveraging user stories and tech research to define API interfaces, data models, and integration points. This process ensures alignment across architecture and implementation by specifying scope, constraints, and verification criteria.

What is the best way to structure API design and database schema for a new feature?

The best way to structure API design and database schema is to produce comprehensive design artifacts that capture data models and integration points. This approach derives scope and constraints directly from existing PRD drafts and technical research.

Can I use existing tech research to define verification criteria and testing strategy?

Yes, you can use existing tech research to define verification criteria and testing strategy. The technical design process specifies testing strategies, risks, and acceptance criteria by citing source documents like PRD drafts and user stories.

Does technical design generation work without predefined architecture dependencies?

Technical design generation works without predefined architecture dependencies by extracting scope and constraints directly from provided PRD drafts and user stories. It focuses on defining integration points and design artifacts independently.

What limitations exist when creating technical designs from scattered requirements?

A limitation when creating technical designs from scattered requirements is ensuring consistent alignment across architecture and implementation. Without structured source documents like tech research and user stories, deriving accurate acceptance criteria and design artifacts becomes difficult.