cursor rules

Instructions:
Objective: Apply Chain of Thought (CoT) reasoning to decompose the programming task.

Steps:

Break down the task into logical, manageable components.

Clearly articulate each step in the coding process, whether it's designing an algorithm, structuring code, or implementing specific functions.

Outline the dependencies between components, ensuring that the overall system design is coherent and modular.

Verify the correctness of each step before proceeding to ensure that your code is logically sound and modular.

Variable: RationalizeDecisions
Instructions:
Objective: Use Step-by-Step Rationalization (STaR) to justify every coding decision.

Steps:

Provide clear, logical justifications for every decision made during the coding process.

Consider and document alternative design choices.

Explain why the chosen approach is preferred, based on criteria such as performance, scalability, and maintainability.

Ensure that each line of code has a clear purpose and is well-commented for maintainability.

Variable: OptimizeEfficiency
Instructions:
Objective: Incorporate A* Search principles to evaluate and optimize code efficiency and reliability.

Steps:

Select the most direct and cost-effective algorithms and data structures.

Consider time complexity, space complexity, and resource management.

Develop and run test cases, including edge cases, to ensure code efficiency and reliability.

Profile the code to identify and optimize any performance bottlenecks.

Variable: EvaluateSolutions
Instructions:
Objective: Leverage Tree of Thoughts (ToT) to explore and evaluate different coding solutions.

Steps:

Explore different coding approaches and solutions in parallel.

Evaluate each potential solution using A* Search principles.

Prioritize those that offer the best balance between performance, readability, and maintainability.

Document why less favorable solutions were rejected, providing transparency for future code reviews.

Variable: SimulateLearning
Instructions:
Objective: Simulate adaptive learning in coding by applying Q-Learning principles.

Steps:

Reflect on coding decisions throughout the session as if you were learning from each outcome.

Prioritize coding strategies that lead to robust and optimized code.

At the conclusion of each coding task, summarize key takeaways and areas for improvement to guide future development.

Variable: ContinuousMonitoring
Instructions:
Objective: Engage in Process Monitoring to continuously refine the coding process.

Steps:

Periodically assess the progress of your coding task.

Review the codebase for technical debt and refactoring opportunities.

Ensure that each segment of the code aligns with the overall project goals and requirements.

Use real-time feedback to refine your coding approach, making necessary adjustments to maintain code quality throughout the development process.

Variable: IncorporateSecurity
Instructions:
Objective: Incorporate security best practices into the coding process.

Steps:

Apply input validation, encryption, and secure coding techniques.

Safeguard the code against vulnerabilities.

Ensure robustness against common security threats.

Variable: EnhanceReadability
Instructions:
Objective: Prioritize code readability and maintainability.

Steps:

Use clear variable names, consistent formatting, and logical organization.

Ensure that the code is easy to understand and maintain, facilitating future development and collaboration.

Variable: ConsiderCollaboration
Instructions:
Objective: Consider how the code will be used and understood by other developers.

Steps:

Write comprehensive documentation.

Follow team coding standards to facilitate collaboration.

Ensure that the codebase remains accessible and maintainable for all contributors.

Final Instruction:
Objective: Integrate all advanced reasoning techniques into your coding workflow.

Goal: Deliver the most logical, secure, efficient, and well-documented code possible by fully adhering to these structured instructions.

IMPORTANT: Do not lower versions in pubspec.yml you can bump versions but never lower them