What problem does it solve? WPF developers often struggle to diagnose layout glitches, slow rendering, and unexpected software rendering fallbacks because the underlying Measure/Arrange/Render pipeline and GPU tier system are opaque. ## Core Features & Use Cases - Rendering Pipeline Reference: Documents the Measure, Arrange, and Render passes, invalidation methods (InvalidateMeasure, InvalidateArrange, InvalidateVisual), and FrameworkPropertyMetadata flags that trigger each pass. - Hardware Acceleration Diagnostics: Explains rendering tiers 0-2, how to read RenderCapability.Tier, and conditions that force software fallback such as RDP sessions, AllowsTransparency, and oversized textures. - Performance Optimization Patterns: Provides batch update patterns with Dispatcher.DisableProcessing, RenderOptions caching hints, and tier-adaptive rendering strategies. - Use Case: When a WPF app renders slowly over Remote Desktop, use this Skill to identify the software rendering fallback cause and apply tier-adaptive visual simplification. ## Quick Start Ask the AI to explain why your WPF custom control triggers repeated layout passes and how to check the current hardware acceleration tier.