typescript-standards

A set of coding rules for TypeScript, a programming language that adds type checks to JavaScript.

In plain words
What is it for?
Writing or reviewing TypeScript, converting JavaScript projects, refactoring code, and setting up TypeScript projects with strict type checking.
Why use it?
It helps catch incorrect data and null-value handling early and keeps names, files, and shared code organized consistently.

Skill for Claude CodeCodex

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.

agentmods
npx agentmods add skills/usrrname/cursorrules/typescript
Any agent
npx skills add usrrname/cursorrules --skill typescript
Clone the repo
git clone --depth 1 https://github.com/usrrname/cursorrules

Made for: Claude Code, Codex.

Per session 12 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 462 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00012 $0.00462
Opus 5 $0.00006 $0.00231
Sonnet 5 $0.00002 $0.00092
Haiku 4.5 $0.00001 $0.00046

Measured yesterday against content hash 6fdd61215dc2, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

typescript-standards 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 yesterday.

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.

.claude/skills/typescript/SKILL.md · 83 lines

What it actually says

TypeScript Standards Skill

Guides you to write clean, type-safe TypeScript code following best practices.

When to Use

  • Writing new TypeScript code
  • Refactoring JavaScript to TypeScript
  • Reviewing TypeScript for quality
  • Setting up TypeScript projects

Critical Rules

Type Safety

  • Always enable strict: true in tsconfig.json
  • Avoid any - use unknown when type is uncertain
  • Use explicit return types on public functions
  • Enable noImplicitAny and strictNullChecks

Naming Conventions

  • PascalCase for types, interfaces, classes
  • camelCase for variables, functions, methods
  • UPPER_SNAKE_CASE for constants
  • Use descriptive names, avoid abbreviations

Code Organization

  • One class/interface per file (preferably)
  • Group related types in dedicated files
  • Export types explicitly
  • Use barrel exports (index.ts) for clean imports

Best Practices

  • Prefer interface over type for object shapes
  • Use discriminated unions for complex state
  • Leverage generics for reusable code
  • Use readonly for immutable properties
  • Prefer const assertions for literal types

Workflow

  1. Setup: Ensure strict mode is enabled
  2. Write: Follow naming and type conventions
  3. Review: Check for any usage and implicit types
  4. Refine: Add explicit types where inference fails

Examples

Good

interface User {
  readonly id: string;
  name: string;
  email: string;
}

function getUserById(id: string): Promise<User | null> {
  // Implementation
}

Bad

type User = any;

function getUser(id) {
  return fetch(`/users/${id}`);
}
  • /react-typescript - React-specific TypeScript patterns
  • /vue3-typescript - Vue 3 TypeScript integration
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. yesterday First seen · 83 lines · 12 tokens per session scan A 6fdd61215dc2

Subscribe to this mod's changes

typescript-standards is a skill published in the GitHub repository usrrname/cursorrules (10 stars, last pushed 4mo ago), licensed ISC. It adds 12 tokens to every session and 462 once invoked, about $0.0001 per session on Opus 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.