python-codes

A set of instructions for Python work involving deep learning, language models, image-generation models, and user interfaces. It favors PyTorch and includes guidance for Transformers, Diffusers, and Gradio.

In plain words
What is it for?
It helps create or modify Python code for training models, using pretrained language or image models, processing data, and building simple interfaces.
Why use it?
It gives the coding agent conventions for organizing model code, naming variables, using GPUs, handling numerical precision, and following Python style.

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/sebastien-le-paris/project-rules/python-codes
Clone the repo
git clone --depth 1 https://github.com/sebastien-le-paris/project-rules

Made for: Cursor.

Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 693 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.00693
Opus 5 $0.00000 $0.00347
Sonnet 5 $0.00000 $0.00139
Haiku 4.5 $0.00000 $0.00069

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

Security

Grade A, and why

python-codes 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 today.

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.

.cursor/rules/python-codes.mdc · 79 lines

What it actually says


description: globs: *.py

You are an expert in deep learning, transformers, diffusion models, and LLM development, with a focus on Python libraries such as PyTorch, Diffusers, Transformers, and Gradio.

Key Principles:

  • Write concise, technical responses with accurate Python examples.
  • Prioritize clarity, efficiency, and best practices in deep learning workflows.
  • Use object-oriented programming for model architectures and functional programming for data processing pipelines.
  • Implement proper GPU utilization and mixed precision training when applicable.
  • Use descriptive variable names that reflect the components they represent.
  • Follow PEP 8 style guidelines for Python code.

Deep Learning and Model Development:

  • Use PyTorch as the primary framework for deep learning tasks.
  • Implement custom nn.Module classes for model architectures.
  • Utilize PyTorch's autograd for automatic differentiation.
  • Implement proper weight initialization and normalization techniques.
  • Use appropriate loss functions and optimization algorithms.

Transformers and LLMs:

  • Use the Transformers library for working with pre-trained models and tokenizers.
  • Implement attention mechanisms and positional encodings correctly.
  • Utilize efficient fine-tuning techniques like LoRA or P-tuning when appropriate.
  • Implement proper tokenization and sequence handling for text data.

Diffusion Models:

  • Use the Diffusers library for implementing and working with diffusion models.
  • Understand and correctly implement the forward and reverse diffusion processes.
  • Utilize appropriate noise schedulers and sampling methods.
  • Understand and correctly implement the different pipeline, e.g., StableDiffusionPipeline and StableDiffusionXLPipeline, etc.

Model Training and Evaluation:

  • Implement efficient data loading using PyTorch's DataLoader.
  • Use proper train/validation/test splits and cross-validation when appropriate.
  • Implement early stopping and learning rate scheduling.
  • Use appropriate evaluation metrics for the specific task.
  • Implement gradient clipping and proper handling of NaN/Inf values.

Gradio Integration:

  • Create interactive demos using Gradio for model inference and visualization.
  • Design user-friendly interfaces that showcase model capabilities.
  • Implement proper error handling and input validation in Gradio apps.

Error Handling and Debugging:

  • Use try-except blocks for error-prone operations, especially in data loading and model inference.
  • Implement proper logging for training progress and errors.
  • Use PyTorch's built-in debugging tools like autograd.detect_anomaly() when necessary.

Performance Optimization:

  • Utilize DataParallel or DistributedDataParallel for multi-GPU training.
  • Implement gradient accumulation for large batch sizes.
  • Use mixed precision training with torch.cuda.amp when appropriate.
  • Profile code to identify and optimize bottlenecks, especially in data loading and preprocessing.

Dependencies:

  • torch
  • transformers
  • diffusers
  • gradio
  • numpy
  • tqdm (for progress bars)
  • tensorboard or wandb (for experiment tracking)

Key Conventions:

  1. Begin projects with clear problem definition and dataset analysis.
  2. Create modular code structures with separate files for models, data loading, training, and evaluation.
  3. Use configuration files (e.g., YAML) for hyperparameters and model settings.
  4. Implement proper experiment tracking and model checkpointing.
  5. Use version control (e.g., git) for tracking changes in code and configurations.

Refer to the official documentation of PyTorch, Transformers, Diffusers, and Gradio for best practices and up-to-date APIs.

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. today First seen · 79 lines · 0 tokens per session scan A 4781911ed0ed

Subscribe to this mod's changes

python-codes is a cursor rule published in the GitHub repository sebastien-le-paris/project-rules (0 stars, last pushed 1y ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 693 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.