agents/skills/typescript/typescript-tooling/SKILL.md
Development tools, linting, and build config for TypeScript. Use when configuring ESLint, Prettier, Jest, Vitest, tsconfig, or any TS build tooling.
npx skillsauth add hoangnguyen0403/agent-skills-standard typescript-toolingInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
tsc for CI builds; esbuild or ts-node for development.ESLint with @typescript-eslint/recommended. Enable strict type checking.Prettier via lint-staged and .prettierrc.Vitest (or Jest) for unit/integration testing. Target > 80% line coverage.tsup (library bundling) or Vite (web applications).strict: true long-term. For existing projects, migrate incrementally: start with strictNullChecks, then noImplicitAny, strictFunctionTypes. Do NOT flip strict: true in one step.tsc --noEmit in build pipeline to catch type errors.@ts-expect-error over @ts-ignore for documented edge-cases.Enable @typescript-eslint/recommended at minimum. When strict: false in tsconfig, no-unsafe-* rules may produce excessive noise — suppress selectively with @ts-expect-error rather than disabling globally.
See reference for common linting issues (request typing, unused params, test mock typing) and tsconfig migration examples.
After editing any .ts / .tsx file:
getDiagnostics (typescript-lsp MCP tool) — surfaces type errors in real time.tsc --noEmit in CI — catches project-wide errors LSP may miss.eslint --fix — auto-fix formatting and lint violations.Fallback when typescript-lsp MCP unconfigured: run
tsc --noEmitdirectly.
getDiagnostics fastest feedback loop. Use it before every commit on modified files. Use getHover to inspect inferred types, getReferences before renaming symbols.
@ts-ignore: Use @ts-expect-error — self-documents intent, fails if error disappears.any for request objects: Import centralized interfaces from src/common/interfaces/.eslint-disable (global): Suppress per-line; fix root cause instead.strict: true flip on existing repos: migrate incrementally starting with strictNullChecks.testing
Infer the requesting operator's technical fluency from message content (never ask directly) and adapt register — business, hybrid, or technical — across SDLC workflow output. Use when starting sdlc, brainstorm-feature, plan-feature, verify-work, publish-notes, or session-report, or whenever a request's phrasing signals a non-technical or cross-stack operator.
documentation
Define transaction boundaries, locking, and consistency guarantees for multi-step writes. Use when designing atomic operations, retries, idempotency, or concurrent write behavior.
development
Design relational or document schemas from access patterns, cardinality, and lifecycle. Use when modeling entities, choosing embed vs normalize, or shaping schema boundaries before implementation.
data-ai
Diagnose database latency with explain plans, index ownership, and query-shape review. Use when a query is slow, an index is missing, or scans and N+1 patterns appear.