0votes

Cursor rules for Python projects

TemplateLow risk

submitted 16h ago by u/client to c/backend · 0 copies

A .cursor/rules/python.mdc for typed, tested, well-structured Python.

Template · 3 variables

---
description: Python conventions
globs: ["**/*.py"]
alwaysApply: false
---

# Python

- Python {{python_version}}; type hints on every function signature; `mypy` clean.
- Format and lint with ruff (`ruff format`, `ruff check --fix`).
- Small pure functions; side effects (I/O, network, DB) at the edges.
- Use dataclasses or Pydantic models instead of loose dicts for structured data.
- Raise specific exceptions; never use bare `except:`.
- Tests with pytest in `tests/`, mirroring the package layout; use fixtures, not globals.
- Dependencies managed with {{dependency_tool}}; don't add packages without saying why.

## When you change code
- Follow the patterns in the nearest existing file before inventing new ones.
- Add or update a test for behavior changes; run `{{test_command}}`.
- Keep diffs small; explain anything surprising in your reply.

python_version

dependency_tool

test_command

0 commentsreport

How to use this command

Fill in the blanks. Type your details into the boxes above. This command has 3 blanks:

{{python_version}} Python version
{{dependency_tool}} Dependency tool
{{test_command}} Test command

Copy itwith the Copy button. Your answers are filled in automatically. Use “copy raw” to keep the blanks for later.

Paste it into Cursor, Claude, ChatGPT or Codex and send it.

Tip: This produces a file or document. Save the filled-in result in your project (for example as CLAUDE.md or AGENTS.md) so you can reuse it.

Cursor rules for Python projects

How to use this command

More from c/backend