code-quality-standardslisted

# Code Quality Standards ## Core Principles - **Readability**: Clear, self-documenting code. Clarity over cleverness. - **Naming**: Descriptive, concise names for variables, functions, classes. - **DRY**: Encapsulate reusable logic. Define once, reference everywhere. - **Comments**: Explain *why*, not *what*. - **Security**: No hardcoded secrets. Least privilege. Validate all input. - **TDD**: Write failing tests before implementation. Red-green-refactor. - **Idempotency**: Operations must be safely repeatable with consistent results. ## Language Rules ### Python - Follow PEP 8. Use type hints for all function signatures. - Write docstrings for all functions/classes/modules. - Use `logging` module, never `print()`. - Pin dependencies for apps (lock file); use ranges for libraries. - Run `black`, `flake8`, `mypy` before committing. ### Bash / Shell - **NEVER use Bash for file operations** — use Read/Edit/Write/Grep/Glob tools. - **NEVER use `for` loops** — breaks permission matching, requires interactive prompts. Use parallel tool calls or tool-native batch operations instead. - **NEVER generate scripts** — execute commands directly via tool calls. - Prefer parallel tool calls for independent commands. ### JavaScript / TypeScript - Use TypeScript for all new JS code. Prefer `const` over `let`, avoid `var`. - Implement proper error boundaries in React components. ## Logging Standards Format: `YYYY-MM-DD HH:mm:ss [LEVEL] {message}` | Level | Use | | --- | --- | | E