SteamFrame/FrameAssistant
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Start the design document with the high-level architecture

Browse Source 
DESIGN.md: one process with several threads (D16), three layers (D17),
HA-centric object classes (D18), injected configuration (D19). Design
decisions move from REQUIREMENTS.md to DESIGN.md.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
matzman
2026-10-05 20:46:23 +02:00
co-authored by Claude Opus 5.5
parent ed8b2237bd
commit f6c5de4fb9
5 changed files with 86 additions and 16 deletions
Download Patch File Download Diff File Expand all files Collapse all files
CLAUDE.md
+2 -1
View File
@@ -34,7 +34,8 @@ dashboard tab. Status: the overlay platform works; the Home Assistant parts are
**Start every session by reading `docs/PROGRESS.md`** (current state, next steps, log).
User-facing docs: `README.md` (quick start, development, CLI), `docs/REQUIREMENTS.md`
(requirements, open questions, decisions), `docs/PROGRESS.md`, `docs/ARCHITECTURE.md`, `docs/STEAM-FRAME.md`.
(requirements, open questions, decisions), `docs/DESIGN.md` (design of the HA parts and its
decisions), `docs/PROGRESS.md`, `docs/ARCHITECTURE.md`, `docs/STEAM-FRAME.md`.
Keep them in sync with changes. This file holds what a developer needs on top of that.
Platform: a SteamVR **dashboard overlay**, built from the author's vrdashboard template,