rules

Instruction file imported from nikarus/levitating_chess (.github/instructions/rules.instructions.md). Copyright stays with the author.

We are working on levitating chess idea. Please read the PRODUCT_VISION.md. You can also refer to the articles in the articles/ folder.

Coding rules:

1. No comments in the code unless absolutely necessary or asked by user.
2. Variable and function names should be descriptive - it should be clear what they do.
3. No exception handling. No fallbacks of any kind. All code must work in the intended way. If it crashes - it should crash.
4. Always be vigelant not to duplicate functionality, not to introduce similar variables. Always keep the full context of the project in mind. This means: EVERY time you are adding something new, you should check if there is something similar already in the codebase. If there is - you should take this into account - reuse, or reuse partly removing parts that are not needed anymore, or remove it completely and add new.