Launch & entry points
- Animated agent only: keep avatar behavior, moods, and UI polish here. Games and quests live in their own hub.
- Cross-app consistency: align visuals with the shared UNI menu and dimmi color system (`shared-styles.css`).
Core files for the avatar
Avatar
dimmi.htmlMain animated assistant with moods, mic/cam inputs, and HUD controls.
Shared JS
shared.jsGlobal sounds, quest helpers, and UI hooks reused by avatar overlays.
Styles
shared-styles.cssDimmi color tokens (yes/no/reward/neutral) and component skinning.
Resources
resources/Deck schema references, manifests, and supporting JSON/ARK assets.
Integration guidelines
- Keep the animated agent lightweight: avoid loading quest/game modules directly on
dimmi.html. - Use the experiences hub for anything that runs a game loop, camera test, or trainer flow.
- When adding new avatar behaviors, reuse the
dimmi_*localStorage keys documented inshared.js. - Match the UNI menu theme so DIMMI feels like the sibling of GIZMO and other assistants.