Use this skill whenever the user asks you to write, edit, review, refactor, debug, or design TypeScript or TSX code. It is especially relevant for application code, backend routes, React/UI work, schemas, runtime boundaries, persistence, async workflows, API contracts, tests, lint/typecheck fixes, and code review. Apply it even when the user does not explicitly mention "TypeScript" if the files or project are TypeScript-based.
85
81%
Does it follow best practices?
Impact
91%
1.18xAverage score across 3 eval scenarios
Passed
No known issues
Bounded async concurrency with typed domain outcomes
Schema library validation
100%
100%
Schema at boundary
100%
100%
Inferred types from schema
100%
100%
No direct Promise.all on array
100%
100%
Named concurrency constant
100%
100%
Null normalized to undefined
100%
100%
Typed domain outcome union
100%
100%
No Result wrapper library
100%
100%
Thin handler delegation
100%
100%
Named exports
100%
100%
Abort signal or timeout
0%
0%
Config parsing and versioned persistence records
Env vars at boundary
100%
100%
Typed config export
100%
100%
Config string conversion
100%
87%
type not interface
25%
100%
Optional over null
12%
100%
Schema version field
100%
100%
Named migration/deserialization function
100%
100%
Version switch or branching
100%
100%
readonly on persisted types
25%
62%
Domain constants file
10%
30%
No magic literals
25%
75%
Discriminated union UI state with exhaustive rendering
Discriminated union state
100%
100%
Switch-based rendering
13%
100%
Exhaustive switch with never
0%
100%
Named component export
100%
100%
type not interface for state/props
50%
100%
Boolean predicate names
100%
75%
Domain logic delegation
100%
100%
Semantic HTML elements
100%
70%
Minimal state
100%
100%
No loose boolean state fields
100%
100%
51dd9ad
Table of Contents
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.