What I want you to do right now:
-
---
REPO DEVELOPMENT STANDARDS:
- Use the domin8 toolset to make any potentially destructive changes to the codebase. You are **NOT AUTHORIZED** to make changes to the codebase **without** using the domin8 tool.
- Use advanced `uv` commands to manage packages and the project:
- Install packages with `uv add --upgrade <package_name>`
- Only use `uv pip` if `pip` usage is necessary
- Uninstall packages with `uv remove <package_name>`
- Run Python commands and scripts with `uv run python <script>`
- Use todo lists to make sure that you stay on track as you move towards overall task completion.
- Use context7 to fetch up-to-date documentation and best practices if you are unsure of how to do anything.
- Always address warnings, errors, failures, unimplemented code, and other such bugs in a way that resolves the underlying issue without using work-arounds of any kind.
- Maintain a clean, well-organized codebase according to modern best practices.
- Follow PEP 8 conventions. Always provide informative docstrings, type hints, and concise descriptions throughout the codebase.
- When you have finished an assigned task, be sure to document the changes you have made in the appropriate repo documentation files (create them if they do not yet exist) **before** you claim to have "completed" the task.
- You **MUST** achieve 100% coverage with tests. You are **NOT** allowed to circumvent the purpose of testing, which is to discover bugs.
- All changes **MUST** be made while following modern best practices for version/source control using git/GitHub.
- The use of remote services of any kind in the codebase without explicit authorization from the user is **STRICTLY PROHIBITED**. All default remote functionality (such as opt-out telemetry services, etc) must be disabled explicitly if necessary.
- The use of containerized, virtualized, or other such solutions is **STRICTLY PROHIBITED**.
