[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79SWKF66DWBNN7SZ0G2W1R2":3,"skill-same:01M79SWKF66DWBNN7SZ0G2W1R2":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},"01M79SWKF66DWBNN7SZ0G2W1R2","desktop-distribution-architect",null,"Architect-level desktop distribution — code signing and notarization, installer and package formats per OS, auto-update channels with staged rollout and rollback, and the enterprise deployment requirements (silent install, MDM, versions) that decide whether an app can be sold. Use when shipping desktop software.","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\u002Fdelivery-architect\u002Fdesktop-distribution-architect\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: desktop-distribution-architect\ndescription: Architect-level desktop distribution — code signing and notarization, installer and package formats per OS, auto-update channels with staged rollout and rollback, and the enterprise deployment requirements (silent install, MDM, versions) that decide whether an app can be sold. Use when shipping desktop software.\nlicense: MIT\ncompatibility: Any desktop stack; Authenticode, Apple notarization, MSIX\u002FDMG\u002FAppImage\u002FFlatpak\nmetadata:\n  crusor-domain: desktop-architect\n  crusor-path: desktop-architect\u002Fdelivery-architect\u002Fdesktop-distribution-architect\n  crusor-origin: original\n  crusor-sources: \"developer.apple.com\u002Fdocumentation\u002Fsecurity\u002Fnotarizing; learn.microsoft.com\u002Fwindows\u002Fmsix; electron.build; v2.tauri.app\u002Fdistribute\"\n  crusor-triggers: \"signing, sign the app, code signing, certificate, notarization, installer, msix, dmg, appimage, auto update, staged rollout, silent install, mdm, mac app, sign our\"\n  crusor-verified-on: \"2026-10-30\"\n---\n\n# Desktop Distribution Architect\n\nDesktop distribution is **the part users meet before they trust you**. An unsigned\nbuild, a SmartScreen warning, or an update that bricks installs ends the product\nfaster than any bug.\n\n## When to use\n\n- Preparing installers, signing, notarization, or auto-update.\n- Shipping to enterprises (silent install, MDM, version pinning).\n- Users report \"unknown publisher\" or blocked installs.\n\n## When NOT to use\n\n- Internal tools run from source — but sign anyway if anyone outside the team\n  installs it.\n\n## Decision 1 — Signing identity\n\n| Platform | Requirement |\n|---|---|\n| macOS | Developer ID + hardened runtime + notarization + stapling |\n| Windows | Authenticode (EV recommended for SmartScreen reputation) |\n| Linux | distro signing; Flatpak\u002FAppImage signatures |\n\n- Certificates in a managed secret store with HSM\u002Fcloud signing; never on a\n  laptop.\n- Rotation and expiry monitored — an expired cert stops all releases.\n- Sign **the installer and the binaries**, and verify signatures in CI.\n\n## Decision 2 — Package formats\n\n| OS | Format | Notes |\n|---|---|---|\n| macOS | DMG or PKG | PKG for MDM; DMG for direct download |\n| Windows | MSIX or EXE\u002FMSI | MSIX for clean install\u002Fupdate; EXE for broad compatibility |\n| Linux | AppImage, deb\u002Frpm, Flatpak, Snap | pick per target distro; Flatpak for sandboxed distribution |\n\n- One canonical download per platform; do not make users choose between five\n  artefacts.\n- Universal\u002Farm64+x64 builds decided explicitly; Rosetta is a bridge, not a plan.\n- Include uninstall path and data location in the docs.\n\n## Decision 3 — Auto-update\n\n- Signed manifests and signed packages; HTTPS only; the update feed is part of\n  the attack surface.\n- Channels: stable \u002F beta \u002F internal — with separate feeds and separate signing\n  keys.\n- Staged rollout percentages with automatic halt on crash-rate regression.\n- Delta updates where supported to keep downloads small.\n- Rollback: keep the previous version installable, and make downgrade possible\n  on request.\n\n## Decision 4 — Enterprise requirements\n\n- Silent install flags documented; MSI\u002FPKG\u002FMSIX for MDM deployment.\n- Version pinning and a documented support window per major version.\n- No mandatory online activation that breaks air-gapped installs, unless the\n  product is explicitly cloud-tied.\n- Proxy support, offline licensing, and centralised configuration for managed\n  fleets.\n- Security questionnaires: an SBOM and a signing policy make them survivable.\n\n## Decision 5 — Release operations\n\n- CI builds all platforms from one commit; artefacts archived with hashes.\n- Release notes per version; update channel notes for breaking changes.\n- Crash and update telemetry by version; adoption visible within days.\n- A \"can we ship a fix in an hour?\" drill: if not, the pipeline is the problem.\n\n## Failure modes at scale\n\n- Unsigned beta handed to a customer, then SmartScreen blocks the paid release.\n- Notarization step skipped after a certificate rotation.\n- Auto-update feed unauthenticated — update hijack is RCE.\n- Each platform's installer built by hand on one engineer's machine.\n- Enterprise customer cannot deploy silently, so the deal dies in IT review.\n\n## Verification receipts\n\n1. Signature verification on each artefact (`codesign -dv`, `signtool verify`).\n2. Clean-machine install, launch, update, uninstall cycle per OS.\n3. Staged rollout with a halt threshold demonstrated.\n4. Silent install tested in a clean VM with the MDM command.\n5. Certificate expiry and rotation dates tracked with alerts.\n","# Desktop Distribution Architect\n\nDesktop distribution is **the part users meet before they trust you**. An unsigned\nbuild, a SmartScreen warning, or an update that bricks installs ends the product\nfaster than any bug.\n\n## When to use\n\n- Preparing installers, signing, notarization, or auto-update.\n- Shipping to enterprises (silent install, MDM, version pinning).\n- Users report \"unknown publisher\" or blocked installs.\n\n## When NOT to use\n\n- Internal tools run from source — but sign anyway if anyone outside the team\n  installs it.\n\n## Decision 1 — Signing identity\n\n| Platform | Requirement |\n|---|---|\n| macOS | Developer ID + hardened runtime + notarization + stapling |\n| Windows | Authenticode (EV recommended for SmartScreen reputation) |\n| Linux | distro signing; Flatpak\u002FAppImage signatures |\n\n- Certificates in a managed secret store with HSM\u002Fcloud signing; never on a\n  laptop.\n- Rotation and expiry monitored — an expired cert stops all releases.\n- Sign **the installer and the binaries**, and verify signatures in CI.\n\n## Decision 2 — Package formats\n\n| OS | Format | Notes |\n|---|---|---|\n| macOS | DMG or PKG | PKG for MDM; DMG for direct download |\n| Windows | MSIX or EXE\u002FMSI | MSIX for clean install\u002Fupdate; EXE for broad compatibility |\n| Linux | AppImage, deb\u002Frpm, Flatpak, Snap | pick per target distro; Flatpak for sandboxed distribution |\n\n- One canonical download per platform; do not make users choose between five\n  artefacts.\n- Universal\u002Farm64+x64 builds decided explicitly; Rosetta is a bridge, not a plan.\n- Include uninstall path and data location in the docs.\n\n## Decision 3 — Auto-update\n\n- Signed manifests and signed packages; HTTPS only; the update feed is part of\n  the attack surface.\n- Channels: stable \u002F beta \u002F internal — with separate feeds and separate signing\n  keys.\n- Staged rollout percentages with automatic halt on crash-rate regression.\n- Delta updates where supported to keep downloads small.\n- Rollback: keep the previous version installable, and make downgrade possible\n  on request.\n\n## Decision 4 — Enterprise requirements\n\n- Silent install flags documented; MSI\u002FPKG\u002FMSIX for MDM deployment.\n- Version pinning and a documented support window per major version.\n- No mandatory online activation that breaks air-gapped installs, unless the\n  product is explicitly cloud-tied.\n- Proxy support, offline licensing, and centralised configuration for managed\n  fleets.\n- Security questionnaires: an SBOM and a signing policy make them survivable.\n\n## Decision 5 — Release operations\n\n- CI builds all platforms from one commit; artefacts archived with hashes.\n- Release notes per version; update channel notes for breaking changes.\n- Crash and update telemetry by version; adoption visible within days.\n- A \"can we ship a fix in an hour?\" drill: if not, the pipeline is the problem.\n\n## Failure modes at scale\n\n- Unsigned beta handed to a customer, then SmartScreen blocks the paid release.\n- Notarization step skipped after a certificate rotation.\n- Auto-update feed unauthenticated — update hijack is RCE.\n- Each platform's installer built by hand on one engineer's machine.\n- Enterprise customer cannot deploy silently, so the deal dies in IT review.\n\n## Verification receipts\n\n1. Signature verification on each artefact (`codesign -dv`, `signtool verify`).\n2. Clean-machine install, launch, update, uninstall cycle per OS.\n3. Staged rollout with a halt threshold demonstrated.\n4. Silent install tested in a clean VM with the MDM command.\n5. Certificate expiry and rotation dates tracked with alerts.\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\u002Fdelivery-architect\u002Fdesktop-distribution-architect","desktop-architect","original","developer.apple.com\u002Fdocumentation\u002Fsecurity\u002Fnotarizing; learn.microsoft.com\u002Fwindows\u002Fmsix; electron.build; v2.tauri.app\u002Fdistribute","signing, sign the app, code signing, certificate, notarization, installer, msix, dmg, appimage, auto update, staged rollout, silent install, mdm, mac app, sign our","2026-10-30","Any desktop stack; Authenticode, Apple notarization, MSIX\u002FDMG\u002FAppImage\u002FFlatpak","main","8fa4e240be65b98472c9b2d3a505ade2aea1a5c6","skills\u002Fdesktop-architect\u002Fdelivery-architect\u002Fdesktop-distribution-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 desktop-distribution-architect",{"tool":45,"command":46},"bunx","bunx skills add SriAkhilSJ\u002FPulseAIRepo --skill desktop-distribution-architect",{"tool":48,"command":49},"pnpm","pnpm dlx skills add SriAkhilSJ\u002FPulseAIRepo --skill desktop-distribution-architect","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo\u002Fblob\u002Fmain\u002Fskills\u002Fdesktop-architect\u002Fdelivery-architect\u002Fdesktop-distribution-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",[],[]]