001-project-standards

001-project-standards is a cursor rule for Cursor from phuoctrung-ppt/ai-sdlc-workflow. It costs 412 tokens per session, scanned A, original, MIT.

A set of general coding standards for a TypeScript or JavaScript project, including project-specific instructions, module structure, input validation, dependency handling, and frontend rendering choices.

In plain words
What is it for?
Use it when implementing or reviewing backend routes, frontend features, shared types, module boundaries, validation, logging, and asynchronous loading or error states.
Why use it?
It reduces inconsistent code and common design mistakes, such as putting business logic in route handlers or leaving access rules unclear.

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/phuoctrung-ppt/ai-sdlc-workflow/001-project-standards
Clone the repo
git clone --depth 1 https://github.com/phuoctrung-ppt/ai-sdlc-workflow

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.

agentmods badge for 001-project-standards

README.md
[![agentmods](https://agentmods.dev/badge/rules/phuoctrung-ppt/ai-sdlc-workflow/001-project-standards.svg)](https://agentmods.dev/rules/phuoctrung-ppt/ai-sdlc-workflow/001-project-standards)
Your own site
<a href="https://agentmods.dev/rules/phuoctrung-ppt/ai-sdlc-workflow/001-project-standards"><img src="https://agentmods.dev/badge/rules/phuoctrung-ppt/ai-sdlc-workflow/001-project-standards.svg" alt="Measured on agentmods" height="20"></a>
Per session 412 This file is loaded in full into every session.
When invoked 412 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.1 $0.00412 $0.00412
Opus 5 $0.00206 $0.00206
Sonnet 5 $0.00082 $0.00082
Haiku 4.5 $0.00041 $0.00041

Measured 5d ago against content hash 65723e0f216e, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-05, from the pricing page.

Security

Grade A, and why

001-project-standards 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 5d 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/001-project-standards.mdc · 44 lines

What it actually says

Project Standards

You are a senior engineer on this project. Full project spec: AGENTS.md.

Always read .memory/constraints.md and AGENTS.md §2 before implementing. Domain patterns load via context-builder tier2 skills.

TypeScript / JavaScript

  • strict: true, no any without eslint-disable + justification comment
  • unknown + type guards for uncertain types; interface for object shapes; type for unions/intersections
  • Barrel exports (index.ts) per module
  • No console.log in production code — use the project's structured logger (see AGENTS.md §2)

Backend (any framework)

  • One feature = one module/package (controller/route, service, schemas/DTOs)
  • Constructor/dependency injection only; business logic in services, never in route handlers
  • Every route: explicitly public OR explicitly protected — no ambiguity
  • Input validated at the boundary (schema validation, type coercion, sanitization)

Frontend (any framework)

  • Server/static rendering by default; client-side only when interactivity or browser APIs require it
  • Shared type/schema contracts from the shared package (see AGENTS.md §3)
  • Loading and error states implemented for every async boundary
  • No hardcoded API keys or secrets in client code

Database

  • Schema changes always via migration — never ORM auto-sync
  • Parameterized queries only — no string-interpolated SQL
  • Both up() and down() in every migration

Git

  • Conventional Commits: type(scope): description (e.g. feat(auth): add refresh token rotation)
  • Branches: feature/description, fix/description, chore/description
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. 5d ago First seen · 44 lines · 412 tokens per session scan A 65723e0f216e

Subscribe to this mod's changes

001-project-standards is a cursor rule published in the GitHub repository phuoctrung-ppt/ai-sdlc-workflow (2 stars, last pushed 19d ago), licensed MIT. It adds 412 tokens to every session, about $0.0021 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-31.