mapping-graphql-models

What problem does it solve?

This Skill prevents data-layer drift by ensuring GraphQL schema, fragments, operations, Kotlin Serializable models, and remote/source wiring stay perfectly aligned.

Core Features & Use Cases

• Schema-to-fragment mapping discipline: Decide AniList vs edge schema ownership before changing models.
• Variant-correct model shaping: Map fragment fields to the intended Kotlin model variant (e.g., Core vs Extended) instead of spreading nullable fields across everything.
• Wiring correctness checks: Verify @GraphQuery operation names, container generics, and source orchestration match the payload contract.
• Atomic variable contract enforcement: Ensure GraphQL operation variables, IGraphPayload.toMap() keys, and domain params are updated together to avoid silent runtime mismatches.
• High-risk drift prevention: Catch common failure patterns such as model-first changes, mismatched variable names, and edge/AniList conflation.

Quick Start

Ask the skill to review your intended GraphQL field change and produce a mapping plan covering schema ownership, fragment/operation selection, Kotlin variant mapping, and remote/source wiring.