automerge-swift

Natural-language entry point for Automerge Swift. Use when the user has an Automerge question but does not know which skill to invoke.

Scan your Automerge Swift code for anti-patterns and common mistakes

Use this agent when the user wants to audit their Automerge Swift code for anti-patterns, or when reviewing code that uses the automerge-swift package. Automatically scans for the initial data problem, String-vs-Text misuse, missing error handling, sync protocol issues, and ObjId mismanagement — prevents merge garbage, silent data loss, and hard-to-debug runtime errors. <example> user: "Can you check my Automerge code for issues?" assistant: [Launches automerge-auditor agent] </example> <example> user: "Review my CRDT code for best practices" assistant: [Launches automerge-auditor agent] </example> <example> user: "Audit my collaborative editing implementation" assistant: [Launches automerge-auditor agent] </example> <example> user: "My merges are producing garbage, can you scan my code?" assistant: [Launches automerge-auditor agent] </example> <example> user: "Check if I'm using Automerge correctly" assistant: [Launches automerge-auditor agent] </example> Explicit command: Users can also invoke this agent directly with `/automerge:audit`

Look up Automerge Swift APIs, Document operations, Codable mapping, collaborative text, sync protocol, and schema patterns.

Use when working with Automerge Swift, automerge-swift package, CRDTs in Swift, collaborative/real-time data, Document merge/fork/sync, or any code importing Automerge. Routes to specialized sub-skills for core API, Codable mapping, sync protocol, and API reference. Even if the task seems simple, check this skill first - Automerge has non-obvious patterns that differ from typical Swift data handling.

Use when synchronizing Automerge documents between peers, implementing sync protocols over network/WebSocket, forking and merging documents, tracking change history, reading historical values, using patches for UI updates, or working with SyncState, ChangeHash, Change, Patch, or PatchAction types. Also use when asking 'how do I sync automerge documents', 'how do merges work', or 'how do I get notified of changes'.

Use when working with collaborative text editing in Automerge — AutomergeText, Cursor, Position, Mark, ExpandMark, spliceText, updateText, text marks/formatting, or building a collaborative text editor with Automerge. Also use when asking 'how do I do concurrent text editing', 'how do marks work', or 'AutomergeText vs String'.

Use when encoding/decoding Swift Codable types to/from Automerge documents, working with AutomergeEncoder or AutomergeDecoder, using AutomergeText for collaborative text fields, using Counter for concurrent counters, choosing SchemaStrategy, or deciding between Codable layer vs core API. Also use when you see 'automerge encoder', 'automerge decoder', 'AutomergeText', or schema strategy questions.

Use when creating Automerge documents, navigating with ObjId, reading/writing maps/lists/text using the core Document API, working with ScalarValue or Value types, or needing fine-grained control over document mutations. Use this instead of the Codable skill when you need performance (high-frequency updates) or when working with the low-level document structure directly.

3 hooks across 2 events