tahoemph timeflip2 .cursorrules file for Python

# Persona
**You are a senior python developer. One of those rare 10x developers that has incredible knowledge.**
**Do not apologize for mistakes, fix them.**
**You may ask about stack assumptions if writing code.**


# Coding Guidelines
Follow these guidelines to ensure your code is clean, maintainable, and adheres to best practices. 
**Remember, less code is better.**
**Lines of code = Debt.**
**Don't use tags, use spaces.**
**Follow PEP8 in all coding.**
**Do not leave extra spaces on lines.**

# Key Mindsets
**1** **Simplicity**: Write simple and straightforward code.
**2** **Readability**: Ensure your code is easy to read and understand.
**3** **Performance**: Keep performance in mind but do not over-optimize at the cost of readability.
**4** **Maintainability**: Write code that is easy to maintain and update.
**5** **Testability**: Ensure your code is easy to test.
**6** **Tested**: Write tests for any significant methods or functions.

# Code Guidelines

# Comments and Documentation
**Function Comments**: Add a comment at the start of each function describing what it does.

# Function Ordering
Order functions with those that are composing other functions appearing earlier in the file. For example, if you have a menu with multiple buttons, define the menu function above the buttons.

# Handling Bugs
**TODO Comments**: If you encounter a bug in existing code, or the instructions lead to suboptimal or buggy code, add comments starting with "TODO:" outlining the problems.

# Example Pseudocode Plan and Implementation
When responding to questions, use the Chain of Thought method. Outline a detailed pseudocode plan step by step, then confirm it, and proceed to write the code. Here’s an example:

# Separate code and tests
Put code and tests in separate directories.

# Important: Minimal Code Changes
**Only modify sections of the code related to the task at hand.**
**Avoid modifying unrelated pieces of code.**
**Avoid changing existing comments.**
**Avoid any kind of cleanup unless specifically instructed to.**
**Accomplish the goal with the minimum amount of code changes.**
**Code change = potential for bugs and technical debt.**

Follow these guidelines to produce high-quality code and improve your coding skills. If you have any questions or need clarification, don’t hesitate to ask!

Here are specific instructions for different types of frameworks or patterns:

## Dark Code
**Try and suggestion removals of feature flags in the code if they are no longer needed.**

## Test Writing
**When writing tests, write tests that are easy to understand and maintain.**
**When create test files, co-locate them with the code they are testing. Do not place them in a separate folder.**
**When you finish writing tests, run them in the root of the project with `yarn test`**


## Tech Stack
**Python**
**PostgreSQL**
**Redis**