typescript-rules

A set of TypeScript rules that requires explicit types and rejects unsafe shortcuts such as any, as any, and unexplained error-suppression comments. TypeScript is JavaScript with optional type checking.

In plain words
What is it for?
Use it when writing or reviewing TypeScript interfaces, function signatures, error types, and code that uses type assertions.
Why use it?
It prevents type information from being weakened and makes function inputs, outputs, objects, and errors clearer.

Cursor rule for Cursor

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/sethdford/flowx/typescript-rules
Clone the repo
git clone --depth 1 https://github.com/sethdford/flowx

Made for: Cursor.

Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 2,931 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.02931
Opus 5 $0.00000 $0.01465
Sonnet 5 $0.00000 $0.00586
Haiku 4.5 $0.00000 $0.00293

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

Security

Grade A, and why

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

.cursor/rules/typescript-rules.mdc · 473 lines

How it starts

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

TypeScript Rules: Zero Tolerance for Type Errors + Community Wisdom

🚨 CRITICAL TYPE SAFETY RULES

NEVER Use These (Auto-Reject)

// ❌ FORBIDDEN - Will break our type safety
any
@ts-ignore  // without detailed explanation
@ts-expect-error  // without test case
as any
<any>
Function  // Use proper function signatures
Object    // Use proper object types
{}        // Use proper interface/type

ALWAYS Use These Patterns

// ✅ REQUIRED - Proper type definitions
interface UserData {
  readonly id: string;
  readonly name: string;
  readonly email: string;
  readonly createdAt: Date;
}

// ✅ REQUIRED - Proper error types
type ApiError = {
  readonly code: string;
  readonly message: string;
  readonly details?: Record<string, unknown>;
};

// ✅ REQUIRED - Proper function signatures
type ProcessUser = (user: UserData) => Promise<ProcessResult>;
type ValidateInput = <T>(input: unknown, schema: Schema<T>) => T;

📝 COMMUNITY-PROVEN PATTERNS

1. Functional Programming with Types

// ✅ REQUIRED - Functional and declarative patterns
// From cursor.directory research: "Use functional and declarative programming patterns; avoid classes"

// ❌ FORBIDDEN - Classes
class UserProcessor {
  process(user: User): Result { /* ... */ }
}

// ✅ REQUIRED - Functional approach with proper types
type UserProcessor = (user: User) => Result;
type ProcessResult<T> = {
  readonly success: boolean;
  readonly data?: T;
  readonly error?: string;
};

const processUser: UserProcessor = (user) => {
  // Process functionally
  return { success: true, data: transformedUser };
};

2. Interface over Types (Community Standard)

// ✅ REQUIRED - Use interfaces for object shapes
// From research: "Use TypeScript for all code; prefer interfaces over types"

interface ComponentProps {
  readonly title: string;
  readonly onComplete: (result: CompletionResult) => void;
  readonly isLoading?: boolean;
}

interface ApiResponse<T> {
  readonly data: T;
  readonly status: number;
  readonly message: string;
}

// ✅ REQUIRED - Types for unions and computations
type Status = 'idle' | 'loading' | 'success' | 'error';
type EventHandler<T> = (event: T) => void;

Read the full file on GitHub · 473 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 · 473 lines · 0 tokens per session scan A 4e9d98d22748

Subscribe to this mod's changes

typescript-rules is a cursor rule published in the GitHub repository sethdford/flowx (2 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,931 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-31.