gurix/wecker
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Emphasize strict adherence to development guidelines (TDD, DRY, MVP)

Browse Source
This commit is contained in:
Markus Graf
2026-05-19 14:48:58 +02:00
parent 62c98f0a87
commit 29aff04e33
1 changed files with 7 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
AGENTS.md
+7 -3
View File
@@ -7,11 +7,15 @@ Please take this into account for all code changes, dependencies (e.g., ARM arch
When configuring audio or running tasks on this device, **always use the 3.5mm headphone jack (Audio Jack)** as the explicit audio output unless requested otherwise. The system might have HDMI devices as lower-index cards, which can cause headless/cron background scripts to fail with ALSA errors. Ensure tools and scripts explicitly target the correct audio card (usually `hw:2,0` or via a user-wide `~/.asoundrc` config). When configuring audio or running tasks on this device, **always use the 3.5mm headphone jack (Audio Jack)** as the explicit audio output unless requested otherwise. The system might have HDMI devices as lower-index cards, which can cause headless/cron background scripts to fail with ALSA errors. Ensure tools and scripts explicitly target the correct audio card (usually `hw:2,0` or via a user-wide `~/.asoundrc` config).
## Development Guidelines ## Development Guidelines
- Follow the principles of TDD (Test-Driven Development), DRY (Don't Repeat Yourself), and MVP (Minimum Viable Product). **STRICT ADHERENCE to the following guidelines is mandatory for every task. Failure to follow these principles undermines the integrity of the project.**
- **TDD (Test-Driven Development):** Always write tests *before* implementing the actual logic. Follow the Red-Green-Refactor cycle.
- **DRY (Don't Repeat Yourself):** Minimize redundancy in code and logic.
- **MVP (Minimum Viable Product):** Implement only what is necessary to meet the requirement.
- Use `uv` to manage dependencies for Python. - Use `uv` to manage dependencies for Python.
- Use `uv ruff` to lint the code. - Use `uv ruff` to lint the code.
- Never commit untested code. - **Never commit untested code.**
- Only commit when ruff is green. - **Only commit when ruff is green.**
## Pre-commit Rules ## Pre-commit Rules
- Always lint the code (`uv ruff`). - Always lint the code (`uv ruff`).