code-organization

code-organization is a cursor rule for Cursor from jaycewalzer1/SilverKey-Inc.. It costs 0 tokens per session (2,187 once invoked), scanned A, original, MIT.

A set of rules for organizing code by limiting file size and guiding where methods should be placed.

In plain words
What is it for?
Use it when deciding how large files should be and where new methods belong.
Why use it?
It gives developers consistent boundaries for keeping code files and methods organized.

Cursor rule for Cursor

Written for Cursor: installed under .cursor/.

Needs its repository: it reads a path above its own folder, which exists only inside the repository. The line is import { parseEvents } from '../../../packages/utils/calendar/eventParsing';.

Good fit Use it when deciding how large files should be and where new methods belong.

Compare 6 cursor rules from other repositories ↓
Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo
git clone --depth 1 https://github.com/jaycewalzer1/SilverKey-Inc.
agentmods
npx agentmods add rules/jaycewalzer1/silverkey-inc./code-organization

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 code-organization

README.md
[![agentmods](https://agentmods.dev/badge/rules/jaycewalzer1/silverkey-inc./code-organization/github.svg)](https://agentmods.dev/rules/jaycewalzer1/silverkey-inc./code-organization)
Your own site
<a href="https://agentmods.dev/rules/jaycewalzer1/silverkey-inc./code-organization"><img src="https://agentmods.dev/badge/rules/jaycewalzer1/silverkey-inc./code-organization/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for code-organization

Your own site · 80×15
<a href="https://agentmods.dev/rules/jaycewalzer1/silverkey-inc./code-organization"><img src="https://agentmods.dev/badge/rules/jaycewalzer1/silverkey-inc./code-organization.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 2,187 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.00000 $0.02187
Opus 5.5 $0.00000 $0.00875
Sonnet 5.5 $0.00000 $0.00437
Haiku 4.5 $0.00000 $0.00219

Measured 1mo ago against content hash 3ea347bc3017, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

code-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 1mo 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/shared/code-organization.mdc · 264 lines

How it starts

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

Code Organization Rules

File Size and Method Placement

Prefer New Files for Large Methods

When adding large methods or substantial functionality, PREFER creating new files over expanding existing files to very large sizes.

Guidelines:

  • ✅ Create a new file when adding a method that:

    • Exceeds ~100-150 lines of code
    • Has complex logic with multiple responsibilities
    • Would push an existing file over ~400-500 lines
    • Is a distinct feature or capability that can be logically separated
  • ✅ Extract to a new file when an existing file:

    • Exceeds ~500 lines and you're adding more functionality
    • Contains multiple distinct concerns that can be separated
    • Has methods that are rarely used together
  • ✅ Keep related functionality together when:

    • Methods are tightly coupled and always used together
    • The file is still under ~400 lines
    • Splitting would create unnecessary indirection

File Organization Patterns

Frontend (TypeScript/React)

Services:

// ✅ CORRECT: Split large service into focused modules
// services/calendar/core/service.ts (main service)
// services/calendar/events/operations.ts (event operations)
// services/calendar/calendars/management.ts (calendar management)

// ❌ AVOID: Single massive service file
// services/calendar/service.ts (1000+ lines with everything)

Hooks:

// ✅ CORRECT: Separate hooks by concern
// hooks/data/useCalendarEvents.ts
// hooks/data/useCalendarPreferences.ts
// hooks/data/useCalendarAvailability.ts

// ❌ AVOID: Single hook file with multiple large hooks
// hooks/data/useCalendar.ts (500+ lines with all calendar hooks)

Components:

// ✅ CORRECT: Extract large components or logic; utilities live in packages
// packages/features/calendar/components/Calendar.tsx (main component)
// packages/features/calendar/components/CalendarView.tsx
// packages/utils/calendar/eventParsing.ts (utilities – not under apps/web)

// ❌ AVOID: Single massive component file
// features/calendar/Calendar.tsx (800+ lines with everything)

// ❌ AVOID: Standalone .ts utilities under apps/web/features or components
// features/calendar/utils/eventParsing.ts

Read the full file on GitHub · 264 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. 1mo ago First seen · 264 lines · 0 tokens per session scan A 3ea347bc3017

Subscribe to this mod's changes

code-organization is a cursor rule published in the GitHub repository jaycewalzer1/SilverKey-Inc. (2 stars, last pushed 3d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,187 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.