Typescript Tooling

Community

HoangNguyen0403

typescript-tooling

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

Overview

Publisher	HoangNguyen0403
Repository	`agent-skills-standard`
Skill name	`typescript-tooling`
Stars	573
Forks	166
Bundled files	1
License	MIT
Links	Skill source Repository Homepage

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
1 bundled files
Scripts, templates, and references the model can read while it works. Files are read-only and never executed.
Open source
Published by HoangNguyen0403 on GitHub. Read the source before you install it.

Installation

Install the Typescript Tooling AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/HoangNguyen0403/agent-skills-standard/tree/develop/.agents/skills/typescript/typescript-tooling
Enable the skill in any chat where you want it available.

Store

Installed

Skills

Add skills

Import one or more skills from a public GitHub folder or a local .skill or .zip archive, or SKILL.md file.

From GitHub URLFrom .skill, .zip, or SKILL.md

GitHub repo or folder

https://github.com/HoangNguyen0403/agent-skills-standard/tree/develop/.agents/skills/typescript/typescript-tooling

Points to a single skill folder, or any folder that contains multiple skills. Public repos only.

CancelContinue

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/HoangNguyen0403/agent-skills-standard.git /tmp/agent-skills-standard
mkdir -p .claude/skills
cp -r /tmp/agent-skills-standard/.agents/skills/typescript/typescript-tooling .claude/skills/typescript-tooling

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Typescript Tooling in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Typescript Tooling on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Typescript Tooling is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

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

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

references/REFERENCE.md2 KB

Frequently asked questions

What does the Typescript Tooling AI skill do?

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

Why use Typescript Tooling on TypingMind?

Because you install it once and use it with any model. Typescript Tooling is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Typescript Tooling in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/HoangNguyen0403/agent-skills-standard/tree/develop/.agents/skills/typescript/typescript-tooling. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Typescript Tooling?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Typescript Tooling?

As many as you like. As long as a model supports skills, you can use Typescript Tooling with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Typescript Tooling AI skill free?

Yes. It is published on GitHub by HoangNguyen0403 under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Release Openclaw Maintainer

openclaw

OrganizationPopular

Prepare, publish, recover, or verify OpenClaw beta, stable, and extended-stable releases, including approved backports.

Release Openclaw Plugin Testing

openclaw

OrganizationPopular

Plan and run pre-release OpenClaw plugin validation across bundled plugins, package artifacts, lifecycle commands, doctor/fix, config round-trip, gateway startup, SDK compatibility, Docker E2E,…

Solid

Write, port, review, or test Solid 2 UI in OpenClaw (Control UI, plugin views, Canvas hosts), including state ownership, Lit interop during the migration, native overlays, testing, performance, and…

Auto Qa

Run OpenClaw-wide autonomous QA and live/stress campaigns across independent subsystem lanes, with verified fixes and a resumable evidence report.

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

TypeScript Tooling

Priority: P1 (HIGH)

Implementation Guidelines

ESLint Configuration

Verification Workflow (Mandatory)

Anti-Patterns

References

Bundled files

Frequently asked questions

Related AI Skills

Set up your own AI workspace now