[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M77VWDZP14ARVBV7JMBCAEWP":3,"skill-same:01M77VWDZP14ARVBV7JMBCAEWP":51},{"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":28,"commitSha":29,"skillDirectory":30,"forksCount":31,"repositoryHtmlUrl":32,"repositoryHomepageUrl":33,"ownerHtmlUrl":34,"ownerBlogUrl":6,"ownerDescription":35,"updatedAt":36,"install":37,"resources":50},"01M77VWDZP14ARVBV7JMBCAEWP","swiftui-macos",null,"Expert SwiftUI guidance for macOS apps — covers writing and reviewing code with runtime-level understanding of observation, concurrency, performance, and platform integration. Use when user asks to \"build a SwiftUI view\", \"review my SwiftUI code\", \"fix observation issues\", \"bridge AppKit\", \"architect state management\", \"debug view updates\", or works on any macOS SwiftUI project — building features, reviewing existing code, debugging view updates or performance, fixing concurrency issues, architecting state management, bridging AppKit, or making design decisions. Do NOT use for iOS\u002FiPadOS-only SwiftUI, UIKit bridging, or basic Swift language questions. Focuses on non-obvious traps and deep patterns, not basics.","Lord1Egypt\u002Fawesome-skill-forge","Lord1Egypt","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F99746359?v=4","01M7592YDNT0XK9WJ0T2MQVPDN","Mohamed Mounir Ali AL Keshita","01M75GRFNHC8VZNWEB8DKDE433",3,"MIT","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fcommunity\u002Fclawhub\u002Fs\u002Fswiftui-macos\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: swiftui-macos\ndescription: Expert SwiftUI guidance for macOS apps — covers writing and reviewing code with runtime-level understanding of observation, concurrency, performance, and platform integration. Use when user asks to \"build a SwiftUI view\", \"review my SwiftUI code\", \"fix observation issues\", \"bridge AppKit\", \"architect state management\", \"debug view updates\", or works on any macOS SwiftUI project — building features, reviewing existing code, debugging view updates or performance, fixing concurrency issues, architecting state management, bridging AppKit, or making design decisions. Do NOT use for iOS\u002FiPadOS-only SwiftUI, UIKit bridging, or basic Swift language questions. Focuses on non-obvious traps and deep patterns, not basics.\nlicense: MIT\ncompatibility: Requires macOS 26+ targeting and Swift 6.2 with strict concurrency. Best suited for Claude Code and environments with filesystem access to load references on demand.\nmetadata:\n  author: kageroumado\n  version: 1.0.0\n---\n\nGuide SwiftUI development for macOS apps. Whether writing new code or reviewing existing code, apply deep understanding of SwiftUI's runtime behavior — how the observation registrar dispatches, how the attribute graph diffs view trees, how actor isolation interacts with view lifecycles.\n\n## How to Use\n\n**Writing code**: Load relevant references before implementation. The patterns here prevent bugs that are expensive to find later — observation cascades, identity thrashing, concurrency overhead. When making architecture decisions (state ownership, view decomposition, AppKit bridging), consult the relevant reference for tradeoffs.\n\n**Reviewing code**: Check each reference area systematically. Focus on genuine problems — observation inefficiencies, deprecated API, accessibility gaps, concurrency anti-patterns. Don't flag obvious issues or invent problems.\n\n**Partial scope**: Load only what the task needs. Not every change requires all eight references.\n\n## References\n\n| Reference | Load when |\n|---|---|\n| `references\u002Fobservation.md` | `@Observable`, `@State`, `ForEach`, data-driven views, `Observations {}` streams |\n| `references\u002Fconcurrency.md` | `Task`, `async`\u002F`await`, actors, `DispatchQueue`, `AsyncStream`, scheduling decisions |\n| `references\u002Fperformance.md` | View composition, animations, gestures, large collections, `Canvas`, `TimelineView` |\n| `references\u002Fviews.md` | View decomposition, navigation, `.task(id:)`, preference keys, custom `Layout` |\n| `references\u002Fdata.md` | State architecture, SwiftData, environment injection, bindings, persistence |\n| `references\u002Fplatform.md` | `NSViewRepresentable`, `NSHostingView`, multi-window, AppKit bridging, window chrome |\n| `references\u002Fapi.md` | API choice, deprecated patterns, modern Swift\u002FSwiftUI idioms |\n| `references\u002Faccessibility.md` | VoiceOver, keyboard navigation, Dynamic Type, Reduce Motion |\n\n## Principles\n\n- Target **macOS 26+**, Swift 6.2 with strict concurrency and `@MainActor` default isolation.\n- Check whether the project enables **`NonisolatedNonsendingByDefault`** (SE-0461) — this changes where `nonisolated` async functions execute. See `references\u002Fconcurrency.md`.\n- Prefer SwiftUI-native solutions. Use AppKit (`NSViewRepresentable`, `NSHostingView`, `NSWindow`) only when SwiftUI has no equivalent.\n- **Understand the mechanism.** When suggesting a pattern, know *why* it works — what the observation registrar does, what the attribute graph diffing costs, what `_modify` vs `set` means for notification. Rules without understanding produce cargo-culted code.\n- Do not introduce third-party frameworks without asking. Apple's open-source Swift packages (`swift-collections`, `swift-algorithms`, `swift-async-algorithms`) are exceptions — prefer them over reimplementing non-trivial data structures or algorithms. See `references\u002Fapi.md`.\n\n## Examples\n\n**User**: \"Review observation patterns in these sidebar views\"\n→ Load `references\u002Fobservation.md`. Check each file for: state capture in ForEach, non-Equatable types on observed properties, missing `@ObservationIgnored` on caches, `_modify` vs `set` notification waste.\n\n**User**: \"I need to embed an NSCollectionView in SwiftUI\"\n→ Load `references\u002Fplatform.md`. Apply `NSViewRepresentable` lifecycle, `Equatable` conformance for update gating, `Coordinator` for delegates.\n\n**User**: \"This view is re-rendering too much, help me debug it\"\n→ Load `references\u002Fperformance.md` and `references\u002Fobservation.md`. Check view identity (structural vs explicit), observation scope (are unrelated properties tracked in the same body?), `@State` vs `@Observable` for gesture-driven values.\n\n## Review Output\n\nOrganize findings by file. For each issue:\n\n1. File and relevant line(s).\n2. The pattern being violated and *why it matters* at the runtime level.\n3. Brief before\u002Fafter code fix.\n\nSkip clean files. End with a prioritized summary of the most impactful changes.\n","Guide SwiftUI development for macOS apps. Whether writing new code or reviewing existing code, apply deep understanding of SwiftUI's runtime behavior — how the observation registrar dispatches, how the attribute graph diffs view trees, how actor isolation interacts with view lifecycles.\n\n## How to Use\n\n**Writing code**: Load relevant references before implementation. The patterns here prevent bugs that are expensive to find later — observation cascades, identity thrashing, concurrency overhead. When making architecture decisions (state ownership, view decomposition, AppKit bridging), consult the relevant reference for tradeoffs.\n\n**Reviewing code**: Check each reference area systematically. Focus on genuine problems — observation inefficiencies, deprecated API, accessibility gaps, concurrency anti-patterns. Don't flag obvious issues or invent problems.\n\n**Partial scope**: Load only what the task needs. Not every change requires all eight references.\n\n## References\n\n| Reference | Load when |\n|---|---|\n| `references\u002Fobservation.md` | `@Observable`, `@State`, `ForEach`, data-driven views, `Observations {}` streams |\n| `references\u002Fconcurrency.md` | `Task`, `async`\u002F`await`, actors, `DispatchQueue`, `AsyncStream`, scheduling decisions |\n| `references\u002Fperformance.md` | View composition, animations, gestures, large collections, `Canvas`, `TimelineView` |\n| `references\u002Fviews.md` | View decomposition, navigation, `.task(id:)`, preference keys, custom `Layout` |\n| `references\u002Fdata.md` | State architecture, SwiftData, environment injection, bindings, persistence |\n| `references\u002Fplatform.md` | `NSViewRepresentable`, `NSHostingView`, multi-window, AppKit bridging, window chrome |\n| `references\u002Fapi.md` | API choice, deprecated patterns, modern Swift\u002FSwiftUI idioms |\n| `references\u002Faccessibility.md` | VoiceOver, keyboard navigation, Dynamic Type, Reduce Motion |\n\n## Principles\n\n- Target **macOS 26+**, Swift 6.2 with strict concurrency and `@MainActor` default isolation.\n- Check whether the project enables **`NonisolatedNonsendingByDefault`** (SE-0461) — this changes where `nonisolated` async functions execute. See `references\u002Fconcurrency.md`.\n- Prefer SwiftUI-native solutions. Use AppKit (`NSViewRepresentable`, `NSHostingView`, `NSWindow`) only when SwiftUI has no equivalent.\n- **Understand the mechanism.** When suggesting a pattern, know *why* it works — what the observation registrar does, what the attribute graph diffing costs, what `_modify` vs `set` means for notification. Rules without understanding produce cargo-culted code.\n- Do not introduce third-party frameworks without asking. Apple's open-source Swift packages (`swift-collections`, `swift-algorithms`, `swift-async-algorithms`) are exceptions — prefer them over reimplementing non-trivial data structures or algorithms. See `references\u002Fapi.md`.\n\n## Examples\n\n**User**: \"Review observation patterns in these sidebar views\"\n→ Load `references\u002Fobservation.md`. Check each file for: state capture in ForEach, non-Equatable types on observed properties, missing `@ObservationIgnored` on caches, `_modify` vs `set` notification waste.\n\n**User**: \"I need to embed an NSCollectionView in SwiftUI\"\n→ Load `references\u002Fplatform.md`. Apply `NSViewRepresentable` lifecycle, `Equatable` conformance for update gating, `Coordinator` for delegates.\n\n**User**: \"This view is re-rendering too much, help me debug it\"\n→ Load `references\u002Fperformance.md` and `references\u002Fobservation.md`. Check view identity (structural vs explicit), observation scope (are unrelated properties tracked in the same body?), `@State` vs `@Observable` for gesture-driven values.\n\n## Review Output\n\nOrganize findings by file. For each issue:\n\n1. File and relevant line(s).\n2. The pattern being violated and *why it matters* at the runtime level.\n3. Brief before\u002Fafter code fix.\n\nSkip clean files. End with a prioritized summary of the most impactful changes.\n",{"name":5,"license":15,"metadata":24,"description":7,"compatibility":27},{"author":25,"version":26},"kageroumado","1.0.0","Requires macOS 26+ targeting and Swift 6.2 with strict concurrency. Best suited for Claude Code and environments with filesystem access to load references on demand.","master","4aa004da461d820f4ea5499e58eb8d196cf99016","community\u002Fclawhub\u002Fs\u002Fswiftui-macos",0,"https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge","https:\u002F\u002Fskill-explorer-rho.vercel.app","https:\u002F\u002Fgithub.com\u002FLord1Egypt","Unbreakable. Unstoppable. Unmatched⚡.\r\n Speaker of machine tongues 🤖  | World-builder of decentralized dreams 🌐 | Defender of the digital realm🛡️.","2026-06-10 08:21:01",{"source":8,"skillName":5,"commands":38,"prompt":48,"zipAvailable":49},[39,42,45],{"tool":40,"command":41},"npx","npx skills add Lord1Egypt\u002Fawesome-skill-forge --skill swiftui-macos",{"tool":43,"command":44},"bunx","bunx skills add Lord1Egypt\u002Fawesome-skill-forge --skill swiftui-macos",{"tool":46,"command":47},"pnpm","pnpm dlx skills add Lord1Egypt\u002Fawesome-skill-forge --skill swiftui-macos","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fcommunity\u002Fclawhub\u002Fs\u002Fswiftui-macos\u002FSKILL.md",true,[],[52,59,66,73,80,87],{"skillNo":53,"name":54,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":19},"01M785WKJB99G3STR1NF9NRTJW","youtube-content","YouTube transcripts to summaries, threads, blogs.","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fskills\u002Fyoutube-content\u002FSKILL.md",[],[],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":19},"01M785WEFHB0G2S9YA6EPR3H0E","xurl","X\u002FTwitter via xurl CLI: post, search, DM, media, v2 API.","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fskills\u002Fxurl\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":19},"01M785W98EDN4EFJXJPMQEHCRC","touchdesigner-mcp","Control a running TouchDesigner instance via twozero MCP — create operators, set parameters, wire connections, execute Python, build real-time visuals. 36 native tools.","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fskills\u002Ftouchdesigner-mcp\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":19},"01M785W5S9FP3QBH2V191E025P","test-driven-development","TDD: enforce RED-GREEN-REFACTOR, tests before code.","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fskills\u002Ftest-driven-development\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":19},"01M785W2AS08NSSH9YATCV6FJB","teams-meeting-pipeline","Operate the Teams meeting summary pipeline via Hermes CLI — summarize meetings, inspect pipeline status, replay jobs, manage Microsoft Graph subscriptions.","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fskills\u002Fteams-meeting-pipeline\u002FSKILL.md",[],[],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":19},"01M785VXKW4T34BTP1SCHW1R7F","systematic-debugging","4-phase root cause debugging: understand bugs before fixing.","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fskills\u002Fsystematic-debugging\u002FSKILL.md",[],[]]