with one click
typescript-tooling
Development tools, linting, and build config for TypeScript. Use when configuring ESLint, Prettier, Jest, Vitest, tsconfig, or any TS build tooling.
Menu
Development tools, linting, and build config for TypeScript. Use when configuring ESLint, Prettier, Jest, Vitest, tsconfig, or any TS build tooling.
| name | typescript-tooling |
| description | Development tools, linting, and build config for TypeScript. Use when configuring ESLint, Prettier, Jest, Vitest, tsconfig, or any TS build tooling. |
| metadata | {"triggers":{"files":["tsconfig.json",".eslintrc.*","jest.config.*","package.json"],"keywords":["eslint","prettier","jest","vitest","build","compile","lint"]}} |
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.Standardize BRD and BRD-lite discovery for business goals, stakeholder impact, current-to-future state, and measurable value outcomes. Use when creating BRD, business case, project justification, ROI narrative, or AS-IS to TO-BE scope.
Standardize PRD discovery and drafting for product scope, user outcomes, requirement IDs, and acceptance criteria. Use when creating PRD, product requirements, feature specification, or acceptance criteria plan.
Standardize SRS and FRS specifications for technical behavior, interfaces, data contracts, quality constraints, and verification mapping. Use when writing SRS, functional specification, system behavior requirements, API/data contracts, or non-functional thresholds.
Clarify a rough product or engineering idea into a BRD-lite brief (Why) with measurable business value.
Turn an approved PRD or implementation goal into SRS/FRS technical requirements (How), architecture, contracts, and verification decisions.
Plan a feature from BRD-lite brief or clear intent into PRD (What), decisions, implementation plan, and task slices.