code-conventions

Eliminate magic numbers by importing and referencing constants from your project's modules instead of hardcoding numeric values. This approach centralizes value definitions, improves maintainability, and makes code intent explicit across implementation and testing phases.

Separating physical and screen coordinates prevents coordinate-system confusion and bugs in rendering and collision detection. Always distinguish between domain coordinates and display coordinates to maintain consistency across your codebase and avoid performance issues from misaligned transformations.

Moving setup operations outside loops eliminates redundant computation on each iteration, reducing CPU cycles and improving runtime performance. This convention ensures expensive operations—constant initialization, complex calculations—execute once rather than repeatedly during loop execution.

Enforce project-wide coding conventions during implementation and code reviews by requiring constant references, eliminating magic numbers, separating coordinates, and following performance best practices. Apply these standards uniformly so all contributors maintain the same codebase style and quality.

Yes, code-conventions standards apply during implementation, testing, and code reviews for both new features and legacy code. Incrementally refactor existing code to import BOARD_PHYSICAL constants and eliminate magic numbers as you modify or review sections.