Derive narrow UI types from generated API shapes using TypeScript utilities.
npx skills add https://github.com/massCodeIO/massCode --skill api-and-typing
Please help me install this Agent Skill. Skill: api-and-typing Source: https://github.com/massCodeIO/massCode/tree/main/.agents/skills/api-and-typing Command: npx skills add https://github.com/massCodeIO/massCode --skill api-and-typing
The massCode UI often encounters the need to work with API types that originate from generated sources or DTOs. Duplicating or re-creating these shapes in renderer code leads to drift, maintenance burden, and inconsistent behavior. This skill emphasizes reusing existing generated types, and introduces guidelines for deriving narrow local types for UI models, while keeping API shapes intact.
Review a renderer component and replace any copied API shape with a narrow derived type based on the existing generated type.
High-intent search queries and answers about installing and using this skill.
To avoid duplicating API types in UI components, reuse existing generated types or DTOs and derive narrow local view models using TypeScript utilities like Pick and Omit.
The best way to derive UI-only types from existing API DTOs is to apply TypeScript utilities such as Pick, Omit, ReturnType, and Awaited to safely adapt the original API shapes for view models.
You should create a local type instead of reusing an API type directly when defining UI-only models, form models, or derived views that require narrowing the original API shape for specific renderer needs.
ReturnType and Awaited help with TypeScript API typing by extracting the resolved promise shapes from API functions, allowing you to derive accurate UI models without manually copying the underlying API shapes.
Yes, you can use TypeScript Pick and Omit to adapt generated API shapes for forms by selecting only the required properties from the original DTOs to create safe, narrow form models.
Manually copied API shapes cause type drift in renderer code because duplicating generated types or DTOs creates maintenance burdens and leads to inconsistent behavior when the original API shape changes.
buchananwillDerive new TypeScript types from existing definitions using mapped and conditional types.
akiojinEdit, search, and refactor Unity C# scripts using a compact code index.
RomualdPGenerate synchronized DTOs and TypeScript types for Next.js and NestJS API contracts.
AsmayaseenDefine frontend TypeScript types from backend contracts with naming conventions.
