file-provider-and-finder-sync-workflowlisted

# File Provider and Finder Sync Workflow ## Purpose Choose the correct filesystem extension model. File Provider is the modern path for remote-storage synchronization: it enumerates items, materializes content, receives file operations, and reports remote changes to the system. Finder Sync is a macOS Finder UI extension for monitored-folder badges, contextual menus, and visibility; it does not implement remote synchronization itself. This skill owns that decision, File Provider synchronization mechanics, and Finder Sync’s limited UI role. It does not own a storage backend protocol, generic networking, or unrelated app-extension architecture. ## When To Use - Use this skill when an Apple app exposes remote storage in Files or Finder, synchronizes cloud-backed files, handles placeholders, materializes content, or reconciles remote changes. - Use this skill when a macOS app needs Finder badges, toolbar/contextual menus, selected-item context, or monitored-folder visibility. - Use `app-extension-architecture-workflow` when target/process, entitlement, app-group, or general extension decisions remain unresolved. - Use `swift-openapi-client-workflow` or server-side skills when the storage service contract or transport is the main unresolved concern. - Use `xcode-build-run-workflow`, `xcode-testing-workflow`, and `macos-distribution-workflow` for execution, testing, and release evidence. ## Single-Path Workflow 1. Classify the requested outcome: - choose File Provider when