TypeScript

**Judgement:** Strongly recommended as a focused, low-risk TypeScript best-practices reference for agents that generate or refactor TS, especially under `strict` mode. **What it’s good for** - Helping the agent avoid common TypeScript pitfalls: misuse of `any`, incorrect narrowing, non-exhaustive discriminated unions, and misleading patterns like `filter(Boolean)`. - Producing higher-quality type definitions with generics, utility types, and declaration files. - Guiding JS→TS migration in a conservative, type-safe way. **Risks / Limitations** - Scope is narrowly technical: it does not cover framework-specific patterns (e.g., React, Vue) or build tooling; it’s about core TS semantics and patterns. - Guidance may lag behind the very latest TypeScript language features or ecosystem conventions if the skill is not frequently updated. - Opinionated strict-mode patterns might conflict with an existing codebase that intentionally relaxes some checks or uses `any` for pragmatic reasons. **Recommended scenarios** - Use when you want the agent to act like a TypeScript expert emphasizing safety and correctness over brevity or permissive typing. - Particularly suitable for library/API authors, teams enforcing strict TypeScript, and projects migrating from JavaScript where type soundness is a priority. - Combine with project-specific instructions about coding style or framework usage, as this skill focuses on language-level TypeScript rather than application architecture.