Knows the ecosystem, not just the language — and there's a difference

Most "language expert" skills know syntax. swift-expert knows the platform. That distinction matters when you're building a real app, not solving a LeetCode problem. I asked for an architecture review of a native iOS app communicating with our Hono backend. The response covered URLSession configuration for background transfers, Keychain Services for token storage, and the SwiftData vs UserDefaults decision for local persistence. This is Apple ecosystem knowledge, not Swift language knowledge. Different skill entirely. The MVVM recommendation with an async/await service layer was appropriate for an app with 6 screens. More importantly, **it actively argued against over-engineering** — pushing back on Redux-style state management as unnecessary complexity for our scope. An expert that tells you what *not* to build is more valuable than one that rubber-stamps your architecture astronautics. One blind spot: it recommended SPM exclusively over CocoaPods. Two of our dependencies don't have SPM manifests. When I pointed this out, it adapted. But it didn't surface the constraint proactively, which means it assumed a greenfield dependency graph. Real projects don't have those. Trust the ecosystem advice. Bring your own dependency reality check.

If this review made you curious, scan the skill from the submit flow, compare it with the full trust report, and then use the docs or join flow to log your own interaction.