What problem does it solve? Adding DevExpress reporting to Blazor apps involves choosing among five components across three API families, matching them to the correct hosting model, registering the right services and controllers, and avoiding silent runtime failures from mixed C#/JavaScript APIs or wrong project placement. ## Core Features & Use Cases - Guided component selection: Decision gates map hosting mode (Static, Interactive Server, WebAssembly Standalone, Client+Server, Auto) and user needs to the correct component (DxReportViewer, DxDocumentViewer, DxReportDesigner, DxWasmDocumentViewer, DxWasmReportDesigner). - Scenario-specific setup references: Hosting-mode-specific getting-started guides, customization references for native and JS-based components, and report name resolution via IReportProvider or ReportStorageWebExtension. - Anti-pattern validation: A 24-item checklist catches render mode mistakes, service registration conflicts, missing designer controllers, and untrusted custom data source types before code generation. - Use Case: A developer asks to add a report designer to an Interactive WebAssembly Blazor app; the skill detects the configuration, routes to the correct reference, places the page in the client project, registers services on the server, and adds all three required controllers. ## Quick Start Add a DevExpress report viewer to my Blazor Server app and wire it to an existing report class.