coding-standard-python
Python Coding Standards (PEP 8)
When reviewing or generating Python code, follow these rules:
File Naming
- Source files: Use snake_case (e.g.,
user_service.py,api_client.py) - Package directories: Use snake_case (e.g.,
data_processing/,utils/) - Test files: Use
test_prefix (e.g.,test_user_service.py) - Config files: Use snake_case (e.g.,
config_settings.py)
Variable Naming
- Variables: snake_case (e.g.,
user_name,is_active,total_count) - Constants: UPPER_SNAKE_CASE (e.g.,
MAX_RETRIES,API_BASE_URL) - Boolean variables: Prefix with
is_,has_,can_,should_(e.g.,is_loading,has_error) - Protected variables: Single underscore prefix (e.g.,
_internal_data) - Private variables: Double underscore prefix (e.g.,
__private_data)
More from jdubray/puffin
coding-standard-cpp
Enforce C++ coding standards including camelCase or snake_case variables, PascalCase classes, and consistent file naming.
26coding-standard-java
Enforce Java coding standards including camelCase variables, PascalCase classes, and PascalCase filenames matching class names.
23coding-standard-javascript
Enforce JavaScript/ES6+ and TypeScript coding standards including camelCase variables, PascalCase classes, and kebab-case filenames.
18modularity-patterns
Recommends modularity, composition, and decoupling patterns for design challenges. Use when designing plugin architectures, reducing coupling, improving testability, or separating cross-cutting concerns.
17coding-standard-c
Enforce C coding standards including snake_case variables and functions, UPPER_SNAKE_CASE macros, and snake_case filenames.
16rlm
Run a Recursive Language Model-style loop for long-context tasks. Uses a persistent local Python REPL and an rlm-subcall subagent as the sub-LLM (llm_query).
1