What problem does it solve? Complex data modeling with Pydantic involves subtle pitfalls—lost subclass fields during serialization, misapplied field metadata, broken forward references, and validator ordering issues—that produce silent bugs in APIs and data pipelines. ## Core Features & Use Cases - Field Metadata & Constraints: Correct usage of Field(), Annotated patterns, StringConstraints, and built-in constraints instead of custom validators. - Model Hierarchies: Discriminated unions, generics, and polymorphic serialization to avoid subclass serialization data loss. - Forward References & Aliases: Guidance on recursive type aliases, deferred annotation evaluation, and avoiding stringified annotations. - Use Case: When building a FastAPI endpoint with a polymorphic request body, apply discriminated unions so each subclass validates and serializes with its own fields intact. ## Quick Start Ask the AI to review or write a Pydantic model with constraints, validators, or a subclass hierarchy following these best practices.