### 1. Encoding Requirements - All source files must **remain in UTF-8 encoding**. Do not modify the existing encoding of the files. - Ensure that all files are saved using UTF-8 encoding and do not use other encodings like ASCII or UTF-16. - If there is a mismatch in encoding when processing text or files, **do not automatically fix the encoding**. Keep the original encoding.
---
## Development Principles
### 2. Error Handling and Fail-Fast Strategy - Use the **Fail-Fast** principle: when an unrecoverable error occurs, immediately fail and stop further execution. Do not continue after encountering critical errors. - **Do not write defensive logic**. If certain conditions are unacceptable, directly throw an exception or return an error instead of performing redundant error checks or recovery actions. - In the design of APIs or libraries, if external inputs are invalid or configuration errors occur, **fail immediately and inform the user**. Do not attempt to "fix" the error by providing default values or recovery mechanisms.
---
## Other Guidelines
### 3. Code Review and Testing - Before submitting any code, ensure that **all unit tests pass**. - It's strongly encouraged that every feature has corresponding test cases, and **automated tests should cover all public interfaces**. - **Do not modify production code directly**; all changes must go through feature branches and Pull Requests for code review and merging.
