What problem does it solve? Developers working in the LobeHub codebase need consistent conventions for creating and migrating modals, dialogs, and confirm flows, especially when moving from legacy antd-style modals to the base-ui imperative modal stack. ## Core Features & Use Cases - Imperative Modal Creation: Guides the use of createModal, confirmModal, and useModalContext from @lobehub/ui/base-ui instead of declarative open-state patterns. - ModalHost Wiring: Explains the requirement to mount the base-ui ModalHost near the app root so imperative modals actually render. - Callback Semantics: Clarifies the difference between onOpenChange and onOpenChangeComplete so caller-side cleanup runs reliably when modals close. - Use Case: When adding a new settings dialog, follow the prescribed file structure (index.tsx exporting createXxxModal plus a content component) and wire i18n via useTranslation in content and t from i18next in modal options. ## Quick Start Ask the assistant to create a new imperative modal for a feature using the base-ui createModal pattern with a separate content component and proper ModalHost setup.