domains / families / software-engineering / typescript

typescript

combined

Provide best-practice coding conventions and generate standards-compliant TypeScript code. Language-specific super-code guidelines for typescript.

When to use

• Use this skill when the task matches this description: Language-specific super-code guidelines for typescript.

When not to use

• These are language-specific guidelines and do not cover overall architectural decisions.
• Over-compression might reduce readability; apply judgement.

Skill page

Conflict

The two skills cover overlapping ground (TypeScript best practices, async handling, type safety) but have distinct focuses and conflicting advice. The first skill (sickn33) is a 'super-code' efficiency reference focused on idiomatic refactoring (e.g., preferring `type` for unions, avoiding explicit return types when obvious). The second skill (LeoYeAI) is a comprehensive style guide covering naming, file structure, and specific conventions (e.g., preferring `interface` for object shapes, requiring explicit return types for public APIs). Because they disagree on specific conventions (like `type` vs `interface` preference and return type annotation), crowning one would hide the other's valid alternative approach.