Day 4: Cursor Rules: Teach Cursor Your Codebase Standards

Tech stack specifics:
  Python 3.12, FastAPI, SQLAlchemy, PostgreSQL

Code style:
  Use type hints always. No raw SQL (use ORM). 
  Async by default for route handlers.

Architecture patterns:
  Separate routes/ models/ services/ — no business logic in routes

What to avoid:
  Never use eval(). No print() statements (use logging).

Testing:
  pytest with fixtures in conftest.py. Test all error cases.

# Project: My AI API
# Stack: Python 3.12, FastAPI, SQLAlchemy, PostgreSQL

Code Style:
- Use type hints on all function signatures
- Use Pydantic BaseModel for all request/response bodies
- Route handlers are always async
- Use f-strings, not .format()

Architecture:
- routes/ for HTTP handlers (no business logic)
- services/ for business logic
- models/ for database models
- schemas/ for Pydantic models

Error Handling:
- Always use HTTPException with specific status codes
- Log errors with logger.error(), not print()
- Never expose stack traces in API responses

Testing:
- pytest with TestClient
- Each endpoint needs: success case, 400 case, auth failure case
- Use factory_boy for test data

Never:
- No raw SQL queries (use SQLAlchemy ORM)
- No synchronous I/O in async functions
- No hardcoded credentials

# Writing Project Rules

Voice: Direct and conversational. No jargon.
Sentence length: Vary between short (5 words) and medium (20 words).
Never use: "leverage", "utilize", "synergize", "game-changing"
Headers: Sentence case (not Title Case)
Code examples: Always include, always runnable
Tone: Teach don't preach. Assume smart reader, not expert.