typescript

A set of coding guidelines for TypeScript, a version of JavaScript that checks data types before code runs. It emphasizes strict checking, modern modules, clear object and union types, and using unknown instead of any for untrusted data.

In plain words
What is it for?
Use it when writing or reviewing TypeScript, configuring tsconfig.json, defining data models, handling external input, and choosing between interfaces, type aliases, and checked unknown values.
Why use it?
It catches more mistakes during development and makes assumptions about data explicit. This helps prevent unsafe code that silently accepts values of the wrong shape.

Cursor rule

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 rules/renvia-code/best-cursor-rules/typescript
Clone the repo
git clone --depth 1 https://github.com/Renvia-code/best-cursor-rules
Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 1,706 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.00000 $0.01706
Opus 5 $0.00000 $0.00853
Sonnet 5 $0.00000 $0.00341
Haiku 4.5 $0.00000 $0.00171

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

Security

Grade A, and why

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

rules/languages/typescript.mdc · 336 lines

How it starts

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

TypeScript Best Practices

Overview

Setting Recommendation
Strict Mode Always enabled
Target ES2022+
Module ESNext
No any Use unknown instead

Type Fundamentals

Prefer interface for Objects

// ✅ Use interface for object shapes
interface User {
  id: string
  name: string
  email: string
}

// ✅ Use type for unions, intersections, primitives
type Status = 'pending' | 'active' | 'inactive'
type ID = string | number
type UserWithRole = User & { role: string }

Avoid any, Use unknown

// ❌ Bad - any bypasses type checking
function process(data: any) {
  return data.something  // No error, but unsafe
}

// ✅ Good - unknown requires type checking
function process(data: unknown) {
  if (typeof data === 'object' && data !== null && 'something' in data) {
    return (data as { something: string }).something
  }
  throw new Error('Invalid data')
}

Strict Mode Settings

// tsconfig.json
{
  "compilerOptions": {
    "strict": true,
    "noUncheckedIndexedAccess": true,
    "noImplicitReturns": true,
    "noFallthroughCasesInSwitch": true,
    "exactOptionalPropertyTypes": true
  }
}

Type Patterns

Discriminated Unions

// ✅ Use discriminated unions for state
type AsyncState<T> =
  | { status: 'idle' }
  | { status: 'loading' }
  | { status: 'success'; data: T }
  | { status: 'error'; error: Error }

function handle<T>(state: AsyncState<T>) {
  switch (state.status) {
    case 'idle':
      return 'Ready'
    case 'loading':
      return 'Loading...'
    case 'success':
      return state.data  // TypeScript knows data exists
    case 'error':
      return state.error.message
  }
}

Const Assertions

// ✅ Use as const for literal types
const ROLES = ['admin', 'user', 'guest'] as const
type Role = typeof ROLES[number]  // 'admin' | 'user' | 'guest'

const CONFIG = {
  api: 'https://api.example.com',
  timeout: 5000,
} as const

Read the full file on GitHub · 336 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. yesterday First seen · 336 lines · 0 tokens per session scan A d0b50baa09ab

Subscribe to this mod's changes

typescript is a cursor rule published in the GitHub repository Renvia-code/best-cursor-rules (12 stars, last pushed 9mo ago), licensed CC0-1.0. It costs nothing until one of its globs matches a file; then it loads 1,706 tokens. 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-30.