What problem does it solve? CloudKit Production schemas are additive-only, so deleting or renaming fields incorrectly can permanently break a live app. This Skill enforces the correct workflow for evolving the schema safely: editing the canonical schema.ckdb manifest, regenerating wire structs, updating Swift adapters, and respecting the Production baseline. ## Core Features & Use Cases - Field lifecycle management: Add fields with correct index policies, deprecate fields via // DEPRECATED markers instead of deletion, and handle renames as deprecate-plus-add with read-time migration. - Record type creation: Declare new record types in schema.ckdb, generate wire structs, write CloudKitRecordConvertible adapters, and register them in RecordTypeRegistry. - Error diagnosis: Maps common failures (missing wire-struct members, check-schema-additive violations, cktool import errors) to their root causes and fixes. - Use Case: When a Swift compile error like "value of type 'AccountRecordCloudKitFields' has no member 'foo'" appears, use this Skill to determine whether the field must be added to schema.ckdb or removed from the adapter, then regenerate with just generate. ## Quick Start Ask the AI to add a new field to a CloudKit record type and update the schema, adapter, and round-trip test accordingly.
