The Mental Faculty contributor

Ensembles

Ship Core Data and SwiftData sync with Ensembles 3 while migrating from E2 and handling compatibility and transformable-attribute edge cases.

Overview

ensembles is a plugin marketplace for the Build phase that brings Claude Code up to speed on the Ensembles 3 API, E2 migration, seed policy, compatibility mode, and transformable-attribute sync issues.

What is this marketplace?

  • Covers the Ensembles 3 API surface Claude needs for correct sync calls
  • Documents E2-to-E3 migration paths and seed policy decisions
  • Explains compatibility mode when mixing legacy and v3 stacks
  • Surfaces transformable-attribute sync failure patterns and fixes
  • Single-plugin marketplace focused on SwiftData and Core Data sync

Compatible agents: Claude Code, Cursor, any compatible agent

Community signal: 29 GitHub stars.

What problem does it solve?

You are implementing Ensembles 3 sync but keep hitting E2 migration traps, seed-policy mistakes, and transformable-attribute sync bugs the docs scatter across threads.

Who is it for?

Indie iOS or macOS builders actively integrating Ensembles 3 with Core Data or SwiftData who want agent answers aligned to Mental Faculty’s sync model.

Skip if: Teams on CloudKit-only sync, Android backends, or greenfield apps with no Ensembles legacy who only need generic CRUD patterns.

What do I get? / Deliverables

After adding the marketplace, Claude can propose Ensembles 3–correct API usage, migration steps, and targeted fixes for compatibility and transformable-attribute sync failures.

  • Agent-grounded Ensembles 3 API and migration guidance in coding sessions
  • Clearer handling of compatibility mode and transformable-attribute sync cases
  • Reduced back-and-forth when debugging Ensembles-specific sync errors

Plugins in this marketplace

1 plugin — install individually after you add the marketplace.

Recommended Marketplaces

Journey fit

Canonical shelf is Build because the marketplace packages guidance and tooling for wiring and maintaining data sync during product implementation. Integrations fits Ensembles 3 API usage, E2-to-E3 migration, seed policy, and sync behavior—not generic UI or docs work.

How it compares

Framework-specific Claude marketplace, not a general database skill or hosted MCP server.

Common Questions / FAQ

Who is Ensembles for?

Solo and small-team Apple developers using Ensembles 3 for multi-device Core Data or SwiftData sync who rely on Claude Code during integration and migration.

When should I use Ensembles?

Use it during Build when you are wiring sync, migrating from Ensembles 2, or debugging seed policy, compatibility mode, and transformable-attribute issues.

How do I add Ensembles to my agent?

Add the mentalfaculty/Ensembles3 Claude Code marketplace from the catalog, install the Ensembles plugin, and invoke it in sessions where you edit sync-related Swift or Core Data models.

This week for builders

Five minutes, every Monday — the tools, releases and tactics for shipping solo.

unsubscribe anytime.