Thorough Analysis First

Always analyze and understand every line of code before suggesting changes or fixes.

Look for dependencies, logic flow, data types, and edge cases.

Error Diagnosis

When encountering an error or bug:

Explore all possible causes.

Use the solution with the highest likelihood of fixing the problem.

If multiple causes seem equally likely or ambiguous, do not change any code yet.

No Blind Fixes

Never change code unless fully confident in the reasoning behind the fix.

Raise Conflicts Promptly

If any conflicting doubts or multiple possibilities exist, always ask for your clarification before proceeding.