These instructions have been created to help Cursor but are expected to be generally helpful.
Follow .github/instructions/cpp.instructions.md
Follow .github/instructions/cpp.instructions.md
Prefer American spelling in file, function, and variable names for new code and for anything not tied to an existing API.
Exceptions:
- Match existing external or legacy APIs (for example, public C API names and types that already use a different style, such as
AnalysePlay*). - Do not rename unrelated legacy identifiers in the same change unless the task requires it.
For every code change, follow strict TDD:
- Write or update automated tests that initially fail and describe the desired behavior and edge cases.
- Write the minimal production code needed to make the new tests pass. Do not add untested functionality.
- After tests are green, refactor tests and implementation for clarity and to remove duplication.
- Run the relevant tests after each refactor and keep them green.
- Repeat this red-green-refactor cycle in small steps.
Structure tests with Arrange-Act-Assert and use descriptive names that capture intent, including negative and boundary cases.
Never write production code first and wrap tests around it afterward. Tests must be written first and must fail before implementation.
Tests are not necessary for changes to documentation, unless the change is coupled to a code or configuration change.