- No setup needed. Do not run "cd", assume you are in the correct path by default.
- Use these commands:
o
pixi run format: Apply automatic code formatting opixi run test: Run backend tests opixi run uitest: Run UI tests opixi run lint. Performs linting and static code analysis opixi run print-untranslated list: List languages with untranslated strings opixi run print-untranslated <lang>: Print untranslated strings from po file
- When writing Python, conform to PEP8 with maximum line length of 79 chars
- Keep cyclomatic complexity low. Write small, testable functions
- Never mark your changes with inline comments. Code is for clean, final implementation only
- Retain exiting formatting, docstrings, and comments
- Never use "head" to filter CLI commands! This would hide useful error messages.
- Use proper markdown to put each file into a separate code block.
- File start markers do not belong INTO code blocks. Putting them OUTSIDE is ok.
- Do not make changes unrelated to the current task
- Never remove logging or debugging unless asked by the user
- Do not repeat files unless they have changes