typescript
Use TypeScript for type-safe JavaScript: types, interfaces, generics, narrowing, tsconfig, modules, and strict mode. Use when writing or reviewing TypeScript, configuring tsconfig.json, defining types or interfaces, generics, type inference, or when the user mentions TypeScript, TS, or type checking.
What this skill does
# TypeScript
## Overview
TypeScript is JavaScript with static typing. It adds a **compile-time type checker**; runtime behavior is JavaScript. Learning JavaScript applies to TypeScript for runtime tasks (e.g. sorting a list, DOM, async). Use TypeScript for types, interfaces, generics, and better tooling.
**Core idea**: Types describe shape and contracts; the compiler catches type errors before run time. Enable `strict` in `tsconfig.json` as a best practice.
---
## Quick reference
| Concept | Syntax / note |
|--------|----------------|
| Type annotation | `let x: string`, `function f(n: number): void` |
| Interface | `interface User { name: string; id: number }` |
| Type alias | `type Id = string \| number` |
| Union | `string` or `number` (union types) |
| Optional | `prop?: string` or `prop: string \| undefined` |
| Generics | `function id<T>(x: T): T { return x }` |
| Infer type from schema | Use library (e.g. Zod: `z.infer<typeof schema>`) |
---
## Everyday types
- **Primitives**: `string`, `number`, `boolean`, `bigint`, `symbol`.
- **Arrays**: `number[]` or `Array<number>`.
- **Any**: `any` — disables checking; avoid when possible. Prefer `unknown` for truly unknown data and narrow before use.
- **Type annotations** (postfix): `const name: string = "x"`, `function greet(name: string): string { return "Hi " + name }`.
- **Object types**: `{ name: string; age?: number }` or `interface User { name: string; age?: number }`.
- **Unions**: `string | number`; **literal types**: `"a" | "b"`.
---
## Narrowing
Narrow types with conditionals so TypeScript can infer:
- **typeof**: `if (typeof x === "string") { ... }`
- **Truthiness**: `if (value) { ... }`
- **Equality**: `if (x === null) { ... }`
- **in**: `if ("name" in obj) { ... }`
- **Type guards**: `function isFish(pet: Fish | Bird): pet is Fish { ... }`
- **Discriminated unions**: Use a common literal field (e.g. `kind: "circle"`) and switch on it.
---
## Functions
- **Signatures**: `(a: string, b?: number) => boolean`; **void** for no return value.
- **Overloads**: Multiple call signatures + one implementation.
- **Generics**: `function first<T>(arr: T[]): T \| undefined`.
- **Constraints**: `function longest<T extends { length: number }>(a: T, b: T): T`.
---
## Object types & type manipulation
- **Interfaces**: `interface Point { x: number; y: number }`; `extends` for extension.
- **Index signatures**: `[key: string]: number`.
- **keyof**: `type K = keyof User` → union of keys.
- **typeof**: `type C = typeof config` (value → type).
- **Indexed access**: `type Name = User["name"]`.
- **Mapped types**: `type Readonly<T> = { readonly [K in keyof T]: T[K] }`.
- **Conditional types**: `type F = T extends string ? number : boolean`.
- **Template literal types**: `` type E = `on${Capitalize<Event>}` ``.
- **Utility types**: `Partial<T>`, `Required<T>`, `Pick<T, K>`, `Omit<T, K>`, `Record<K, V>`, `Exclude<T, U>`, `Extract<T, U>`, `NonNullable<T>`, `ReturnType<F>`, `Parameters<F>`.
---
## Classes
- **Members**: `class C { prop: number; method(): void {} }`.
- **Constructor**: `constructor(public name: string) {}` (parameter property).
- **Implements**: `class D implements I {}`.
- **Extends**: `class Child extends Parent {}`.
- **Readonly**, **private**, **protected** as needed.
---
## Modules
- **ES modules**: `import { x } from "./file"`, `export const x = 1`, `export type { T }`.
- **Default export**: `export default App`, `import App from "./App"`.
- **Namespace** (legacy): Prefer ES modules.
---
## Project configuration: tsconfig.json
- **strict**: Set `"strict": true` (recommended). Enables strictNullChecks, noImplicitAny, strictFunctionTypes, etc.
- **target**: e.g. `"ES2022"` or `"ESNext"`.
- **module**: e.g. `"ESNext"`, `"NodeNext"` for Node.
- **moduleResolution**: `"bundler"` (with bundler), `"NodeNext"` for Node.
- **paths**: `"@/*": ["./src/*"]` for path aliases.
- **include** / **exclude**: Which files are compiled.
- **References**: Use project references for large monorepos.
See [reference.md](reference.md) for official TSConfig Reference link.
---
## Best practices
- Enable **strict** mode.
- Prefer **interfaces** for object shapes that may be extended; **type** for unions, mapped types, and aliases.
- Prefer **const** and **readonly** where possible.
- Use **unknown** instead of **any** for external data; narrow before use.
- Use **generics** to keep functions reusable and type-safe.
- For runtime validation + types, use a schema library (e.g. **Zod**) and infer types with `z.infer<typeof schema>`.
---
## Common mistakes
- **any**: Avoid; use `unknown` and narrow, or proper types.
- **Non-null assertion (`!`)**: Use sparingly; prefer narrowing or optional chaining.
- **Type assertions (`as`)**: Prefer type guards or schema validation when data comes from outside.
- **Strict off**: Keep `strict: true`; fix errors rather than disabling.
---
## Additional resources
- [reference.md](reference.md) — Official documentation links (Handbook, Reference, TSConfig, Cheat Sheets).
- **Official**: https://www.typescriptlang.org/docs — Get Started, Handbook, Reference, TSConfig.
Related in Writing & Docs
jax-development
IncludedUse this skill when the user is writing, debugging, profiling, refactoring, reviewing, benchmarking, parallelising, exporting, or explaining JAX code, or when they mention JAX, jax.numpy, jit, grad, value_and_grad, vmap, scan, lax, random keys, pytrees, jax.Array, sharding, Mesh, PartitionSpec, NamedSharding, pmap, shard_map, Pallas, XLA, StableHLO, checkify, profiler, or the JAX repo. It helps turn NumPy or PyTorch-style code into pure functional JAX, fix tracer/control-flow/shape/PRNG bugs, remove recompiles and host-device syncs, choose transforms and sharding strategies, inspect jaxpr/lowering/IR, and benchmark compiled code correctly.
nature-article-writer
IncludedDrafts, rewrites, diagnostically critiques, and style-calibrates primary research manuscripts for Nature and Nature Portfolio journals. Use when the user wants a Nature-style title, summary paragraph or abstract, introduction, results, discussion, methods, figure legends, presubmission enquiry, cover letter, reviewer response, or when a scientific draft sounds generic, jargon-heavy, structurally weak, or AI-ish and needs precise, broad-reader-friendly prose without inventing data, analyses, or references. Best for primary research articles and letters rather than reviews or press releases unless explicitly adapting one.
deckrd
IncludedDocument-driven framework that derives requirements, specifications, implementation plans, and executable tasks from goals through structured AI dialogue. Use when user says "write requirements", "create spec", "plan implementation", "derive tasks", "structure this feature", "break down into tasks", or "document this module". Also use for reverse engineering existing code into docs (/deckrd rev). Do NOT use for direct code writing — use /deckrd-coder after tasks are generated. Do NOT use when the user only wants to run or fix existing code without planning.
clinical-decision-support
IncludedGenerate professional clinical decision support (CDS) documents for pharmaceutical and clinical research settings, including patient cohort analyses (biomarker-stratified with outcomes) and treatment recommendation reports (evidence-based guidelines with decision algorithms). Supports GRADE evidence grading, statistical analysis (hazard ratios, survival curves, waterfall plots), biomarker integration, and regulatory compliance. Outputs publication-ready LaTeX/PDF format optimized for drug development, clinical research, and evidence synthesis.
handling-sf-data
IncludedSalesforce data operations with 130-point scoring. Use this skill to create, update, delete, bulk import/export, generate test data, and clean up org records using sf CLI and anonymous Apex. TRIGGER when: user creates test data, performs bulk import/export, uses sf data CLI commands, needs data factory patterns for Apex tests, or needs to seed/clean records in a Salesforce org. DO NOT TRIGGER when: SOQL query writing only (use querying-soql), Apex test execution (use running-apex-tests), or metadata deployment (use deploying-metadata).
accelint-ac-to-playwright
IncludedConvert and validate acceptance criteria for Playwright test automation. Use when user asks to (1) review/evaluate/check if AC are ready for automation, (2) assess if AC can be converted as-is, (3) validate AC quality for Playwright, (4) turn AC into tests, (5) generate tests from acceptance criteria, (6) convert .md bullets or .feature Gherkin files to Playwright specs, (7) create test automation from requirements. Handles both bullet-style markdown and Gherkin syntax with JSON test plan generation and validation.