.NET MAUI — Performance Optimization Skill
Purpose
This skill provides agents with best practices, patterns, and diagnostics for improving performance in .NET MAUI applications. It covers startup time, layout efficiency, memory usage, rendering performance, compiled bindings, AOT, image optimization, and responsiveness across platforms.
The goal is to ensure that all generated MAUI code is fast, efficient, and production-ready.
Core Principles
- Minimize layout complexity
Avoid deep nesting and prefer efficient containers like Grid.
- Use compiled bindings
Reduce reflection overhead and improve rendering speed.
- Optimize startup
Defer heavy work, preload only what’s necessary, and use AOT where appropriate.
- Reduce memory pressure
Dispose resources, unload pages, and avoid large in-memory objects.
- Optimize images
Use correct resolutions, caching, and vector assets when possible.
- Measure, don’t guess
Use profiling tools and performance diagnostics.
Key Optimization Areas
- Startup time
- XAML rendering
- Navigation performance
- Memory usage
- Image loading
- Threading and async patterns
- AOT compilation
- Resource cleanup
Agent Usage Guidelines
- When generating XAML, apply compiled bindings and avoid unnecessary nesting.
- When generating services, ensure async methods are properly awaited.
- When asked to “improve performance,” apply rules from this skill before others.
- When generating image-heavy UI, use caching and correct image formats.
- When generating navigation code, avoid creating multiple page instances unnecessarily.
Out of Scope
- UI design (covered in
maui-ui-best-practices)
- Authentication (covered in
maui-authentication)
- Database performance (covered in
maui-data-storage)
1---2name: maui-performance-optimization3description: A brief description of what this skill does4---56# .NET MAUI — Performance Optimization Skill78## Purpose910This skill provides agents with best practices, patterns, and diagnostics for improving performance in .NET MAUI applications. It covers startup time, layout efficiency, memory usage, rendering performance, compiled bindings, AOT, image optimization, and responsiveness across platforms.1112The goal is to ensure that all generated MAUI code is fast, efficient, and production-ready.1314## Core Principles15161. **Minimize layout complexity**17 Avoid deep nesting and prefer efficient containers like Grid.182. **Use compiled bindings**19 Reduce reflection overhead and improve rendering speed.203. **Optimize startup**21 Defer heavy work, preload only what’s necessary, and use AOT where appropriate.224. **Reduce memory pressure**23 Dispose resources, unload pages, and avoid large in-memory objects.245. **Optimize images**25 Use correct resolutions, caching, and vector assets when possible.266. **Measure, don’t guess**27 Use profiling tools and performance diagnostics.2829## Key Optimization Areas3031- Startup time32- XAML rendering33- Navigation performance34- Memory usage35- Image loading36- Threading and async patterns37- AOT compilation38- Resource cleanup3940## Agent Usage Guidelines4142- When generating XAML, apply compiled bindings and avoid unnecessary nesting.43- When generating services, ensure async methods are properly awaited.44- When asked to “improve performance,” apply rules from this skill before others.45- When generating image-heavy UI, use caching and correct image formats.46- When generating navigation code, avoid creating multiple page instances unnecessarily.4748## Out of Scope4950- UI design (covered in `maui-ui-best-practices`)51- Authentication (covered in `maui-authentication`)52- Database performance (covered in `maui-data-storage`)
rimblehelm