AI rules update

Author: 0xmichalis

.clinerules

@@ -6,12 +6,9 @@
 
 ## Code Changes
 
-- Ensure the code you have provided is complete
+- Ensure the code you have provided is complete (compiles and tests pass)
 - Ensure the project is formatted (cargo fmt --all)
 - Ensure that any clippy warnings are addressed (cargo clippy -- -D warnings)
-- When writing an if/else clause, prefer putting the clause with most of the code in the else part to keep the whole conditional more readable
-- Avoid arrowized code when possible
-- Avoid renaming variables unless explicitly asked to do so
 
 ## Security Practices
 
@@ -21,6 +18,10 @@
 
 ## Misc
 
+- Avoid making any formatting changes when not explicitly asked to do so
+- Avoid renaming variables unless explicitly asked to do so
+- When writing an if/else clause, prefer putting the clause with most of the code in the else part to keep the whole conditional more readable
+- Avoid arrowized code whenever possible
 - When providing a solution, give me a score on a scale of 1-10 about how confident you are in the solution
 
 ## Project-Specific Patterns