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.
npx agentmods add rules/farzannajipour/cursor-react-rules/file-organizationgit clone --depth 1 https://github.com/Farzannajipour/cursor-react-rulesWhat 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.01216 | $0.01216 |
| Opus 5 | $0.00608 | $0.00608 |
| Sonnet 5 | $0.00243 | $0.00243 |
| Haiku 4.5 | $0.00122 | $0.00122 |
Grade A, and why
file-organization 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.
How it starts
The opening of the file, as written. The whole thing — 188 lines — stays where its author put it; the contents beside it link to each section on GitHub.
File Organization Standards
Project Structure
src/
├── app/ # Next.js app directory
│ ├── (auth)/ # Route group
│ ├── (dashboard)/ # Route group
│ ├── api/ # API routes
│ ├── layout.tsx
│ └── page.tsx
├── components/
│ ├── ui/ # Reusable UI components
│ │ ├── Button.tsx
│ │ ├── Input.tsx
│ │ └── Card.tsx
│ └── features/ # Feature-specific components
│ ├── auth/
│ └── dashboard/
├── hooks/ # Custom React hooks
│ ├── useAuth.ts
│ └── useDebounce.ts
├── lib/ # Utilities and helpers
│ ├── api.ts
│ ├── utils.ts
│ └── constants.ts
├── server/ # Server-side code
│ ├── db.ts
│ └── actions/
├── types/ # Shared TypeScript types
│ └── index.ts
└── styles/ # Global styles
└── globals.css
Naming Conventions
Files
- Components: PascalCase -
UserProfile.tsx,Button.tsx - Hooks: camelCase with 'use' prefix -
useAuth.ts,useDebounce.ts - Utilities: camelCase -
formatDate.ts,api.ts - Types: camelCase or PascalCase -
types.ts,User.types.ts - Tests: Match source file -
Button.test.tsx
Variables and Functions
- Components: PascalCase -
UserProfile,Button - Functions: camelCase -
fetchUser,formatDate - Hooks: camelCase with 'use' -
useAuth,useDebounce - Constants: UPPER_SNAKE_CASE -
API_BASE_URL,MAX_RETRY_COUNT - Types/Interfaces: PascalCase -
User,UserProfile,ApiResponse
Component File Structure
Single Component File:
// 1. Imports - React, Next.js, external, internal
import { useState } from 'react';
import Link from 'next/link';
import { cn } from '@/lib/utils';
import { Button } from '@/components/ui/Button';
// 2. Types/Interfaces
interface UserCardProps {
user: User;
onEdit?: () => void;
}
// 3. Component
export function UserCard({ user, onEdit }: UserCardProps) {
const [isExpanded, setIsExpanded] = useState(false);
return (
<div>
{/* JSX */}
</div>
);
}
// 4. Sub-components (if small)
function UserAvatar({ src }: { src: string }) {
return <img src={src} alt="Avatar" />;
}
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.
- 2d ago First seen · 188 lines · 1,216 tokens per session scan A 8802f49b4848
file-organization is a cursor rule published in the GitHub repository Farzannajipour/cursor-react-rules (3 stars, last pushed 7mo ago), licensed MIT. It adds 1,216 tokens to every session, about $0.0061 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.
Other cursor rules, from other repositories
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.
family-instance-domain-actions
Family instance domain action implementation patterns.