Writes and reviews SwiftData code against modern API rules and best practices.
npx skills add https://github.com/AlexW00/Zettel --skill swiftdata-pro-alexw00
Please help me install this Agent Skill. Skill: swiftdata-pro Source: https://github.com/AlexW00/Zettel/tree/main/.agents/skills/swiftdata-pro Command: npx skills add https://github.com/AlexW00/Zettel --skill swiftdata-pro-alexw00
isEmpty == false, regular expressions, and unsupported methods like hasPrefix(). - Platform-Specific Guidance: Applies CloudKit constraints, iOS 18+ indexing, and iOS 26+ class inheritance rules only when relevant to the project's deployment targets. - Use Case: Ask for a review of your SwiftData models before shipping, and receive a prioritized report flagging data-loss risks, runtime crashes, and incorrect @Query usage with concrete fixes. ## Quick Start Use swiftdata-pro to review the SwiftData models and queries in my project and report any issues.High-intent search queries and answers about installing and using this skill.
Run a SwiftData review that checks core rules covering autosaving, relationship delete rules, property restrictions, and FetchDescriptor optimization. Findings are organized by file with the violated rule and a before/after code fix, ending in a prioritized summary.
Some predicates compile cleanly but fail at runtime, such as using `isEmpty == false` instead of `!isEmpty`, regular expressions, computed properties, or `@Transient` properties. Predicates must rely only on data actually stored in the model.
No, `@Query` is designed to work only inside SwiftUI views and will not operate correctly elsewhere. In other classes, use a `ModelContext` with `FetchDescriptor` to fetch data manually.
No, `@Attribute(.unique)` and `#Unique` are not supported in CloudKit and cause local data to fail too. All properties must have default values or be optional, and all relationships must be optional.
Yes, starting with iOS 26 and coordinated releases, SwiftData supports model subclassing. Child classes must be marked `@available` for the 26 release, both parent and child need `@Model`, and all classes must be listed in the schema.
jperezdelrealReview SwiftData code for correctness and modern API usage.
piyushmal13Generate dbt unit test YAML definitions with given inputs and expected outputs.
OMIXECWrites and reviews SwiftData code against modern API rules and best practices.
Roy-wonjiReview SwiftData models and queries for predicate safety and platform compliance.