swiftdata-pro
Skill7 starsChanged 19 days agoMITView on GitHub
Use when reading, writing, or reviewing projects that use SwiftData. Writes, reviews, and improves SwiftData code using modern APIs and best practices.
5 other projects use a version of this, 4 of them edited.
Adopted by
Most recently taken up by
- kelvinkosbab/KozBonedited, first seen Nov 6, 2026
- VelimirMueller/claude-skillsword for word, first seen Nov 1, 2026
- Provenance-Emu/Provenanceedited, first seen Oct 8, 2026
- 199-biotechnologies/swiftui-claude-skillsedited, first seen Mar 19, 2026
- twostraws/SwiftData-Agent-Skilledited, first seen Mar 11, 2026
Other versions5 projects use a version of this.
Word for word · 1
- VelimirMueller/claude-skills★ 7100% same
Edited · 4
- Provenance-Emu/Provenance★ 6.4k98% same
- twostraws/SwiftData-Agent-Skill★ 45298% same
- 199-biotechnologies/swiftui-claude-skills★ 798% same
- kelvinkosbab/KozBon★ 598% same
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository156 other files it gives its agents.
- skills/swift/swiftui-design-principles/AGENTS.mdAGENTS.md
- skills/swift/ios-code-audit/CLAUDE.mdCLAUDE.md
- skills/swift/swift-focusengine-pro/llms.txtllms.txt
- build-llm-seamSkill
- build-mcp-serverSkill
- build-rag-pipelineSkill
- secure-llm-featuresSkill
- set-up-llm-evalsSkill
- build-nextjs-backendSkill
- build-supabase-edge-functionSkill
- configure-backend-testsSkill
- design-http-apiSkill
- harden-backendSkill
- scaffold-fastapi-serviceSkill
- scaffold-go-serviceSkill
- scaffold-hono-serviceSkill
- secure-supabase-rlsSkill
- set-up-backend-authSkill
- set-up-background-jobsSkill
- set-up-databaseSkill
- set-up-nextjs-supabase-authSkill
- set-up-observabilitySkill
- set-up-supabaseSkill
- build-cliSkill
- release-cliSkill
- set-up-dev-toolchainSkill
- audit-securitySkill
- audit-toolchainSkill
- extend-skillsetSkill
- promote-releaseSkill
- set-up-stack-profileSkill
- write-commit-messagesSkill
- write-pull-requestsSkill
- analyze-complexitySkill
- apply-algorithmsSkill
- apply-design-patternsSkill
- apply-design-principlesSkill
- apply-solidSkill
- choose-data-structureSkill
- debug-systematicallySkill
- enforce-dependency-ruleSkill
- refactor-safelySkill
- slice-and-estimateSkill
- write-clean-testsSkill
- write-readable-codeSkill
- clean-frontend-scaffoldingSkill
- configure-accessibilitySkill
- configure-analyticsSkill
- configure-ciSkill
- configure-error-trackingSkill
- configure-lintingSkill
- configure-test-stackSkill
- configure-typescriptSkill
- create-moduleSkill
- optimize-performanceSkill
- scaffold-frontend-projectSkill
- set-up-authSkill
- set-up-design-systemSkill
- set-up-document-headSkill
- set-up-error-boundariesSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
11 rules. 6 are common, 0 are distinctive, and 5 are very specific to this project.
6
Common
Most of the 4 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Common: line 10
Write and review SwiftData code for correctness, modern API usage, and adherence to project conventions.
- Very specific: line 14
Check for core SwiftData issues using references/core-rules.md.
- Very specific: line 15
Check that predicates are safe and supported using references/predicates.md.
- Very specific: line 16
If the project uses CloudKit, check for CloudKit-specific constraints using references/cloudkit.md.
- Very specific: line 17
If the project targets iOS 18+, check for indexing opportunities using references/indexing.md.
- Very specific: line 18
If the project targets iOS 26+, check for class inheritance patterns using references/class-inheritance.md.
- Common: line 20
If doing partial work, load only the relevant reference files.
- Common: line 27
Do not introduce third-party frameworks without asking first.
- Common: line 28
Use a consistent project structure, with folder layout determined by app features.
- Common: line 33
If the user asks for a review, organize findings by file.
- Common: line 41
If the user asks you to write or improve code, follow the same rules above but make the changes directly instead of returning a findings …
“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Write and review SwiftData code for correctness, modern API usage, and adherence to project conventions. Report only genuine problems - do not nitpick or invent issues.
Review process:
- Check for core SwiftData issues using
references/core-rules.md. - Check that predicates are safe and supported using
references/predicates.md. - If the project uses CloudKit, check for CloudKit-specific constraints using
references/cloudkit.md. - If the project targets iOS 18+, check for indexing opportunities using
references/indexing.md. - If the project targets iOS 26+, check for class inheritance patterns using
references/class-inheritance.md.
If doing partial work, load only the relevant reference files.
Core Instructions
- Target Swift 6.2 or later, using modern Swift concurrency.
- The user strongly prefers to use SwiftData across the board. Do not suggest Core Data functionality unless it is a feature that cannot be solved with SwiftData.
- Do not introduce third-party frameworks without asking first.
- Use a consistent project structure, with folder layout determined by app features.
Output Format
If the user asks for a review, organize findings by file. For each issue:
- State the file and relevant line(s).
- Name the rule being violated.
- Show a brief before/after code fix.
Skip files with no issues. End with a prioritized summary of the most impactful changes to make first.
If the user asks you to write or improve code, follow the same rules above but make the changes directly instead of returning a findings report.
Example output:
Destination.swift
Line 8: Add an explicit delete rule for relationships.
// Before
var sights: [Sight]
// After
@Relationship(deleteRule: .cascade, inverse: \Sight.destination) var sights: [Sight]Line 22: Do not use isEmpty == false in predicates – it crashes at runtime. Use ! instead.
// Before
#Predicate<Destination> { $0.sights.isEmpty == false }
// After
#Predicate<Destination> { !$0.sights.isEmpty }DestinationListView.swift
Line 5: @Query must only be used inside SwiftUI views.
// Before
class DestinationStore {
@Query var destinations: [Destination]
}
// After
class DestinationStore {
var modelContext: ModelContext
func fetchDestinations() throws -> [Destination] {
try modelContext.fetch(FetchDescriptor<Destination>())
}
}Summary
- Data loss (high): Missing delete rule on line 8 of Destination.swift means sights will be orphaned when a destination is deleted.
- Crash (high):
isEmpty == falseon line 22 will crash at runtime – use!isEmptyinstead. - Incorrect behavior (high):
@Queryon line 5 of DestinationListView.swift only works inside SwiftUI views.
End of example.
References
references/core-rules.md- autosaving, relationships, delete rules, property restrictions, and FetchDescriptor optimization.references/predicates.md- supported predicate operations, dangerous patterns that crash at runtime, and unsupported methods.references/cloudkit.md- CloudKit-specific constraints including uniqueness, optionality, and eventual consistency.references/indexing.md- database indexing for iOS 18+, including single and compound property indexes.references/class-inheritance.md- model subclassing for iOS 26+, including @available requirements, schema setup, and predicate filtering.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

