What is backend-conventions?

Coding rules for the backend and command-line parts of cursor-doctor, a TypeScript program that checks project documentation and generates improvement plans.

They are for adding commands, organizing business logic, handling failures, reading project files, and updating related documentation.

They keep code structure, naming, errors, file handling, and command behavior consistent as the program grows.

backend-conventions — Cursor rule for Cursor by ajgreyling: Coding rules for the backend and command-line parts of…

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/ajgreyling/cursor-doctor/backend-conventions

Clone the repo

git clone --depth 1 https://github.com/ajgreyling/cursor-doctor

Made for: Cursor.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/rules/ajgreyling/cursor-doctor/backend-conventions.svg)](https://agentmods.dev/rules/ajgreyling/cursor-doctor/backend-conventions)

Your own site

<a href="https://agentmods.dev/rules/ajgreyling/cursor-doctor/backend-conventions"><img src="https://agentmods.dev/badge/rules/ajgreyling/cursor-doctor/backend-conventions.svg" alt="Measured on agentmods" height="20"></a>

Per session 0 Nothing until a file matches its globs; then the whole rule loads.

When invoked 320 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.

Model	Per session	Once invoked
Fable 5	$0.00000	$0.00320
Opus 5	$0.00000	$0.00160
Sonnet 5	$0.00000	$0.00064
Haiku 4.5	$0.00000	$0.00032

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

Security

Grade A, and why

backend-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 3d 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/backend-conventions.mdc · 47 lines

What it actually says

Backend Conventions (CLI Core)

Stack and structure

Runtime: Node.js CLI in TypeScript (type: module).
Keep executable orchestration in src/index.ts.
Keep pure business logic in focused modules (scanner, analyzer, prescription, catalog, types).

Naming and module patterns

Use camelCase for functions and variables.
Use PascalCase for exported types/interfaces.
Keep one responsibility per function and keep helpers close to usage.
Prefer explicit return types for exported functions.

Error handling

Let command handlers throw meaningful errors.
Handle top-level failures in main().catch(...) and exit non-zero.
Avoid swallowing parsing/read errors unless intentionally best-effort (for file discovery resilience).

I/O conventions

Read/write files using fs/promises.
Resolve paths relative to --project root.
Keep output deterministic for auditability (stable ordering and concise summaries).

Adding a new command

Extend the Command union and parseCommand.
Add a dedicated run<Command> handler.
Reuse existing scanner/analyzer/prescription types where possible.
Update README.md, docs/ARCHITECTURE.md, and openapi.yaml.

Completeness checklist

language/framework
naming
error handling
file/package structure

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.

3d ago First seen · 47 lines · 0 tokens per session scan A aa1f6c84defc

Subscribe to this mod's changes

backend-conventions is a cursor rule published in the GitHub repository ajgreyling/cursor-doctor (0 stars, last pushed 29d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 320 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.

Backend and APIs Languages TypeScript cursor developer-tools mcp

app_rules

This document outlines the essential rules and guidelines for developing with the MobileLauncher LT boilerplate. Follow these rules to maintain consistency, scalability, and code quality across the project.

chohra-med/expo_boilerplate · 12,680 tokens

app_feature_first_architecture

Feature-first architecture is a design pattern that organizes code by business features rather than technical layers. This approach promotes better maintainability, scalability, and team collaboration by keeping related functionality together and reducing coupling between different parts of the application.

chohra-med/expo_boilerplate · 6,279 tokens

backend-conventions