mcpbeat

Typescript Tooling

hoangnguyen0403/typescript-tooling

Development tools, linting, and build config for TypeScript. Use when configuring ESLint, Prettier, Jest, Vitest, tsconfig, or any TS build tooling.

1k tokens
context cost
the whole folder, loaded on every use
2
files
instructions only
0
copies elsewhere
how many repositories repackaged it
536
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/HoangNguyen0403/agent-skills-standard --skill typescript-tooling

What comes with it

1 879 bytes besides the instruction
references/REFERENCE.md

The instruction itself

7 sections, as written by the author

TypeScript Tooling

Priority: P1 (HIGH)

Implementation Guidelines

  • Compiler: Use tsc for CI builds; esbuild or ts-node for development.
  • Linting: Enforce ESLint with @typescript-eslint/recommended. Enable strict type checking.
  • Formatting: Mandate Prettier via lint-staged and .prettierrc.
  • Testing: Use Vitest (or Jest) for unit/integration testing. Target > 80% line coverage.
  • Builds: Use tsup (library bundling) or Vite (web applications).
  • TypeScript Config: Aim for strict: true long-term. For existing projects, migrate incrementally: start with strictNullChecks, then noImplicitAny, strictFunctionTypes. Do NOT flip strict: true in one step.
  • CI/CD: Always run tsc --noEmit in build pipeline to catch type errors.
  • Error Suppression: Favor @ts-expect-error over @ts-ignore for documented edge-cases.

ESLint Configuration

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.

Verification Workflow (Mandatory)

After editing any .ts / .tsx file:

  • Call getDiagnostics (typescript-lsp MCP tool) — surfaces type errors in real time.
  • Run tsc --noEmit in CI — catches project-wide errors LSP may miss.
  • Run 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.

Anti-Patterns

  • No @ts-ignore: Use @ts-expect-error — self-documents intent, fails if error disappears.
  • No any for request objects: Import centralized interfaces from src/common/interfaces/.
  • No eslint-disable (global): Suppress per-line; fix root cause instead.
  • No atomic strict: true flip on existing repos: migrate incrementally starting with strictNullChecks.

References

  • Config Examples & Linting Patterns

How to use it

Copy the folder

Take hoangnguyen0403/typescript-tooling from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

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.