From 8a315550b16af4891617c88cfbc04d8273437547 Mon Sep 17 00:00:00 2001 From: Claude Date: Mon, 28 Sep 2026 15:15:36 +0000 Subject: [PATCH] docs(claude): AccountViewModel now lives in commonsUI Co-Authored-By: Claude Opus 5.5 Claude-Session: https://claude.ai/code/session_01S7FuNBSKiyVecARSoE4B9P --- .claude/CLAUDE.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/.claude/CLAUDE.md b/.claude/CLAUDE.md index e43dd865f0..bb25787d7d 100644 --- a/.claude/CLAUDE.md +++ b/.claude/CLAUDE.md @@ -221,9 +221,10 @@ etc. instead of re-implementing them. system integrations (notifications, file pickers, share sheets, camera, media3, WebView, keyring/Keystore), and the platform `actual`s or port implementations the shared UI calls. A new screen goes in `commonsUI` when - its dependencies allow. While `AccountViewModel` is still app-side, one that - needs it may live in `amethyst/`, but keep Android APIs out of it (behind a - port or slot) so it can move later. Don't add screens to today's `desktopApp` + its dependencies allow — `AccountViewModel` itself is in `commonsUI` + (`commons.viewmodels`), reaching Android through `AccountViewModelHost`. A + screen that still needs an app-only helper may live in `amethyst/`, but keep + Android APIs out of it (behind a port or slot) so it can move later. Don't add screens to today's `desktopApp` that the shared UI will have to re-create. When extracting a composable: move it to `commonsUI/commonMain/` (see