typescript-coderlisted

# TypeScript Coding Standards ## Activation Scope Apply this skill to every task in a TypeScript or mixed TypeScript repository, not only edits to `.ts` or `.tsx` files. It also governs JavaScript, configuration, tests, dependencies, build scripts, CI, and documentation that belong to that TypeScript project. Do not activate automatically for JavaScript-only projects. When project type is uncertain, inspect the markers in [`references/project-detection.md`](references/project-detection.md). Load task-relevant references before making decisions or changes. ## Precedence and Inspection Resolve decisions in this order: 1. User requirements and repository instructions. 2. Established repository architecture, configuration, scripts, lockfile, and CI. 3. Framework and runtime conventions for the versions actually installed. 4. This skill's greenfield defaults. Before changing code or tooling, inspect the relevant package boundary and its: - `package.json`, lockfile, `packageManager`, `engines`, workspaces, and runtime pins. - `tsconfig*.json` and framework/build configuration. - ESLint, Biome, Prettier, test, and CI configuration. - Source layout and several representative files. Never silently change the runtime, package manager, lockfile format, module system, linter, formatter, test runner, bundler, or framework. Do not generate a second lockfile. See [`references/project-detection.md`](references/project-detection.md). ## General - Favor readable, unsurprising code