typescript-strict

A set of strict TypeScript and Zod validation rules. TypeScript is a language that adds checked types to JavaScript, while Zod checks that incoming data has the expected shape at runtime.

In plain words
What is it for?
Use it to configure strict TypeScript, validate form data, JSON requests, webhooks, and URL parameters, and require declared return types for server actions and API routes.
Why use it?
It catches unclear or invalid data at application boundaries and avoids the unsafe any type, making API and server code easier to check.

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/vibestackdev/vibe-stack/typescript-strict
Clone the repo
git clone --depth 1 https://github.com/vibestackdev/vibe-stack

Made for: Cursor.

Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 577 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.00577
Opus 5 $0.00000 $0.00289
Sonnet 5 $0.00000 $0.00115
Haiku 4.5 $0.00000 $0.00058

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

Security

Grade A, and why

typescript-strict 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-strict.mdc · 73 lines

How it starts

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

Strict TypeScript & Zod

Core Rules

  • tsconfig.json MUST have strict: true
  • NEVER use any — use unknown and narrow with type guards
  • ALWAYS provide explicit return types for Server Actions and API routes
  • Prefer interface over type for public API contracts (better error messages, extendable)

The any Ban

// ❌ NEVER
function process(data: any) { return data.name }

// ✅ Use unknown + narrowing
function process(data: unknown): string {
  if (typeof data === 'object' && data !== null && 'name' in data) {
    return (data as { name: string }).name
  }
  throw new Error('Invalid data shape')
}

// ✅ Or better — use Zod
const DataSchema = z.object({ name: z.string() })
function process(data: unknown): string {
  const parsed = DataSchema.parse(data)
  return parsed.name
}

Zod at Every Boundary

Validate ALL external input at these boundaries:

  1. Server ActionsformData from client
  2. Route Handlersrequest.json() from external callers
  3. Webhooks — payload from Stripe, GitHub, etc.
  4. URL paramssearchParams from user-controlled URLs
const CreateTodoSchema = z.object({
  title: z.string().min(1, 'Title is required').max(200),
  priority: z.enum(['low', 'medium', 'high']).default('medium'),
  dueDate: z.string().datetime().optional(),
})

type CreateTodoInput = z.infer<typeof CreateTodoSchema>

export async function createTodo(formData: FormData): Promise<ActionResponse> {
  const parsed = CreateTodoSchema.safeParse({
    title: formData.get('title'),
    priority: formData.get('priority'),
    dueDate: formData.get('dueDate'),
  })

  if (!parsed.success) {
    return { success: false, error: parsed.error.issues[0].message }
  }

  // proceed with parsed.data (fully typed as CreateTodoInput)
}

Utility Types You Should Use

  • Partial<T> for optional updates
  • Pick<T, 'field1' | 'field2'> for selecting fields
  • Omit<T, 'id' | 'created_at'> for create inputs
  • Record<string, unknown> instead of object or {}
  • NonNullable<T> to strip null/undefined

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

Subscribe to this mod's changes

typescript-strict is a cursor rule published in the GitHub repository vibestackdev/vibe-stack (7 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 577 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.