Public/Live_RC
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

add

Browse Source
This commit is contained in:
larssand
2026-09-02 22:04:42 +02:00
parent 69a6ed311a
commit 82d52ed6cd
1 changed files with 7 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
AGENTS.md
View File

@@ -24,3 +24,10 @@ Always use these exact Linux commands for management:
- **Commits:** Conventional Commits (e.g., `fix(lap): repair split calculations`, `feat(audio): add linux sound trigger`). - **Commits:** Conventional Commits (e.g., `fix(lap): repair split calculations`, `feat(audio): add linux sound trigger`).
- **File System:** Ensure `chmod +x` commands are suggested if modifying scripts under `scripts/` or `AMMC/`. - **File System:** Ensure `chmod +x` commands are suggested if modifying scripts under `scripts/` or `AMMC/`.
- Always respect frontend `localStorage` to backend SQLite synchronization. - Always respect frontend `localStorage` to backend SQLite synchronization.
## Feature Generation Rules (Kvot-räddare för nya funktioner)
When implementing a NEW feature or module:
1. **Architecture Blueprint First:** Do NOT write the code immediately. Output a 3-bullet-point layout explaining *where* the new logic goes (e.g., frontend state, backend API route, or SQLite schema change). Wait for human confirmation.
2. **Draft Modular Skeleton:** Output only the function definitions, routes, or component names with empty bodies (stubs) first.
3. **Fill Code Incremental:** Implement the feature in small, separate code blocks (max 30 lines at a time). Never generate frontend, backend, and database changes in a single massive response.
4. **Use Existing Utilities:** Always check `server.js` and `src/app.js` for existing helper functions (like DB queries, WebSocket broadcasts, or audio hooks) instead of writing new ones from scratch.