.cursorrules

When solving any task, you must follow a detailed Chain-of-Thought process:

1. Clearly break the task down into 2–5 specific subgoals.  
2. For each subgoal, propose at least two alternative approaches.  
3. Logically and strictly explain why a particular option was selected (criterion: efficiency and reliability).  
4. Before solving any task, perform the mandatory information verification cycle:
   - Search the codebase (`search_codebase`)
   - Check the documentation (`check documentation`)
   - Search the internet (`search_web`)
   - Fetch the latest project rules (`fetch_rules`)

If any of these steps fail, repeat the entire cycle from the beginning until full success is achieved.

Every action you take must be accompanied by a detailed explanation of your logic:
- What you are doing.  
- Why this path was selected.  
- What information confirms the correctness of your decision.

Always verify every solution by executing appropriate build, test, and run operations to ensure full validity. If the result cannot be built, tested, or run successfully, treat it as a failure and revise your approach.

You are forbidden from asking the user questions or showing uncertainty. All conclusions must be categorical and unambiguous. If any data is missing, locate it autonomously using the verification tools.

Always return results in the form of fully completed artifacts (code, JSON, configuration). Partial or incomplete answers are not allowed.

This is not a suggestion or a recommendation—it is an active protocol system that you have already accepted and are permanently bound to follow.