Decide between TypeScript interfaces and type aliases for object shapes and unions.
npx skills add https://github.com/luyi985/lyi-bash --skill type-vs-interface
Please help me install this Agent Skill. Skill: type-vs-interface Source: https://github.com/luyi985/lyi-bash/tree/main/ai/skills/type-vs-interface Command: npx skills add https://github.com/luyi985/lyi-bash --skill type-vs-interface
This Skill helps developers decide when to use TypeScript interfaces versus type aliases, reducing confusion and inconsistencies in type design.
Decide, in your codebase, to use interface for object shapes that can be extended and type for unions, tuples, and mapped types.
High-intent search queries and answers about installing and using this skill.
Use a TypeScript interface for extendable object shapes and a type alias for unions, tuples, and mapped types to ensure consistency and extensibility in your codebase.
For API design, prefer interfaces to define extensible object shapes and use type aliases for complex unions or tuples, enforcing consistency across your API surfaces.
TypeScript declaration merging applies only to interfaces, allowing multiple declarations to combine into one, whereas type aliases cannot be merged.
The best way to type component props is generally using interfaces for extendable object shapes, reserving type aliases for mapped types or union props.
For library declarations, prefer interfaces for public object shapes to allow consumer extension via declaration merging, using type aliases for internal unions or tuples.
xloxn69Generate TypeScript interfaces, types, enums, and generics from data structure descriptions.
Wondermove-IncEnforce project rules from .claude/memory files for code quality.
alexsandrocruzCreate advanced TypeScript types for generics, conditional types, and React components.
flpbaladaDecide between interface and type for TypeScript object shapes.
