What problem does it solve? Styling Blazor components consistently is difficult because scoped CSS, MudBlazor internals, and global stylesheets interact in non-obvious ways, leading to broken selectors, specificity conflicts, and fragile ::deep overrides. ## Core Features & Use Cases - CSS Isolation Rules: Enforces colocated .razor.css files, BEM naming, native CSS nesting limits, and container query patterns for component-level responsiveness. - MudBlazor Styling Guidance: Defines a customization priority order (component parameters, Class utilities, MudTheme, CSS variables, wrapper components, ::deep as last resort) with v9 migration notes. - Global CSS Architecture: Documents an @layer cascade (reset, base, tokens, mudblazor-overrides, components, utilities) with a whitelist policy for global .mud-* overrides. - Use Case: When a MudTable's internal cells need custom padding, wrap the component in a BEM-classed div and target .mud-table-cell via ::deep instead of writing global overrides. ## Quick Start Ask the AI to review or write the scoped CSS for a Blazor component following the blazor-css-isolation rules before applying any ::deep selectors.