// Makepad UI patterns in MoFA Studio: live_design layout, event handling, apply_over usage, shader-driven theming, and animation lifecycles. Use when editing UI or behavior.
Onboard to the MoFA Studio repository, run the app and dataflows, and choose the right MoFA Studio skill. Use when setting up the workspace, building/running, or deciding which part of the system to edit (app, dataflow, UI, audio, settings, deployment, troubleshooting).
Core architecture of MoFA Studio: plugin system, shell/app boundaries, state coordination, theme and dark mode, and timer/event lifecycles. Use when changing architecture, refactoring, or adding cross-cutting behavior.
Create or modify MoFA Studio apps, screens, and shell integration. Use when adding a new app, changing an existing app, or wiring app lifecycle (timers, dark mode, dataflow).
Dora dataflow authoring and wiring for MoFA Studio dynamic nodes. Use when editing voice-chat.yml, adding dynamic nodes, or debugging dataflow connections and signals.
Audio pipeline details for MoFA Studio: device selection, mic monitoring, AudioPlayer buffer behavior, and participant tracking. Use when modifying audio code or diagnosing audio issues.
Provider settings and user preferences in MoFA Studio. Use when editing provider UI, saving preferences, or wiring API keys and defaults.
Follow Makepad patterns for event handling and runtime updates. Use apply_over for dynamic changes and keep hover handling before action extraction.
live_design! using theme constants.Widget::handle_event and call self.view.handle_event.Event::Actions early return.apply_over for visibility and shader instance updates.Event::NextFrame for animations.