What problem does it solve? Spring Boot REST APIs often need to serve multiple API versions or different response projections of the same entity without duplicating controllers or cluttering services with mapping logic. This Skill wires a version-aware response mapping layer so new versions are added by creating one strategy class, with no changes to existing handler or registry code. ## Core Features & Use Cases - Version Resolution: Resolves the target API version from the Accept header, URI segment, or query parameter via a MapperContextResolver. - Strategy-Based Mapping: Each version or projection is a @Component MapperStrategy that maps an entity to its version-specific DTO, registered automatically through a MapperRegistry. - Safe Fallbacks: Unknown or missing versions fall back to the latest schema instead of failing hard. - Use Case: A User API must keep serving a legacy v1 schema to old mobile clients while v3 adds a structured contact block. Add V3UserMapperStrategy, update ApiVersion.latest(), and existing clients keep working unchanged. ## Quick Start Apply the response-mapper skill to add version-aware DTO mapping to my Spring Boot UserController using the Accept header.