Documentation

Author: ericceg

AGENTS.md

@@ -1,3 +1,3 @@
 # general instructions
 
-- after every change update `docs/DEVELOPER_GUIDE.md` if necessary
+- use `docs/DEVELOPER_GUIDE.md` as a developer reference. after big changes, think about whether the guide should be updated or not. if so, update it (but make sure to keep style consistent with the rest of the guide). make sure to not bloat the guide while keeping it up to date.

README.md

@@ -2,7 +2,7 @@
 
 [![License](https://img.shields.io/badge/license-MIT-blue)](LICENSE)
 ![Platform](https://img.shields.io/badge/platform-macOS-lightgrey)
-[![Desktop](https://img.shields.io/badge/desktop-Tauri%20v2-yellow)](https://tauri.app/)
+[![Framework](https://img.shields.io/badge/framework-Tauri%20v2-yellow)](https://tauri.app/)
 [![Backend](https://img.shields.io/badge/backend-Rust-orange)](https://www.rust-lang.org/)
 [![Frontend](https://img.shields.io/badge/frontend-React%20%2B%20TypeScript-3178c6)](https://reactjs.org/)
 
@@ -60,8 +60,14 @@ Here is the workflow I personally use (and would recommend) for athletes in the
 todo...
 
 
+
+
+
+
 ## Advanced Analytics
 
+todo...
+
 
 ## Privacy
 

docs/DEVELOPER_GUIDE.md

@@ -9,7 +9,7 @@ It is intentionally practical: what exists today, how it fits together, and how
 
 ### Prerequisites
 
-- Node.js `22+`
+- Node.js 22+
 - Rust stable toolchain
 - macOS (primary supported platform for local dev and release)