900-project-specific

A set of project-specific rules for a system with a PHP/Symfony API and a Vue.js frontend in a monorepo, meaning one repository containing multiple related applications. It also documents architecture, authentication, state management, APIs, and testing conventions.

In plain words
What is it for?
Guiding backend and frontend changes, REST API work, JWT and OAuth authentication, Vuex state management, and Codeception or Vitest tests.
Why use it?
It keeps code, labels, architecture, authentication, and tests consistent with the existing project.

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

Made for: Cursor.

Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 738 The whole file, excluding the scripts and references it only reads on demand.
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.00000 $0.00738
Opus 5 $0.00000 $0.00369
Sonnet 5 $0.00000 $0.00148
Haiku 4.5 $0.00000 $0.00074

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

Security

Grade A, and why

900-project-specific 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.

emush/.cursor/rules/900-project-specific.mdc · 100 lines

How it starts

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

Project-Specific Rules Template

1.0.0

Context

  • This file is used as specification only for this project

Recommendation

Languages

  • For code and logs: English
  • For labels: English language in UI and errors

Overall Architecture

  • Project structure: Monorepo with API (PHP/Symfony) and App (Vue.js frontend)
  • Architectural patterns used: Domain-Driven Design, Clean Architecture, Command and Query Segregation, and in-memory object repositories for testing

Authentication

  • Authentication mechanisms used: JWT Authentication with Lexik JWT Bundle
  • External authentication: Integration with Eternaltwin OAuth

State Management

  • State management approach: Vuex
  • Organization of stores: Feature-based stores

API and Services

  • Backend structure: Domain-first organization with bounded contexts in separate folders
  • API conventions: RESTful API with API Platform

Testing

  • Testing strategy: Unit tests first with in-memory repositories, functional tests when needed
  • Testing frameworks: Codeception for backend, Vitest for frontend
  • Test patterns: Given-When-Then and test doubles using in-memory repositories

Custom for this project

Backend (PHP/Symfony)

Domain Organization
  • The codebase is organized by domain bounded contexts (Action, Alert, Chat, Communications, Daedalus, Disease, Equipment, Game, Hunter, etc.)
  • Each domain has its own set of entities, repositories, services, and interfaces following DDD principles
Testing
  • Unit tests use in-memory repositories and service implementations
  • Functional tests use Codeception
  • Tests follow the Given-When-Then pattern with descriptive method names
Controllers
  • API controllers handle HTTP requests and return responses
  • Controllers interact with application services that encapsulate domain logic

Frontend (Vue.js)

Structure
  • Vue 3 with TypeScript
  • Phaser for game-related functionality
  • Vue Router for navigation
  • Vuex for state management

Read the full file on GitHub · 100 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 · 100 lines · 738 tokens per session scan A 71ca37ff426a

Subscribe to this mod's changes

900-project-specific is a cursor rule published in the GitHub repository cmnemoi/cursor-rules (2 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 738 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.