project-structure

A set of coding guidelines for building modern web applications with tools such as Next.js, React, TypeScript, Drizzle, and Cloudflare Workers.

In plain words
What is it for?
Use it when creating, changing, or reviewing a web application that uses the listed technologies.
Why use it?
It gives the coding agent consistent project conventions when working across a web application's frontend, backend, database, and hosting setup.

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/jesseoue/cursor-rules/project-structure
Clone the repo
git clone --depth 1 https://github.com/jesseoue/cursor-rules

Made for: Cursor.

Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 3,222 The whole file, excluding the scripts and references it only reads on demand.
Security scan C 1 finding. Scan, not verified.
Origin unknown 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.03222
Opus 5 $0.00000 $0.01611
Sonnet 5 $0.00000 $0.00644
Haiku 4.5 $0.00000 $0.00322

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

Security

Grade C, and why

project-structure scanned grade C with 1 finding 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.

Recursive force deletehighDestructive command

rm -rf with a variable or a broad path is one typo away from removing the wrong tree.

"clean": "rm -rf .next out dist",
.cursor/rules/project-structure.mdc · 357 lines

The source is not reproduced here

No licence file

A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.

Read it on GitHub

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 · 357 lines · 0 tokens per session scan C 7244f6f8ae57

Subscribe to this mod's changes

project-structure is a cursor rule published in the GitHub repository jesseoue/cursor-rules (6 stars, last pushed 10mo ago), with no licence file. It costs nothing until one of its globs matches a file; then it loads 3,222 tokens. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.