Development tools, linting, and build config for TypeScript. Use when configuring ESLint, Prettier, Jest, Vitest, tsconfig, or any TS build tooling.
npx skills add https://github.com/HoangNguyen0403/agent-skills-standard --skill typescript-tooling
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 --noEmit directly.
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.Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup
Comprehensive GitHub release orchestration with AI swarm coordination for automated versioning, testing, deployment, and rollback management
Migrate test files from `as` type assertions to @total-typescript/shoehorn. Use when user mentions shoehorn, wants to replace `as` in tests, or needs partial test data.
Modern JavaScript/TypeScript development with Bun runtime. Covers package management, bundling, testing, and migration from Node.js. Use when working with Bun, optimizing JS/TS development speed, or migrating from Node.js to Bun.
You are a dependency management expert specializing in safe, incremental upgrades of project dependencies. Plan and execute dependency updates with minimal risk, proper testing, and clear migration pa
Master systematic debugging techniques, profiling tools, and root cause analysis to efficiently track down bugs across any codebase or technology stack. Use when investigating bugs, performance issues, or unexpected behavior.
Opinionated backend development standards for Node.js + Express + TypeScript microservices. Covers layered architecture, BaseController pattern, dependency injection, Prisma repositories, Zod validation, unifiedConfig, Sentry error tracking, async safety, and testing discipline.
Best practices for writing JavaScript/TypeScript tests using Jest, including mocking strategies, test structure, and common patterns.
Take hoangnguyen0403/typescript-tooling from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.