What problem does it solve? Adding tabs to a WARP FluentTabControl is not derivable from its small API alone: the control delegates layout, sizing, and scrolling to its content, so developers easily break Designer compatibility, oversize host forms beyond the screen, or lose scrolling for clipped tab pages. ## Core Features & Use Cases - Mandatory one-UserControl-per-tab pattern: Encapsulate every tab page as its own UserControl so the WinForms Designer, DI, and per-tab ViewModels keep working. - Host size derivation with caps: Compute the form's natural client size from the largest tab UserControl, then clamp to 75% of the screen working area or 90% of the parent client area. - Scrolling strategies for clipped tabs: Enable UserControl.AutoScroll with AutoScrollMinSize, or add an explicit inner scrolling panel when part of the tab must stay pinned. - Use Case: When adding a Settings tab to a MainForm hosting a FluentTabControl, create a SettingsView UserControl with a Designer-set Size, call AddTab from OnLoad (never InitializeComponent), and let the host derive and cap its ClientSize automatically. ## Quick Start Ask the AI to add a new tab to a form hosting a WARP FluentTabControl following the one-UserControl-per-tab pattern with proper host size capping.
