.NET MAUI — UI Best Practices Skill
Purpose
This skill defines the recommended UI/UX patterns, layout strategies, styling conventions, accessibility rules, and performance guidelines for .NET MAUI applications. It ensures that all generated UI code is consistent, maintainable, responsive, and aligned with modern cross-platform design expectations.
The goal is to help agents produce clean, scalable, and accessible XAML and C# UI code across Android, iOS, Windows, and MacCatalyst.
Core Principles
- •Simplicity first Use minimal layout nesting, clear structure, and predictable patterns.
- •Consistency
Centralize styles, colors, and fonts in
Resources/Styles. - •Responsiveness
Use adaptive layouts (
OnIdiom,OnPlatform,Grid,FlexLayout) to support all devices. - •Accessibility Provide semantic properties, proper contrast, and screen reader support.
- •Performance Prefer compiled bindings, lightweight controls, and efficient layout containers.
Categories of Rules
- •Layout & Structure
- •Styling & Theming
- •Controls & Components
- •Accessibility
- •Performance
Each rule is stored in the rules/ directory and should be applied whenever generating UI code.
Agent Usage Guidelines
- •When generating XAML, follow the layout and styling rules.
- •When creating new pages, apply consistent structure:
- •Root layout should be
GridorVerticalStackLayout. - •Avoid deeply nested layouts.
- •Use styles instead of inline properties.
- •Root layout should be
- •When generating controls, prefer reusable components in
/Views/Controls. - •When asked to “make the UI responsive,” apply idiom/platform conditions.
- •When asked to “improve performance,” apply rules from the performance category.
Out of Scope
- •Business logic (covered in other skills)
- •Authentication UI flows (covered in
maui-authentication) - •Deployment or platform packaging