conventions

A set of coding rules for a specific repository, covering error handling, logging, validation, TypeScript, formatting, and package management.

In plain words
What is it for?
Use it while adding or reviewing code to choose the right configuration, error classes, logger, validation schemas, package manager, types, and formatting.
Why use it?
It prevents contributors from using inconsistent patterns or commands that conflict with the project's design and tooling.

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/khaledsaeed18/node-express-boilerplate/conventions
Clone the repo
git clone --depth 1 https://github.com/KhaledSaeed18/node-express-boilerplate

Made for: Cursor.

Per session 664 This file is loaded in full into every session.
When invoked 664 The same file — it is already loaded in full.
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.00664 $0.00664
Opus 5 $0.00332 $0.00332
Sonnet 5 $0.00133 $0.00133
Haiku 4.5 $0.00066 $0.00066

Measured 2d ago against content hash 849c9b159b84, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

conventions 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 2d ago.

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/conventions.mdc · 77 lines

How it starts

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

Hard Rules

Environment variables: Never use process.env directly anywhere. Import the typed config object from src/config/env.ts.

Error handling: Throw from src/errors/index.ts. In controllers, always catch and call this.handleError(error, next) — never res.status().json() on error paths. Available classes: AppError, ValidationError, AuthenticationError, AuthorizationError, NotFoundError, ConflictError, InternalServerError.

Logging: Use the Pino logger from src/config/logger.ts. Never use console.log/warn/error.

Validation: Zod v4 schemas in src/validations/. Use validateBody(schema) from src/lib/validate.ts to produce middleware. Export both the schema type and the RequestHandler from the validation file.

Package manager: pnpm only. Never generate package-lock.json or yarn.lock.

TypeScript

  • Strict mode — no any, no @ts-ignore
  • All type-only imports must use import type
  • Explicit return types on all public methods and class properties
  • No floating promises — always await or .catch()
  • Prefer ?? over || for nullish checks

Formatting (Prettier)

4-space indent · single quotes · semicolons · trailing commas · 100-char line limit

Controller Pattern

Controller methods are arrow function properties (not regular methods) so this is bound correctly when passed as route handlers:

public createFoo = async (req: Request, res: Response, next: NextFunction): Promise<void> => {
    try {
        // ...
        this.sendResponse(res, 201, 'Foo created', data);
    } catch (error) {
        this.handleError(error, next);
    }
};

Repository Pattern

  • Extend BaseRepository
  • Use this.prisma.<model> for all queries
  • In update/delete, wrap Prisma calls in try/catch and call this.handlePrismaError(error)
  • Use this.findManyWithPagination() and this.count() from the base class for list/count operations

Route Pattern

export class FooRoute extends BaseRoute {
    private fooController!: IFooController;

    protected initializeRoutes(): void {
        this.fooController = this.container.getFooController();
        this.router.post('/', fooLimiter, protect, createFooValidation, this.fooController.createFoo);
        // ...
    }
}

const fooRoute = new FooRoute();
const fooRoutes = fooRoute.getRouter();
export default fooRoutes;

Read the full file on GitHub · 77 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. 2d ago First seen · 77 lines · 664 tokens per session scan A 849c9b159b84

Subscribe to this mod's changes

conventions is a cursor rule published in the GitHub repository KhaledSaeed18/node-express-boilerplate (33 stars, last pushed 8d ago), licensed MIT. It adds 664 tokens to every session, about $0.0033 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-30.