What problem does it solve? Choosing and correctly implementing one of DevExpress's six WPF layout controls is error-prone: similar names (DockLayoutManager vs DockLayoutControl), two different LayoutGroup classes in different namespaces, and differing persistence APIs cause broken layouts and failed save/restore. This Skill guides control selection, XAML construction, and layout persistence. ## Core Features & Use Cases - Control picker: Decision guidance across DockLayoutManager (Visual Studio-style docking/MDI), LayoutControl, DataLayoutControl, TileLayoutControl, FlowLayoutControl, and DockLayoutControl. - Building rules: XAML patterns for LayoutGroup nesting, LayoutItem labels, DataAnnotations-driven form generation, tile sizes and groups, flow breaks, and edge docking. - Layout persistence: Save/restore via SaveLayoutToXml for DockLayoutManager and WriteToXML/ReadFromXML for the LayoutControl family, including RestoreLayoutOptions and BindableName for MVVM. - Use Case: Build a settings form by decorating a POCO with [Display(GroupName = "{Tabs}/Contact")] attributes and binding it to a DataLayoutControl, then persist user customizations on window close. ## Quick Start Ask the assistant to create a WPF data-entry form using DevExpress LayoutControl with labeled text editors grouped in a GroupBox.