typescript-coder

typescript-coder is a skill for Claude Code from DmitriyYukhanov/claude-plugins. It costs 30 tokens per session (1,217 once invoked), scanned A, original, MIT.

A coding guide for adding or changing TypeScript and JavaScript code within an existing project structure.

In plain words
What is it for?
Use it to implement features, follow naming and typing conventions, document public code, and validate changes with the project's checks.
Why use it?
It helps keep changes consistent with the project's rules and limits unnecessary edits. It also checks the changed code for type and style problems.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the typescript-dev plugin — 3 skills, 1 command, 1 agent shipped together

Good fit Use it to implement features, follow naming and typing conventions, document public code, and validate changes with the project's checks.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/dmitriyyukhanov/claude-plugins/typescript-coder
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add DmitriyYukhanov/claude-plugins --skill typescript-coder
Clone the repo
git clone --depth 1 https://github.com/DmitriyYukhanov/claude-plugins

Made for: Claude Code.

Or install typescript-dev, the plugin that ships this one along with the rest of its 3 skills, 1 command, 1 agent.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for typescript-coder

README.md
[![agentmods](https://agentmods.dev/badge/skills/dmitriyyukhanov/claude-plugins/typescript-coder/github.svg)](https://agentmods.dev/skills/dmitriyyukhanov/claude-plugins/typescript-coder)
Your own site
<a href="https://agentmods.dev/skills/dmitriyyukhanov/claude-plugins/typescript-coder"><img src="https://agentmods.dev/badge/skills/dmitriyyukhanov/claude-plugins/typescript-coder/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for typescript-coder

Your own site · 80×15
<a href="https://agentmods.dev/skills/dmitriyyukhanov/claude-plugins/typescript-coder"><img src="https://agentmods.dev/badge/skills/dmitriyyukhanov/claude-plugins/typescript-coder.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 30 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,217 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00030 $0.01217
Opus 5.5 $0.00012 $0.00487
Sonnet 5.5 $0.00006 $0.00243
Haiku 4.5 $0.00003 $0.00122

Measured 1mo ago against content hash 426b5fd92104, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

typescript-coder scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

plugins/typescript-dev/skills/typescript-coder/SKILL.md · 184 lines

How it starts

The opening of the file, as written. The whole thing — 184 lines — stays where its author put it; the contents beside it link to each section on GitHub.

TypeScript Coder Skill

You are a senior TypeScript developer following strict coding guidelines.

Workflow

  1. Inspect existing conventions — read nearby code, tsconfig.json, ESLint/Prettier configs before writing
  2. Edit minimum surface — change only what the task requires; don't refactor surrounding code
  3. Validate — run the project's linter/type-checker on changed files
  4. Stop on ambiguity — if the task is unclear or a change could be destructive, ask before proceeding

Core Principles

  • Use English for all code and documentation
  • Follow project-local standards first (tsconfig, ESLint, Prettier, framework style guides)
  • Declare explicit types at module boundaries (public APIs, exported functions, complex returns); use inference for obvious locals
  • Avoid any - define real types instead
  • Use JSDoc to document public classes and methods
  • One export per file
  • Prefer nullish coalescing (??) over logical or (||)

Nomenclature

Naming Conventions

  • Classes: PascalCase (UserService, DataProcessor)
  • Variables, functions, methods: camelCase (userData, processInput)
  • Files and directories: kebab-case (user-service.ts, data-processor/)
  • Environment variables: UPPERCASE (API_URL, NODE_ENV)
  • Constants: Follow project convention (default to UPPER_SNAKE_CASE for module-level constants)

Naming Rules

  • Start functions with verbs (getUser, validateInput, processData)
  • Boolean variables with verbs (isLoading, hasError, canSubmit)
  • Avoid single letters except: i, j for loops; err for errors; ctx for contexts
  • No abbreviations except standard ones (API, URL)

Functions

Structure

  • Short functions (<20 lines)
  • Single purpose
  • Single level of abstraction
  • Avoid nesting - use early returns

Patterns

// Good: Early return
function processUser(user: User | null): Result {
  if (!user) return { error: 'No user' };
  if (!user.isActive) return { error: 'User inactive' };
  return { data: transform(user) };
}

// Good: Use higher-order functions
const activeUsers = users.filter(u => u.isActive).map(u => u.name);

// Good: Default parameters
function createConfig(options: Partial<Config> = {}): Config {
  return { ...defaultConfig, ...options };
}

Read the full file on GitHub · 184 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 1mo ago First seen · 184 lines · 30 tokens per session scan A 426b5fd92104

Subscribe to this mod's changes

typescript-coder is a skill published in the GitHub repository DmitriyYukhanov/claude-plugins (8 stars, last pushed 8d ago), licensed MIT. It adds 30 tokens to every session and 1,217 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

senior-frontend

Frontend development skill for React, Next.js, TypeScript, and Tailwind CSS applications. Use when building React components, optimizing Next.js performance, analyzing bundle sizes, scaffolding frontend projects, implementing accessibility, or reviewing frontend code quality.

composio-community/awesome-claude-plugins · 52 tokens

clean-code-ts

Use when writing or reviewing TypeScript — deeper idioms (eliminate any, discriminated unions, narrowing, exhaustiveness, schema-derived types, async correctness).

CassetteTapeCrackle/claude-starters · 36 tokens

typescript-conventions

Idiomatic, type-safe TypeScript. Use when writing or reviewing TypeScript.

Cypsy1714/cchad · 20 tokens

node-backend

Node.js backend development patterns for Express, NestJS, Fastify, and Hono. Use when implementing APIs, authentication, middleware, services, and server-side logic with Node.js and TypeScript. Provides project structure, code patterns, and best practices.

shahtuyakov/claude-setup · 55 tokens

standards-typescript

This skill provides TypeScript coding standards and is automatically loaded for TypeScript projects. It includes naming conventions, best practices, and recommended tooling.

b33eep/claude-code-setup · 33 tokens

adding-a-command

Creates a new CLI command following the Commander.js pattern in src/commands/. Handles command registration in src/cli.ts, telemetry tracking via tracked() wrapper, and option parsing. Use when user says add command, new CLI command, create subcommand, or adds files to src/commands/. Do NOT use for modifying existing…

caliber-ai-org/ai-setup · 76 tokens