[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7ANNX8JNAGHAEC78KP09F5K":3,"skill-same:01M7ANNX8JNAGHAEC78KP09F5K":66},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":27,"commitSha":28,"skillDirectory":29,"forksCount":14,"repositoryHtmlUrl":30,"repositoryHomepageUrl":6,"ownerHtmlUrl":31,"ownerBlogUrl":6,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M7ANNX8JNAGHAEC78KP09F5K","swift-concurrency-expert",null,"Review and fix Swift concurrency issues such as actor isolation and Sendable violations.","GongYuanCaiJi\u002Fdsh-claude-code-templates","GongYuanCaiJi","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F129952120?v=4","01M7AK39Q4W3VPF7C1K8M58BFX","劉昱廷 Yu-Ting Liu","01M7AK39QPS2RAJKRQY0EPQJPZ",0,"MIT","https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-code-templates\u002Fblob\u002Fmain\u002Fskills\u002Fdevelopment\u002Fswift-concurrency-expert\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: swift-concurrency-expert\ndescription: Review and fix Swift concurrency issues such as actor isolation and Sendable violations.\nrisk: safe\nsource: \"Dimillian\u002FSkills (MIT)\"\ndate_added: \"2026-03-25\"\n---\n\n# Swift Concurrency Expert\n\n## Overview\n\nReview and fix Swift Concurrency issues in Swift 6.2+ codebases by applying actor isolation, Sendable safety, and modern concurrency patterns with minimal behavior changes.\n\n## When to Use\n\n- When the user asks to review Swift concurrency usage or fix compiler diagnostics.\n- When you need guidance on actor isolation, `Sendable`, `@MainActor`, or async migration.\n\n## Workflow\n\n### 1. Triage the issue\n\n- Capture the exact compiler diagnostics and the offending symbol(s).\n- Check project concurrency settings: Swift language version (6.2+), strict concurrency level, and whether approachable concurrency (default actor isolation \u002F main-actor-by-default) is enabled.\n- Identify the current actor context (`@MainActor`, `actor`, `nonisolated`) and whether a default actor isolation mode is enabled.\n- Confirm whether the code is UI-bound or intended to run off the main actor.\n\n### 2. Apply the smallest safe fix\n\nPrefer edits that preserve existing behavior while satisfying data-race safety.\n\nCommon fixes:\n- **UI-bound types**: annotate the type or relevant members with `@MainActor`.\n- **Protocol conformance on main actor types**: make the conformance isolated (e.g., `extension Foo: @MainActor SomeProtocol`).\n- **Global\u002Fstatic state**: protect with `@MainActor` or move into an actor.\n- **Background work**: move expensive work into a `@concurrent` async function on a `nonisolated` type or use an `actor` to guard mutable state.\n- **Sendable errors**: prefer immutable\u002Fvalue types; add `Sendable` conformance only when correct; avoid `@unchecked Sendable` unless you can prove thread safety.\n\n### 3. Verify the fix\n\n- Rebuild and confirm all concurrency diagnostics are resolved with no new warnings introduced.\n- Run the test suite to check for regressions — concurrency changes can introduce subtle runtime issues even when the build is clean.\n- If the fix surfaces new warnings, treat each one as a fresh triage (return to step 1) and resolve iteratively until the build is clean and tests pass.\n\n### Examples\n\n**UI-bound type — adding `@MainActor`**\n\n```swift\n\u002F\u002F Before: data-race warning because ViewModel is accessed from the main thread\n\u002F\u002F but has no actor isolation\nclass ViewModel: ObservableObject {\n    @Published var title: String = \"\"\n    func load() { title = \"Loaded\" }\n}\n\n\u002F\u002F After: annotate the whole type so all stored state and methods are\n\u002F\u002F automatically isolated to the main actor\n@MainActor\nclass ViewModel: ObservableObject {\n    @Published var title: String = \"\"\n    func load() { title = \"Loaded\" }\n}\n```\n\n**Protocol conformance isolation**\n\n```swift\n\u002F\u002F Before: compiler error — SomeProtocol method is nonisolated but the\n\u002F\u002F conforming type is @MainActor\n@MainActor\nclass Foo: SomeProtocol {\n    func protocolMethod() { \u002F* accesses main-actor state *\u002F }\n}\n\n\u002F\u002F After: scope the conformance to @MainActor so the requirement is\n\u002F\u002F satisfied inside the correct isolation context\n@MainActor\nextension Foo: SomeProtocol {\n    func protocolMethod() { \u002F* safely accesses main-actor state *\u002F }\n}\n```\n\n**Background work with `@concurrent`**\n\n```swift\n\u002F\u002F Before: expensive computation blocks the main actor\n@MainActor\nfunc processData(_ input: [Int]) -> [Int] {\n    input.map { heavyTransform($0) }   \u002F\u002F runs on main thread\n}\n\n\u002F\u002F After: hop off the main actor for the heavy work, then return the result\n\u002F\u002F The caller awaits the result and stays on its own actor\nnonisolated func processData(_ input: [Int]) async -> [Int] {\n    await Task.detached(priority: .userInitiated) {\n        input.map { heavyTransform($0) }\n    }.value\n}\n\n\u002F\u002F Or, using a @concurrent async function (Swift 6.2+):\n@concurrent\nfunc processData(_ input: [Int]) async -> [Int] {\n    input.map { heavyTransform($0) }\n}\n```\n\n## Reference material\n\n- See `references\u002Fswift-6-2-concurrency.md` for Swift 6.2 changes, patterns, and examples.\n- See `references\u002Fapproachable-concurrency.md` when the project is opted into approachable concurrency mode.\n- See `references\u002Fswiftui-concurrency-tour-wwdc.md` for SwiftUI-specific concurrency guidance.\n","# Swift Concurrency Expert\n\n## Overview\n\nReview and fix Swift Concurrency issues in Swift 6.2+ codebases by applying actor isolation, Sendable safety, and modern concurrency patterns with minimal behavior changes.\n\n## When to Use\n\n- When the user asks to review Swift concurrency usage or fix compiler diagnostics.\n- When you need guidance on actor isolation, `Sendable`, `@MainActor`, or async migration.\n\n## Workflow\n\n### 1. Triage the issue\n\n- Capture the exact compiler diagnostics and the offending symbol(s).\n- Check project concurrency settings: Swift language version (6.2+), strict concurrency level, and whether approachable concurrency (default actor isolation \u002F main-actor-by-default) is enabled.\n- Identify the current actor context (`@MainActor`, `actor`, `nonisolated`) and whether a default actor isolation mode is enabled.\n- Confirm whether the code is UI-bound or intended to run off the main actor.\n\n### 2. Apply the smallest safe fix\n\nPrefer edits that preserve existing behavior while satisfying data-race safety.\n\nCommon fixes:\n- **UI-bound types**: annotate the type or relevant members with `@MainActor`.\n- **Protocol conformance on main actor types**: make the conformance isolated (e.g., `extension Foo: @MainActor SomeProtocol`).\n- **Global\u002Fstatic state**: protect with `@MainActor` or move into an actor.\n- **Background work**: move expensive work into a `@concurrent` async function on a `nonisolated` type or use an `actor` to guard mutable state.\n- **Sendable errors**: prefer immutable\u002Fvalue types; add `Sendable` conformance only when correct; avoid `@unchecked Sendable` unless you can prove thread safety.\n\n### 3. Verify the fix\n\n- Rebuild and confirm all concurrency diagnostics are resolved with no new warnings introduced.\n- Run the test suite to check for regressions — concurrency changes can introduce subtle runtime issues even when the build is clean.\n- If the fix surfaces new warnings, treat each one as a fresh triage (return to step 1) and resolve iteratively until the build is clean and tests pass.\n\n### Examples\n\n**UI-bound type — adding `@MainActor`**\n\n```swift\n\u002F\u002F Before: data-race warning because ViewModel is accessed from the main thread\n\u002F\u002F but has no actor isolation\nclass ViewModel: ObservableObject {\n    @Published var title: String = \"\"\n    func load() { title = \"Loaded\" }\n}\n\n\u002F\u002F After: annotate the whole type so all stored state and methods are\n\u002F\u002F automatically isolated to the main actor\n@MainActor\nclass ViewModel: ObservableObject {\n    @Published var title: String = \"\"\n    func load() { title = \"Loaded\" }\n}\n```\n\n**Protocol conformance isolation**\n\n```swift\n\u002F\u002F Before: compiler error — SomeProtocol method is nonisolated but the\n\u002F\u002F conforming type is @MainActor\n@MainActor\nclass Foo: SomeProtocol {\n    func protocolMethod() { \u002F* accesses main-actor state *\u002F }\n}\n\n\u002F\u002F After: scope the conformance to @MainActor so the requirement is\n\u002F\u002F satisfied inside the correct isolation context\n@MainActor\nextension Foo: SomeProtocol {\n    func protocolMethod() { \u002F* safely accesses main-actor state *\u002F }\n}\n```\n\n**Background work with `@concurrent`**\n\n```swift\n\u002F\u002F Before: expensive computation blocks the main actor\n@MainActor\nfunc processData(_ input: [Int]) -> [Int] {\n    input.map { heavyTransform($0) }   \u002F\u002F runs on main thread\n}\n\n\u002F\u002F After: hop off the main actor for the heavy work, then return the result\n\u002F\u002F The caller awaits the result and stays on its own actor\nnonisolated func processData(_ input: [Int]) async -> [Int] {\n    await Task.detached(priority: .userInitiated) {\n        input.map { heavyTransform($0) }\n    }.value\n}\n\n\u002F\u002F Or, using a @concurrent async function (Swift 6.2+):\n@concurrent\nfunc processData(_ input: [Int]) async -> [Int] {\n    input.map { heavyTransform($0) }\n}\n```\n\n## Reference material\n\n- See `references\u002Fswift-6-2-concurrency.md` for Swift 6.2 changes, patterns, and examples.\n- See `references\u002Fapproachable-concurrency.md` when the project is opted into approachable concurrency mode.\n- See `references\u002Fswiftui-concurrency-tour-wwdc.md` for SwiftUI-specific concurrency guidance.\n",{"name":5,"risk":24,"source":25,"date_added":26,"description":7},"safe","Dimillian\u002FSkills (MIT)","2026-03-25","main","51493f354fd03e3f941d4df7fd64c0b8c7a2632d","skills\u002Fdevelopment\u002Fswift-concurrency-expert","https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-code-templates","https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi","漏洞研究、根因分析、黑箱測試｜做 AI agent 工具｜Vulnerability research, root-cause analysis, AI agent tooling","2026-08-16 02:24:07",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add GongYuanCaiJi\u002Fdsh-claude-code-templates --skill swift-concurrency-expert",{"tool":40,"command":41},"bunx","bunx skills add GongYuanCaiJi\u002Fdsh-claude-code-templates --skill swift-concurrency-expert",{"tool":43,"command":44},"pnpm","pnpm dlx skills add GongYuanCaiJi\u002Fdsh-claude-code-templates --skill swift-concurrency-expert","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-code-templates\u002Fblob\u002Fmain\u002Fskills\u002Fdevelopment\u002Fswift-concurrency-expert\u002FSKILL.md",true,[48,54,58,62],{"path":49,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":52,"sourceHtmlUrl":53},"agents\u002Fopenai.yaml","REFERENCE","参考文档",243,"https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-code-templates\u002Fblob\u002Fmain\u002Fskills\u002Fdevelopment\u002Fswift-concurrency-expert\u002Fagents\u002Fopenai.yaml",{"path":55,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":56,"sourceHtmlUrl":57},"references\u002Fapproachable-concurrency.md",2471,"https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-code-templates\u002Fblob\u002Fmain\u002Fskills\u002Fdevelopment\u002Fswift-concurrency-expert\u002Freferences\u002Fapproachable-concurrency.md",{"path":59,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":60,"sourceHtmlUrl":61},"references\u002Fswift-6-2-concurrency.md",10673,"https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-code-templates\u002Fblob\u002Fmain\u002Fskills\u002Fdevelopment\u002Fswift-concurrency-expert\u002Freferences\u002Fswift-6-2-concurrency.md",{"path":63,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":64,"sourceHtmlUrl":65},"references\u002Fswiftui-concurrency-tour-wwdc.md",1645,"https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-code-templates\u002Fblob\u002Fmain\u002Fskills\u002Fdevelopment\u002Fswift-concurrency-expert\u002Freferences\u002Fswiftui-concurrency-tour-wwdc.md",[67,74,83,90,97,104],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":19},"01M7ARMYTZ5D4B7N5SKFXV345V","zapier-make-patterns","No-code automation democratizes workflow building. Zapier and Make (formerly Integromat) let non-developers automate business processes without writing code. But no-code doesn't mean no-complexity - these platforms have their own patterns, pitfalls, and breaking points.  This skill covers when to use which platform, how to build reliable automations, and when to graduate to code-based solutions. Key insight: Zapier optimizes for simplicity and integrations (7000+ apps), Make optimizes for power","https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-code-templates\u002Fblob\u002Fmain\u002Fskills\u002Fworkflow-automation\u002Fzapier-make-patterns\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":78,"licenseFileUrl":79,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":19},"01M7ARMX1BVNEAR98SBANMDF2V","yeet","Use only when the user explicitly asks to stage, commit, push, and open a GitHub pull request in one flow using the GitHub CLI (`gh`).","Apache-2.0","https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-code-templates\u002Fblob\u002Fmain\u002Fskills\u002Fworkflow-automation\u002Fyeet\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-code-templates\u002Fblob\u002Fmain\u002Fskills\u002Fworkflow-automation\u002Fyeet\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M7ARMPR4RQ417MG1HMPGNQHH","workflow-automation","Workflow automation is the infrastructure that makes AI agents reliable. Without durable execution, a network hiccup during a 10-step payment flow means lost money and angry customers. With it, workflows resume exactly where they left off.  This skill covers the platforms (n8n, Temporal, Inngest) and patterns (sequential, parallel, orchestrator-worker) that turn brittle scripts into production-grade automation.  Key insight: The platforms make different tradeoffs. n8n optimizes for accessibility","https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-code-templates\u002Fblob\u002Fmain\u002Fskills\u002Fworkflow-automation\u002Fworkflow-automation\u002FSKILL.md",[],[],{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":19},"01M7ARMHBERDMKGDMV7K6MQ6YP","trigger-dev","Trigger.dev expert for background jobs, AI workflows, and reliable async execution with excellent developer experience and TypeScript-first design. Use when: trigger.dev, trigger dev, background task, ai background job, long running task.","https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-code-templates\u002Fblob\u002Fmain\u002Fskills\u002Fworkflow-automation\u002Ftrigger-dev\u002FSKILL.md",[],[],{"skillNo":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":103,"publishedAt":19},"01M7ARME0A7KFT330Q2H25HE2B","slack-automation","Automate Slack workspace operations including messaging, search, channel management, and reaction workflows through Composio's Slack toolkit.","https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-code-templates\u002Fblob\u002Fmain\u002Fskills\u002Fworkflow-automation\u002Fslack-automation\u002FSKILL.md",[],[],{"skillNo":105,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":108,"categories":109,"keywords":110,"publishedAt":19},"01M7ARM8D87V18WDG0GEZS11ZT","planning-with-files","Transforms workflow to use Manus-style persistent markdown files for planning, progress tracking, and knowledge storage. Use when starting complex tasks, multi-step projects, research tasks, or when the user mentions planning, organizing work, tracking progress, or wants structured output.","https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-code-templates\u002Fblob\u002Fmain\u002Fskills\u002Fworkflow-automation\u002Fplanning-with-files\u002FSKILL.md",[],[]]