typescript
Best practices for TypeScript code including type safety, discriminated unions, type guards, and exhaustive checking. Use this skill whenever the user asks about TypeScript patterns, type safety, type assertions (as any, as unknown), non-null assertions, discriminated unions, exhaustive switch/never patterns, type guards, boolean trap parameters, race conditions in async code, memory leaks from closures, or sequential vs parallel async operations. Also trigger when reviewing TypeScript code for unsafe patterns or refactoring types.
Works with
--- name: typescript description: Best practices for TypeScript code including type safety, discriminated unions, type guards, and exhaustive checking. Use this skill whenever the user asks about TypeScript patterns, type safety, type assertions (as any, as unknown), non-null assertions, discriminated unions, exhaustive switch/never patterns, type guards, boolean trap parameters, race conditions in async code, memory leaks from closures, or sequential vs parallel async operations. Also trigger when reviewing TypeScript code for unsafe patterns or refactoring types. license: Apache-2.0 --- # TypeScript You MUST review @projects/site/src/docs/internal/guidelines/typescript.md before making any TypeScript changes. ## When to Use This Skill - Writing or modifying component classes, utilities, or type definitions - Adding or updating TypeScript interfaces, types, or enums - Reviewing code for type safety issues - Implementing type guards or discriminated unions - Working with union types that require exhaustive checking ## References - [TypeScript Guidelines](/projects/site/src/docs/internal/guidelines/typescript.md)
More Debugging skills
diagnosing-bugs
mattpocock/skills
Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.
explore-code
lllllllama/rigorpilot-skills
Rigor Improve implementation leaf skill for auditable candidate implementation in deep learning research repositories. Use when the researcher explicitly authorizes exploratory work on an isolated branch or worktree to transplant modules, adapt a backbone, add LoRA or adapter layers, replace a head, or stitch together meaningful low-risk migration ideas with rollback-aware records in `explore_outputs/`. Do not use for end-to-end exploration orchestration on top of `current_research`, trusted baseline reproduction, conservative debugging, environment setup, verified contribution claims, or default repository analysis.
safe-debug
lllllllama/rigorpilot-skills
Rigor Debug / Rigor Audit skill for deep learning research work. Use when the user pastes a traceback, terminal error, CUDA OOM, checkpoint load failure, shape mismatch, NaN loss symptom, or training failure and wants conservative diagnosis before any patching, with debug fixes clearly separated from research contributions. Do not use for broad refactoring, speculative adaptation, automatic exploratory patching, or general repository familiarization.
