tds-ui

Map MiniApp UI requirements to TDS React Native components and annotate export gaps.

Updated Mar 14, 2026
One-click install
npx skills add https://github.com/jingjing2222/create-rn-miniapp --skill tds-ui
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tds-ui
Source: https://github.com/jingjing2222/create-rn-miniapp/tree/main/skills/tds-ui
Command: npx skills add https://github.com/jingjing2222/create-rn-miniapp --skill tds-ui

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps teams map MiniApp UI requirements to the appropriate TDS React Native surfaces, ensuring exports and public docs align with implementation.

Core Features & Use Cases

  • Provides a doc-backed mapping strategy to choose the correct TDS UI components (e.g., text-field, navbar, chart) based on screen requirements.
  • Identifies and annotates export gaps with anomaly notes to guide repository updates and root-export path decisions.
  • Supports end-to-end decision workflows for both UI surface selection and state management patterns (controlled vs uncontrolled) within the create-rn-miniapp workspace.

Quick Start

Describe how to map a MiniApp screen requirement to a TDS UI component and document any export gaps.

Frequently Asked Questions about tds-ui

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

FAQPage Schema
How do I map MiniApp UI requirements to the correct TDS React Native components?

To map MiniApp UI requirements to TDS React Native components, apply a doc-backed-first strategy that aligns public documentation with actual exports. This ensures you select the correct UI surfaces like text-field or navbar based on screen requirements.

How do I decide between controlled and uncontrolled state management for TDS React Native components?

Deciding between controlled and uncontrolled state management for TDS React Native components involves using an end-to-end decision workflow within the create-rn-miniapp workspace. This workflow aligns state patterns with your specific UI surface selection.

What is the doc-backed-first policy for TDS React Native component selection?

The doc-backed-first policy for TDS React Native selection enforces mapping UI requirements using publicly documented component exports before considering export-only alternatives. This ensures implementation aligns strictly with available public documentation.

Why does my TDS React Native component export not match the public documentation?

TDS React Native component exports may not match public documentation due to export gaps. You resolve this by enforcing the doc-backed-first policy and annotating these discrepancies with anomaly notes and precise root-export paths for repository updates.