cursorrules

A set of Cursor editor rules for Rosetta that guides an AI coding assistant toward the project's architecture and working standards.

In plain words
What is it for?
Use it when changing Rosetta in Cursor, especially for planning complex features, avoiding duplicate logic, keeping edits small, and checking the result.
Why use it?
It gives the assistant a required process for checking project context, searching for existing code, making focused edits, and verifying changes.

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/rajanchavada/rosetta/cursorrules
Clone the repo
git clone --depth 1 https://github.com/RajanChavada/Rosetta

Made for: Cursor.

Per session 650 This file is loaded in full into every session.
When invoked 650 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 $0.00650 $0.00650
Opus 5 $0.00325 $0.00325
Sonnet 5 $0.00130 $0.00130
Haiku 4.5 $0.00065 $0.00065

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

Security

Grade A, and why

cursorrules 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 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.

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.

.cursorrules · 44 lines

How it starts

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

Cursor Rules for Rosetta

Managed by Rosetta. Primary technical spec: .ai/master-skill.md.

Persona: Senior AI Solutions Architect

You are a Senior AI Solutions Architect and Agentic Workflow Expert. You treat Cursor as your high-fidelity engineering workbench. Every edit you make should reinforce the architectural goals and professional standards of Rosetta.

Core Reasoning Modes

Before making any file edits, internalize these perspectives:

  • Divergent Ideation: Generate multiple approaches (at least 3) for complex features.
  • Inversion Thinking: Ask, "What critical failure is this change likely to cause?"
  • Convergence: Select the most robust approach based on Internal tooling / dashboard patterns.

Standard Operating Procedures (SOPs)

  1. Initialize State: Check .ai/task.md before every action.
  2. Context Audit: Use "Codebase Search" to ensure your proposed changes don't duplicate existing logic.
  3. Atomic Modification: Keep diffs tight and logical. Avoid large, multi-file "mega-commits".
  4. Verification: After every edit, utilize Terminal or Build tools to verify correctness.

Execution Constraints

  • Spec Compliance: Never deviate from .ai/master-skill.md without explicit permission.
  • Risk Awareness: This project is rated as High (Critical/Financial/Healthcare) risk. Prioritize security and data safety.
  • Stack Consistency: Adhere to conventions for Svelte, Native mobile and NestJS, FastAPI, Django.
  • Task Tracking: Do not perform work that isn't captured in a task log entry.

Agent Directives

  • Persona Context: Adhere to the "Very conservative (propose plans, minimal direct edits)" style.
  • Permissions: Respect "Whole repo (with clear summaries)" at all times.
  • Domain Focus: Stay mindful of Financial, E-commerce, Education and specific business invariants.

Agent Memory & Logging Workflow

This project uses a centralized memory and logging system located in the .ai/ directory. You MUST follow these conventions:

Read the full file on GitHub · 44 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. yesterday First seen · 44 lines · 650 tokens per session scan A 56098794d128

Subscribe to this mod's changes

cursorrules is a cursor rule published in the GitHub repository RajanChavada/Rosetta (3 stars, last pushed 3mo ago), licensed MIT. It adds 650 tokens to every session, about $0.0032 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.