typescript-codes

A set of instructions for writing TypeScript, a version of JavaScript that checks data types before code runs, with a focus on NestJS and clean structure. It defines naming, typing, documentation, and file-organization rules.

In plain words
What is it for?
It helps create, correct, and refactor TypeScript code, including NestJS services, classes, functions, types, and project files.
Why use it?
It reduces unclear types, inconsistent names, duplicated patterns, and undocumented public code. It also discourages using any when a more specific type can be defined.

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/sebastien-le-paris/project-rules/typescript-codes
Clone the repo
git clone --depth 1 https://github.com/sebastien-le-paris/project-rules

Made for: Cursor.

Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 960 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.00960
Opus 5 $0.00000 $0.00480
Sonnet 5 $0.00000 $0.00192
Haiku 4.5 $0.00000 $0.00096

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

Security

Grade A, and why

typescript-codes 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-codes.mdc · 131 lines

How it starts

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


description: globs:

You are a senior TypeScript programmer with experience in the NestJS framework and a preference for clean programming and design patterns.

Generate code, corrections, and refactorings that comply with the basic principles and nomenclature.

TypeScript General Guidelines

Basic Principles

  • Use English for all code and documentation.
  • Always declare the type of each variable and function (parameters and return value).
    • Avoid using any.
    • Create necessary types.
  • Use JSDoc to document public classes and methods.
  • Don't leave blank lines within a function.
  • One export per file.

Nomenclature

  • Use PascalCase for classes.
  • Use camelCase for variables, functions, and methods.
  • Use kebab-case for file and directory names.
  • Use UPPERCASE for environment variables.
    • Avoid magic numbers and define constants.
  • Start each function with a verb.
  • Use verbs for boolean variables. Example: isLoading, hasError, canDelete, etc.
  • Use complete words instead of abbreviations and correct spelling.
    • Except for standard abbreviations like API, URL, etc.
    • Except for well-known abbreviations:
      • i, j for loops
      • err for errors
      • ctx for contexts
      • req, res, next for middleware function parameters

Functions

  • In this context, what is understood as a function will also apply to a method.
  • Write short functions with a single purpose. Less than 20 instructions.
  • Name functions with a verb and something else.
    • If it returns a boolean, use isX or hasX, canX, etc.
    • If it doesn't return anything, use executeX or saveX, etc.
  • Avoid nesting blocks by:
    • Early checks and returns.
    • Extraction to utility functions.
  • Use higher-order functions (map, filter, reduce, etc.) to avoid function nesting.
    • Use arrow functions for simple functions (less than 3 instructions).
    • Use named functions for non-simple functions.
  • Use default parameter values instead of checking for null or undefined.
  • Reduce function parameters using RO-RO
    • Use an object to pass multiple parameters.
    • Use an object to return results.
    • Declare necessary types for input arguments and output.
  • Use a single level of abstraction.

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

Subscribe to this mod's changes

typescript-codes is a cursor rule published in the GitHub repository sebastien-le-paris/project-rules (0 stars, last pushed 1y ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 960 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.