cursorrules

A set of coding rules for SerpentStack, a full-stack template built with FastAPI, React, PostgreSQL, and Terraform. It describes the project’s architecture, required patterns, and conventions for backend, frontend, testing, and infrastructure code.

In plain words
What is it for?
Use it when developing SerpentStack features, routes, services, database models, frontend code, tests, or Terraform infrastructure while following the template’s established conventions.
Why use it?
It gives an agent consistent project-specific expectations when adding or changing code. This reduces mismatches such as using synchronous database code where the project requires asynchronous code.

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/benja-pauls/serpentstack/cursorrules
Clone the repo
git clone --depth 1 https://github.com/Benja-Pauls/SerpentStack

Made for: Cursor.

Per session 1,052 This file is loaded in full into every session.
When invoked 1,052 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.01052 $0.01052
Opus 5 $0.00526 $0.00526
Sonnet 5 $0.00210 $0.00210
Haiku 4.5 $0.00105 $0.00105

Measured yesterday against content hash 97cd53520bb8, 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 · 92 lines

How it starts

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

SerpentStack — Cursor Rules

You are working on SerpentStack, a fullstack template: FastAPI + React + PostgreSQL + Terraform.

Architecture

  • Backend: FastAPI, Python 3.12+, async SQLAlchemy 2.0 (asyncpg), Alembic, pydantic-settings, structlog, SlowAPI, Sentry SDK, ARQ
  • Frontend: React 18, Vite, TypeScript (strict), Tailwind CSS v4, React Router, React Query, shadcn/ui
  • Cache/Queue: Redis 7 (rate limiting, background tasks)
  • Database: PostgreSQL 16 (Docker locally, RDS in production)
  • Testing: pytest + testcontainers (real Postgres), httpx AsyncClient, Vitest
  • Infrastructure: Terraform, AWS (App Runner, ECR, RDS, S3)

Key Conventions

Python / Backend

  • All route handlers and service methods MUST be async def
  • Use AsyncSession from sqlalchemy.ext.asyncio — never sync Session
  • Services return None or domain values — NEVER raise HTTPException in services
  • Services flush() but do NOT commit() — routes own the transaction boundary
  • Routes translate service results to HTTP responses (None → 404, etc.) and call await db.commit() after mutations
  • New models MUST be imported in backend/app/models/__init__.py for Alembic to detect them
  • Use get_logger(__name__) with structured event-style logging: logger.info("event_name", key=value)
  • UUID primary keys on all models — never integer IDs
  • Pydantic schemas in schemas/ — never expose ORM models directly
  • API routes prefixed with /api/v1/
  • Protect routes with Depends(get_current_user) from routes/auth.py — returns UserInfo
  • Database engine is lazily initialized (not at import time)
  • Line length: 100 characters
  • Formatter/linter: ruff

TypeScript / Frontend

  • Strict mode — no any without justifying comment
  • Named exports for hooks and utilities (components may use default exports)
  • Types auto-generated from OpenAPI spec via make types — prefer generated types over hand-written
  • Use React Query for data fetching, React Router for routing
  • Tailwind CSS v4 for styling

Read the full file on GitHub · 92 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 · 92 lines · 1,052 tokens per session scan A 97cd53520bb8

Subscribe to this mod's changes

cursorrules is a cursor rule published in the GitHub repository Benja-Pauls/SerpentStack (2 stars, last pushed 5mo ago), licensed MIT. It adds 1,052 tokens to every session, about $0.0053 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.