.cursorrules

# Cursor Instructions

## Strategy

1. Write plan with success criteria for each phase to be checked off. Include project scaffolding, including .gitignore, and rigorous unit testing where applicable.
2. Execute the plan ensuring all criteria are met
3. Run thorough automated checks appropriate for this repository (for example, unit tests, problem-specific sample tests, and any available integration or end-to-end tests), fixing defects
4. Only complete when the implementation meets the requirements and all relevant tests pass

## Coding standards

1. Use idiomatic approaches and library versions compatible with this repository's documented toolchains and constraints (for example, C++17 for C++ code)
2. Keep it simple - NEVER over-engineer, ALWAYS simplify, NO unnecessary defensive programming. No extra features - focus on simplicity.
3. Be concise. Keep README minimal. IMPORTANT: no emojis ever

## Git and GitHub

- For every task, first create a new Issue, then create the related branch, and finally open the related PR.
- Use best practices for commit messages. Every commit message should follow this regex:
  `^(?:fix|chore|docs|feat|refactor|style|test)(?:\(.+\)): [A-Z].+(?:\s#\d+)?$`
- Always use one of the commit type keywords (`fix`, `chore`, `docs`, `feat`, `refactor`, `style`, `test`) with an explicit scope in the `type(scope): Message` format (for example, `feat(api): Add new endpoint`).