[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79SZ6QFMPXAS1XGZN1R3Q8K":3,"skill-same:01M79SZ6QFMPXAS1XGZN1R3Q8K":53},{"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":32,"commitSha":33,"skillDirectory":34,"forksCount":14,"repositoryHtmlUrl":35,"repositoryHomepageUrl":6,"ownerHtmlUrl":36,"ownerBlogUrl":6,"ownerDescription":37,"updatedAt":38,"install":39,"resources":52},"01M79SZ6QFMPXAS1XGZN1R3Q8K","appkit-architect",null,"Architect-level macOS-native design — AppKit versus SwiftUI for desktop, window and menu architecture, document-based apps and NSDocument, sandboxing and entitlements, Mac App Store versus direct distribution, and the macOS conventions users expect. Use when the app must feel native on macOS.","SriAkhilSJ\u002FPulseAIRepo","SriAkhilSJ","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F206201543?v=4","01M79RWFD1Q09B89SXTTKKJY6Z","Sri Akhil SJ","01M79RWFE26NPG0BZ1FRNX376H",0,"MIT","https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo\u002Fblob\u002Fmain\u002Fskills\u002Fdesktop-architect\u002Fruntimes-architect\u002Fappkit-architect\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: appkit-architect\ndescription: Architect-level macOS-native design — AppKit versus SwiftUI for desktop, window and menu architecture, document-based apps and NSDocument, sandboxing and entitlements, Mac App Store versus direct distribution, and the macOS conventions users expect. Use when the app must feel native on macOS.\nlicense: MIT\ncompatibility: AppKit, SwiftUI on macOS, Swift, notarisation\nmetadata:\n  crusor-domain: desktop-architect\n  crusor-path: desktop-architect\u002Fruntimes-architect\u002Fappkit-architect\n  crusor-origin: original\n  crusor-sources: \"developer.apple.com\u002Fdocumentation\u002Fappkit; developer.apple.com\u002Fdocumentation\u002Fswiftui; developer.apple.com\u002Fdocumentation\u002Fsecurity\u002Fapp_sandbox\"\n  crusor-triggers: \"appkit, macos app, nsdocument, mac app sandbox, mac catalyst, app store mac, menu bar app, notarization mac, mac app, macos, menu bar, menubar app\"\n  crusor-verified-on: \"2026-10-30\"\n---\n\n# AppKit \u002F macOS Architect\n\nA macOS app is judged on **menus, windows, and sandbox behaviour**. Users do not\nforgive a Mac app that behaves like a website in a frame.\n\n## When to use\n\n- A native Mac experience is the product (pro apps, developer tools, utilities).\n- Deep system integration: services, drag and drop, menu bar, document handling.\n- App Store or notarised direct distribution.\n\n## When NOT to use\n\n- The same UI must ship on Windows\u002FLinux → Electron\u002FTauri first.\n- A thin client where a web app suffices.\n\n## Decision 1 — AppKit or SwiftUI\n\n| Need | Choice |\n|---|---|\n| new app, mostly standard UI | SwiftUI, AppKit where it falls short |\n| document-based, complex window management | AppKit with SwiftUI views inside |\n| menu bar utility | SwiftUI `MenuBarExtra` or AppKit status item |\n| pro app with custom canvases | AppKit + Metal\u002FSceneKit |\n\n- SwiftUI on macOS still lacks mature equivalents for some AppKit patterns; use\n  `NSViewRepresentable` deliberately rather than fighting the framework.\n- One navigation model: sidebar\u002Fsplit view, not a pile of windows.\n\n## Decision 2 — macOS conventions\n\n- Menu bar with the standard menus and keyboard shortcuts; a Mac app without a proper\n  menu feels foreign.\n- Preferences via `Settings` scene\u002F`NSWindowController`, not a custom modal.\n- Window state restoration; users expect the app to reopen where they left it.\n- Drag and drop, Quick Look, Services, and keyboard navigation where applicable.\n\n## Decision 3 — Documents\n\n- `NSDocument`\u002F`ReferenceFileDocument` for document-based apps — undo, autosave, and\n  versions come almost free.\n- iCloud Drive or a user-chosen folder; the sandbox restricts arbitrary paths.\n- Autosave and version browsing are expected behaviours in a document app.\n\n## Decision 4 — Sandbox and entitlements\n\n- App Sandbox required for the App Store; strongly recommended for direct distribution.\n- Entitlements are per capability: file access (user-selected), network client,\n  printing, camera.\n- Security-scoped bookmarks for persistent access outside the container.\n- Hardened runtime + notarisation for direct distribution; check Gatekeeper on a clean\n  machine.\n\n## Decision 5 — Distribution\n\n- App Store: sandbox, review, 30% (or reduced rate), no self-update.\n- Direct: notarised DMG, Sparkle-style update, licence handling you own.\n- Both: one codebase, capability detection at build time; keep the differences in a\n  thin layer.\n\n## Failure modes at scale\n\n- No menu bar; keyboard shortcuts absent, users assume the app is broken.\n- Sandbox enabled late; file access patterns need a redesign.\n- Custom window chrome with broken full-screen and Split View.\n- Sparkle updates without signature verification.\n- App Store build shipped without sandbox, rejected after weeks.\n\n## Verification receipts\n\n1. Framework split documented: SwiftUI screens, AppKit integrations.\n2. Menu bar and shortcut inventory matching macOS conventions.\n3. Sandbox entitlements list with the feature each enables.\n4. Notarised build launched on a clean machine.\n5. Window restoration and document autosave tested.\n","# AppKit \u002F macOS Architect\n\nA macOS app is judged on **menus, windows, and sandbox behaviour**. Users do not\nforgive a Mac app that behaves like a website in a frame.\n\n## When to use\n\n- A native Mac experience is the product (pro apps, developer tools, utilities).\n- Deep system integration: services, drag and drop, menu bar, document handling.\n- App Store or notarised direct distribution.\n\n## When NOT to use\n\n- The same UI must ship on Windows\u002FLinux → Electron\u002FTauri first.\n- A thin client where a web app suffices.\n\n## Decision 1 — AppKit or SwiftUI\n\n| Need | Choice |\n|---|---|\n| new app, mostly standard UI | SwiftUI, AppKit where it falls short |\n| document-based, complex window management | AppKit with SwiftUI views inside |\n| menu bar utility | SwiftUI `MenuBarExtra` or AppKit status item |\n| pro app with custom canvases | AppKit + Metal\u002FSceneKit |\n\n- SwiftUI on macOS still lacks mature equivalents for some AppKit patterns; use\n  `NSViewRepresentable` deliberately rather than fighting the framework.\n- One navigation model: sidebar\u002Fsplit view, not a pile of windows.\n\n## Decision 2 — macOS conventions\n\n- Menu bar with the standard menus and keyboard shortcuts; a Mac app without a proper\n  menu feels foreign.\n- Preferences via `Settings` scene\u002F`NSWindowController`, not a custom modal.\n- Window state restoration; users expect the app to reopen where they left it.\n- Drag and drop, Quick Look, Services, and keyboard navigation where applicable.\n\n## Decision 3 — Documents\n\n- `NSDocument`\u002F`ReferenceFileDocument` for document-based apps — undo, autosave, and\n  versions come almost free.\n- iCloud Drive or a user-chosen folder; the sandbox restricts arbitrary paths.\n- Autosave and version browsing are expected behaviours in a document app.\n\n## Decision 4 — Sandbox and entitlements\n\n- App Sandbox required for the App Store; strongly recommended for direct distribution.\n- Entitlements are per capability: file access (user-selected), network client,\n  printing, camera.\n- Security-scoped bookmarks for persistent access outside the container.\n- Hardened runtime + notarisation for direct distribution; check Gatekeeper on a clean\n  machine.\n\n## Decision 5 — Distribution\n\n- App Store: sandbox, review, 30% (or reduced rate), no self-update.\n- Direct: notarised DMG, Sparkle-style update, licence handling you own.\n- Both: one codebase, capability detection at build time; keep the differences in a\n  thin layer.\n\n## Failure modes at scale\n\n- No menu bar; keyboard shortcuts absent, users assume the app is broken.\n- Sandbox enabled late; file access patterns need a redesign.\n- Custom window chrome with broken full-screen and Split View.\n- Sparkle updates without signature verification.\n- App Store build shipped without sandbox, rejected after weeks.\n\n## Verification receipts\n\n1. Framework split documented: SwiftUI screens, AppKit integrations.\n2. Menu bar and shortcut inventory matching macOS conventions.\n3. Sandbox entitlements list with the feature each enables.\n4. Notarised build launched on a clean machine.\n5. Window restoration and document autosave tested.\n",{"name":5,"license":15,"metadata":24,"description":7,"compatibility":31},{"crusor-path":25,"crusor-domain":26,"crusor-origin":27,"crusor-sources":28,"crusor-triggers":29,"crusor-verified-on":30},"desktop-architect\u002Fruntimes-architect\u002Fappkit-architect","desktop-architect","original","developer.apple.com\u002Fdocumentation\u002Fappkit; developer.apple.com\u002Fdocumentation\u002Fswiftui; developer.apple.com\u002Fdocumentation\u002Fsecurity\u002Fapp_sandbox","appkit, macos app, nsdocument, mac app sandbox, mac catalyst, app store mac, menu bar app, notarization mac, mac app, macos, menu bar, menubar app","2026-10-30","AppKit, SwiftUI on macOS, Swift, notarisation","main","8fa4e240be65b98472c9b2d3a505ade2aea1a5c6","skills\u002Fdesktop-architect\u002Fruntimes-architect\u002Fappkit-architect","https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo","https:\u002F\u002Fgithub.com\u002FSriAkhilSJ","Studying in CMR institute of Technology\r\n2024 - 2028","2026-11-13 21:02:23",{"source":8,"skillName":5,"commands":40,"prompt":50,"zipAvailable":51},[41,44,47],{"tool":42,"command":43},"npx","npx skills add SriAkhilSJ\u002FPulseAIRepo --skill appkit-architect",{"tool":45,"command":46},"bunx","bunx skills add SriAkhilSJ\u002FPulseAIRepo --skill appkit-architect",{"tool":48,"command":49},"pnpm","pnpm dlx skills add SriAkhilSJ\u002FPulseAIRepo --skill appkit-architect","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo\u002Fblob\u002Fmain\u002Fskills\u002Fdesktop-architect\u002Fruntimes-architect\u002Fappkit-architect\u002FSKILL.md",true,[],[54,61,68,75,82,89],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":19},"01M79TTAJNACCNXCEN3649CMMD","interaction-patterns-architect","Architect-level interaction design in code — choosing established patterns over invented ones, feedback and latency behaviour, destructive-action safeguards, navigation and overlay conventions, and the state model behind every interactive surface. Use when a screen has to behave, not just look.","https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo\u002Fblob\u002Fmain\u002Fskills\u002Fwebsite-architect\u002Fui-ux-implementation-architect\u002Finteraction-patterns-architect\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":19},"01M79TT2ESKB1TKZBYY9KYJHV9","design-system-ops-architect","Architect-level operation of a design system in code — token pipelines and versioning, component API and variant policy, the catalogue as the contract, adoption metrics, and the governance that stops a system from forking into three. Use when a component library must survive several teams.","https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo\u002Fblob\u002Fmain\u002Fskills\u002Fwebsite-architect\u002Fui-ux-implementation-architect\u002Fdesign-system-ops-architect\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M79TSV0PWGNK3PRX9P4JDR9N","design-handoff-architect","Architect-level design handoff — what must be specified before implementation starts, tokens over raw values, responsive and content-limit contracts, state matrices, and the review loop that catches drift between design and code. Use when a design is about to become code.","https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo\u002Fblob\u002Fmain\u002Fskills\u002Fwebsite-architect\u002Fui-ux-implementation-architect\u002Fdesign-handoff-architect\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M79TSJS9BFXNP696FMJ9GKDA","content-microcopy-architect","Architect-level UI content — where strings live, voice and terminology consistency, error and empty-state copy as part of the interface, translation-ready authoring, and the content model a product needs before it multiplies screens. Use when the words in the interface matter as much as the pixels.","https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo\u002Fblob\u002Fmain\u002Fskills\u002Fwebsite-architect\u002Fui-ux-implementation-architect\u002Fcontent-microcopy-architect\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M79TSCNBST3N1M68V1KPH9HQ","ui-ux-implementation-architect","Architect-level direction for turning a design into working UI — the handoff contract, component ownership versus screen-level layout, interaction and state conventions, design QA gates, and the review habits that keep an implementation faithful without frozen pixels. Use before any specific UI implementation skill.","https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo\u002Fblob\u002Fmain\u002Fskills\u002Fwebsite-architect\u002Fui-ux-implementation-architect\u002FSKILL.md",[],[],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":19},"01M79TS4N6A4D2QQ433VXS5D0R","test-strategy-architect","Architect-level test strategy — allocating assertions across unit, integration, contract and end-to-end layers, designing for testability through dependency boundaries, fixture and data strategy, and the flake and coverage policies that keep a suite trustworthy. Use when defining how a codebase is tested.","https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo\u002Fblob\u002Fmain\u002Fskills\u002Fwebsite-architect\u002Ftesting-and-deployment-architect\u002Ftest-strategy-architect\u002FSKILL.md",[],[]]