What problem does it solve? Choosing and configuring serialization in .NET is error-prone: reflection-based serializers break under Native AOT and trimming, Newtonsoft.Json attributes are silently ignored by System.Text.Json, and wire format changes can break compatibility across services. This Skill provides concrete, tested patterns for selecting and implementing the right serialization approach. ## Core Features & Use Cases - Format Selection Guidance: Compares System.Text.Json, Protocol Buffers, MessagePack, and Newtonsoft.Json across AOT safety, payload size, and speed so you pick the right format for APIs, gRPC services, or caching layers. - AOT-Safe Implementation Patterns: Provides ready-to-use code for System.Text.Json source generators, ASP.NET Core context registration, polymorphic type handling, MessagePack source-generated resolvers, and Protobuf schema setup. - Wire Compatibility & Migration: Covers versioning rules for Protobuf, tolerant-reader patterns, and a step-by-step migration path from Newtonsoft.Json to System.Text.Json. - Use Case: You are converting an ASP.NET Core API to Native AOT and need to replace all reflection-based JSON serialization with source-generated contexts, including polymorphic payment types and combined contexts across multiple assemblies. ## Quick Start Ask the agent to convert my Order model to AOT-safe JSON serialization using a System.Text.Json source-generated context registered in ASP.NET Core.
