agentleFS
Prisma-Labs-DevPrisma-Labs-Dev/apple-skills/skills/guide-swiftdata/SKILL.md

guide-swiftdata

Skill336 starsChanged 7 months agoMITView on GitHub

SwiftData patterns — autosave, relationships, dangerous predicates, CloudKit constraints, indexing, class inheritance. Use when writing, reviewing, or debugging SwiftData code.

The file

We split this skill into the rules it gives an agent

9 rules. About 0 are common, 4 are distinctive, and 5 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    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
  1. Distinctive:

    Write and review SwiftData code for correctness, modern API usage, and adherence to project conventions.

    line 14
  2. Distinctive:

    Prefer SwiftData across the board.

    line 19
  3. Distinctive:

    Do not introduce third-party frameworks without asking first.

    line 20
  4. Very specific:

    Check for core SwiftData issues using references/core-rules.md.

    line 24
  5. Very specific:

    Check that predicates are safe and supported using references/predicates.md.

    line 25
  6. Very specific:

    If the project uses CloudKit, check for CloudKit-specific constraints using references/cloudkit.md.

    line 26
  7. Very specific:

    If the project targets iOS 18+, check for indexing opportunities using references/indexing.md.

    line 27
  8. Very specific:

    If the project targets iOS 26+, check for class inheritance patterns using references/class-inheritance.md.

    line 28
  9. Distinctive:

    If doing partial work, load only the relevant reference files.

    line 30

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Guide Skill — This is an expert workflow/pattern guide, not API reference documentation. Originally from twostraws/SwiftData-Agent-Skill by Paul Hudson. MIT License.

SwiftData Patterns

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.

Core Instructions

  • Target Swift 6.2 or later, using modern Swift concurrency.
  • Prefer SwiftData across the board. Do not suggest Core Data unless the feature cannot be solved with SwiftData.
  • Do not introduce third-party frameworks without asking first.

Review Process

  1. Check for core SwiftData issues using references/core-rules.md.
  2. Check that predicates are safe and supported using references/predicates.md.
  3. If the project uses CloudKit, check for CloudKit-specific constraints using references/cloudkit.md.
  4. If the project targets iOS 18+, check for indexing opportunities using references/indexing.md.
  5. 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.

References

TopicReference
Autosave, relationships, delete rules, @Query restrictions, #Unique, @Transientreferences/core-rules.md
Supported predicates, dangerous patterns that crash at runtime, unsupported methodsreferences/predicates.md
CloudKit constraints: no #Unique, optional requirements, eventual consistencyreferences/cloudkit.md
Database indexing (iOS 18+), single and compound property indexesreferences/indexing.md
Model subclassing (iOS 26+), @available requirements, predicate filteringreferences/class-inheritance.md

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.