[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7AMTTPHPAVD2YAPABQJ7X78":3,"skill-same:01M7AMTTPHPAVD2YAPABQJ7X78":48},{"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":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":29,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M7AMTTPHPAVD2YAPABQJ7X78","desktop-packaging-security-and-testing",null,"Use when shipping a desktop app: macOS code signing, the Hardened Runtime, notarization and stapling, the four macOS distribution channels including the Mac App Store; the Linux packaging matrix (Flatpak, Snap, AppImage, distro packages); auto-update (Sparkle, Squirrel, Flatpak); sandboxing and privacy (TCC, entitlements, the App Sandbox, Keychain and secrets, XDG portals, supply-chain and dependency risk); and the desktop testing pyramid, tools, and CI.","the-vibey-project\u002Fvibey","the-vibey-project","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F329298758?v=4","01M7AJHGZ9722CTJ4JNQZVRH0Q","the vibey project","01M7AJHGZVMG2K7TGXQ6XFHVG3",5,"MIT","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fdesktop-apps-macos-linux\u002Fskills\u002Fdesktop-packaging-security-and-testing\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: desktop-packaging-security-and-testing\ndescription: \"Use when shipping a desktop app: macOS code signing, the Hardened Runtime, notarization and stapling, the four macOS distribution channels including the Mac App Store; the Linux packaging matrix (Flatpak, Snap, AppImage, distro packages); auto-update (Sparkle, Squirrel, Flatpak); sandboxing and privacy (TCC, entitlements, the App Sandbox, Keychain and secrets, XDG portals, supply-chain and dependency risk); and the desktop testing pyramid, tools, and CI.\"\n---\n\n# Desktop Apps (macOS & Linux): Packaging, Auto-Update, Sandboxing, and Testing\n\n> **Part 4 of 5** of the *Desktop Application Programming — macOS & Linux* reference (plugin `desktop-apps-macos-linux`), covering §10–§13. Sibling skills: `desktop-macos-platform` (§0–§3), `desktop-linux-platform` (§4–§6), `desktop-cross-platform-and-architecture` (§7–§9), `desktop-reference` (§14–§20). Section numbers are shared across the set; a reference written as §N → `skill` points into that sibling skill.\n>\n> **Currency:** Verified August 2026. See §18 → `desktop-reference` for the currency snapshot and what goes stale first.\n\n> **How to read this.** Reference, not tutorial. Sections are independent. Three markers:\n> - **[UNIVERSAL]** — true of desktop software regardless of platform or toolkit.\n> - **[PLATFORM]** — specific to macOS or a particular Linux stack. Verify against current docs.\n> - **[CONTESTED]** — competent engineers disagree. Both cases given; don't adjudicate for the reader.\n>\n> **⚠️ GOTCHA** boxes mark the failure modes that actually cost people days.\n>\n> **The single most important framing in this document:** macOS is *one* platform with\n> *one* vendor, *one* HIG, and *one* blessed path. Linux is *not a platform* — it is a\n> family of overlapping conventions (freedesktop specs), two dominant toolkits, two\n> display protocols, three packaging formats, and a dozen desktop environments. Advice\n> that treats them symmetrically is wrong. Almost every difficulty in cross-platform\n> desktop work traces back to this asymmetry.\n\n---\n\n## §10. Packaging and Distribution\n\n### 10.1 macOS: the four distribution channels\n\n| Channel | Signing | Sandbox | Notarization | Update mechanism | Trade-off |\n|---|---|---|---|---|---|\n| **Mac App Store** | Apple Distribution cert | **Required** | N\u002FA (review instead) | App Store | Discovery + trust; 15–30% cut; review latency; sandbox limits |\n| **Developer ID (direct)** | Developer ID Application | Optional | **Required** | Sparkle or your own | Full capability, your prices, you own support |\n| **Both** | Two builds | Differs | — | — | Common for pro apps; maintain two entitlement sets |\n| **Homebrew Cask** | Developer ID | Optional | Required | `brew upgrade` | Great for developer tools; not a discovery channel for consumers |\n\n**The Developer ID pipeline, precisely:**\n\n```bash\n# 1. Sign everything inside-out: frameworks, helpers, XPC services, then the app.\n#    --options=runtime enables the Hardened Runtime — REQUIRED for notarization.\ncodesign --force --timestamp --options=runtime \\\n  --sign \"Developer ID Application: Example Inc (TEAMID)\" \\\n  MyApp.app\u002FContents\u002FFrameworks\u002F*.framework\n\ncodesign --force --timestamp --options=runtime \\\n  --entitlements MyApp.entitlements \\\n  --sign \"Developer ID Application: Example Inc (TEAMID)\" \\\n  MyApp.app\n\n# 2. Verify BEFORE you ship, not after a user's bug report.\ncodesign --verify --deep --strict --verbose=2 MyApp.app\nspctl --assess --type exec --verbose=4 MyApp.app\n\n# 3. Notarize. Use an App Store Connect API key in CI — it doesn't expire\n#    and doesn't trip 2FA, unlike an app-specific password.\nditto -c -k --keepParent MyApp.app MyApp.zip\nxcrun notarytool submit MyApp.zip \\\n  --key AuthKey_XXXX.p8 --key-id XXXX --issuer \u003Cissuer-uuid> --wait\n\n# 4. Staple the ticket so Gatekeeper works OFFLINE.\nxcrun stapler staple MyApp.app\nxcrun stapler validate MyApp.app\n\n# 5. Ship a DMG or PKG — and notarize + staple THAT too, not just the .app.\n```\n\n> **⚠️ GOTCHA — notarization failures are almost always one of five things:**\n> (1) Hardened Runtime not enabled on *every* executable, including helpers and embedded\n> binaries in `Contents\u002FMacOS\u002F` subdirectories; (2) a nested binary that wasn't signed;\n> (3) a missing `--timestamp` (signatures without a secure timestamp expire with the\n> certificate); (4) a JIT or unsigned-memory requirement without\n> `com.apple.security.cs.allow-jit` \u002F `allow-unsigned-executable-memory` (this hits every\n> Electron, JVM, Python, and .NET app); (5) an entitlement you're not authorized for.\n> The notarization log URL Apple emails you names the exact file — read it rather than\n> guessing.\n\n> **⚠️ GOTCHA — app translocation.** Gatekeeper runs quarantined apps from a randomized,\n> read-only path on first launch. Anything that assumes it can write next to itself, or\n> that reads its own path to find resources outside the bundle, breaks in a way that never\n> reproduces in development. Fix: ship in a DMG that instructs dragging to \u002FApplications,\n> and never write beside the bundle.\n\n**Entitlements** (`MyApp.entitlements`), the ones that matter:\n```xml\n\u003Ckey>com.apple.security.app-sandbox\u003C\u002Fkey>\u003Ctrue\u002F>              \u003C!-- required for MAS -->\n\u003Ckey>com.apple.security.files.user-selected.read-write\u003C\u002Fkey>\u003Ctrue\u002F>\n\u003Ckey>com.apple.security.files.bookmarks.app-scope\u003C\u002Fkey>\u003Ctrue\u002F> \u003C!-- persist file access -->\n\u003Ckey>com.apple.security.network.client\u003C\u002Fkey>\u003Ctrue\u002F>\n\u003Ckey>com.apple.security.device.camera\u003C\u002Fkey>\u003Ctrue\u002F>\n\u003Ckey>com.apple.security.cs.allow-jit\u003C\u002Fkey>\u003Ctrue\u002F>              \u003C!-- Electron\u002FJVM\u002FJIT -->\n\u003Ckey>com.apple.security.temporary-exception.files.home-relative-path.read-write\u003C\u002Fkey>\n```\n**Security bookmarks are the key sandbox concept**: when the user picks a file, you get\naccess to *that file* for *this launch*. To keep access across launches, create a\n**security-scoped bookmark**, persist it, and resolve it later with\n`startAccessingSecurityScopedResource()` \u002F `stopAccessing…` (balanced — leaking these\nexhausts a limited resource).\n\n### 10.2 Linux: the packaging matrix\n\n| Format | Sandbox | Updates | Store | Distro reach | Best for |\n|---|---|---|---|---|---|\n| **Flatpak** | Bubblewrap + namespaces + portals | Delta via OSTree | **Flathub** (community-governed, self-hostable remotes) | Universal; default on Fedora, Mint, elementary, Steam Deck | **The default recommendation for GUI apps** |\n| **Snap** | AppArmor + seccomp | Automatic, transactional, rollback | Snap Store (**Canonical-only, no alternate remotes**) | Ubuntu-centric | Ubuntu targeting; CLI tools; servers\u002FIoT; daemons |\n| **AppImage** | **None** | **None built in** | AppImageHub (community directory) | Anywhere with FUSE | Portable single-file distribution, no-root environments, testing a version |\n| **.deb \u002F .rpm** | None | Distro repo | Distro archives | Per-distro | System-level software; when a distro packages you |\n| **AUR \u002F Homebrew \u002F nix** | Varies | Varies | — | Per-ecosystem | Developer tools |\n\n**[CONTESTED] but with a clear centre of gravity:** the 2026 consensus in most practitioner\ncomparisons is **Flatpak+Flathub as the primary universal format for desktop GUI apps**\n(largest catalogue — Flathub passed ~3,200 apps and 433M downloads in 2025 and continues\ngrowing; strongest sandboxing story; shared runtimes save disk; OSTree deltas save\nbandwidth), **Snap where you're Ubuntu-aligned or shipping daemons\u002FCLI**, and **AppImage\nfor portability**. The recurring criticisms are also real: universal packages start slower\nthan native ones (Snap notably), theming integration is imperfect, runtimes are large on\nfirst install, and **neither Flathub nor the Snap Store vets aggressively** — both have\nhosted fake crypto wallets and other malware. Verified-publisher badges exist for a reason;\ntell your users to check them.\n\n```yaml\n# com.example.MyApp.yaml — a Flatpak manifest\napp-id: com.example.MyApp\nruntime: org.gnome.Platform\nruntime-version: '48'\nsdk: org.gnome.Sdk\ncommand: myapp\nfinish-args:\n  - --socket=wayland\n  - --socket=fallback-x11          # NOT --socket=x11; fallback prefers Wayland\n  - --device=dri                   # GPU\n  - --share=network\n  # NOTE: no --filesystem=home. Use the FileChooser portal instead — that is\n  # the entire point, and Flathub will flag broad filesystem access.\n  - --talk-name=org.freedesktop.secrets   # keyring, if you need it\nmodules:\n  - name: myapp\n    buildsystem: meson\n    sources:\n      - type: archive\n        url: https:\u002F\u002Fexample.com\u002Fmyapp-1.2.0.tar.xz\n        sha256: \u003Chash>\n```\n\n> **⚠️ GOTCHA — `--filesystem=home` is a sandbox escape hatch, not a solution.** It's the\n> first thing developers reach for and the first thing reviewers push back on. If your app\n> needs \"access to files,\" the answer is the FileChooser portal, which grants access to\n> exactly what the user picked, transparently, through the toolkit's normal file dialog.\n\n**Reduce your distro-support burden**: ship one Flatpak, tell everyone else to use it, and\nlet volunteers maintain AUR\u002Fnixpkgs. Trying to build and test `.deb` and `.rpm` across six\ndistro versions is a full-time job that adds no user value in 2026.\n\n---\n\n## §11. Auto-Update\n\n**[UNIVERSAL] Requirements for any desktop updater**, identical in spirit to firmware OTA:\nsigned, atomic, resumable, rollback-capable, and staged. A half-applied update that leaves\nan unlaunchable app is the worst possible outcome — worse than never updating.\n\n| Platform \u002F stack | Mechanism | Notes |\n|---|---|---|\n| macOS direct | **Sparkle 2** | The de facto standard. EdDSA-signed appcast (RSS\u002FXML), delta updates, atomic installs, **works with sandboxed apps** (a Sparkle 2 feature), fully rebrandable, works with any toolkit (Cocoa, SwiftUI, Qt, .NET). |\n| macOS MAS | App Store | You don't control timing. |\n| Electron | `electron-updater` \u002F Squirrel.Mac | Mature; test the update flow in CI, not just the app. |\n| Tauri | Built-in updater plugin | Signed manifests. |\n| Flatpak | `flatpak update` \u002F GNOME Software | OSTree deltas; you just push to the remote. |\n| Snap | Automatic, transactional | You get rollback for free; you also lose control of update timing. |\n| Distro packages | Distro's updater | Slowest path to users. |\n| Cross-platform .NET | WinSparkle\u002FSparkle wrappers (e.g. UpSparkle) | Thin wrappers over the native frameworks. |\n\n**Ecosystem note (2026):** the third-party Mac update-tracking tool **MacUpdater was\ndiscontinued on 1 January 2026** (final free build 3.5.0; its database is scheduled to go\ndark at the end of 2026), pushing users toward Homebrew, `mas-cli`, and Sparkle-aware tools\nlike Latest and Updatest. **Practical implication:** shipping a working Sparkle appcast is\nnow more important, because the safety net of third-party trackers is gone.\n\n**Rollout discipline [UNIVERSAL]:** canary → percentage → full, with a kill switch. Ship a\ncrash reporter *before* you ship auto-update, so you can tell whether a release is bad\nwithin hours instead of learning it from reviews.\n\n---\n\n## §12. Security, Sandboxing, and Privacy\n\n### 12.1 macOS: the three separate systems people conflate\n\nThey are independent, and you need all three straight:\n\n1. **Code signing** — proves *who* built it. Developer ID or Apple Distribution certificate.\n2. **Entitlements** — declare *what it may do*. Sandbox on\u002Foff plus each specific capability.\n3. **Notarization** — proves *Apple scanned it* for malware. Required for anything\n   distributed outside the App Store since macOS 10.15. **Requires Hardened Runtime.**\n\nPlus, at runtime:\n- **Hardened Runtime** — blocks code injection, DYLD hijacking, and unsigned executable\n  memory. Mandatory for notarization. This is what breaks JIT-based runtimes unless you\n  add the corresponding entitlement.\n- **App Sandbox** — kernel-enforced confinement to your container. **Required for the Mac\n  App Store; optional (and recommended) outside it.**\n- **TCC (Transparency, Consent, Control)** — the per-resource consent database (camera,\n  mic, screen recording, Documents\u002FDesktop\u002FDownloads, Contacts, Automation…). Independent\n  of the sandbox: **a non-sandboxed app is still subject to TCC.**\n- **Gatekeeper** — checks signature + notarization ticket at first launch, tracks\n  provenance of files written by downloaded software, and randomizes launch paths when\n  necessary.\n\n> **⚠️ GOTCHA — enabling the sandbox late is a project, not a checkbox.** It relocates\n> your data directory, revokes filesystem access outside the container, breaks hardcoded\n> paths, breaks direct access to other apps' data, and may break your update mechanism.\n> Decide sandbox\u002Fno-sandbox before v1 and develop with it on.\n\n### 12.2 macOS secrets\n\nUse the **Keychain** (`kSecClass...` \u002F the Security framework) for credentials and tokens.\nNot UserDefaults, not a file in Application Support, not obfuscated in the binary. For\nhigher-value secrets, `kSecAttrAccessibleWhenUnlockedThisDeviceOnly` and the Secure\nEnclave (via `SecKeyCreateRandomKey` with `kSecAttrTokenIDSecureEnclave`).\n\n### 12.3 Linux: portals are the model\n\n**XDG Desktop Portals** are the Linux answer to entitlements\u002FTCC: a set of D-Bus\ninterfaces at `org.freedesktop.portal.Desktop` that mediate access to resources outside an\napp's sandbox, with a user-controlled permission system and per-desktop backends\n(`xdg-desktop-portal-gnome`, `-kde`, `-wlr`, and newer generic backends for COSMIC\u002Fniri).\n\n**[UNIVERSAL for Linux] Use portals even if you are not sandboxed.** The portal docs say\nthis explicitly, and the reasons are practical:\n- Free desktop integration: the FileChooser portal gives you *the user's own* file dialog.\n- Some capabilities are **only** available via portals — screen capture and screenshots on\n  Wayland go through the ScreenCast\u002FScreenshot portals; some desktops expose no other path.\n- Your app works identically packaged and unpackaged.\n\nKey portals: FileChooser, OpenURI, ScreenCast (v6), Screenshot, RemoteDesktop, Camera,\nPrint, Notification, Settings (theme\u002Faccent\u002Fcolor-scheme), Inhibit (prevent sleep),\nGlobalShortcuts, Background\u002FAutostart, Secret, Account, Location, Clipboard, Trash.\n\nGTK3\u002FGTK4 and Qt5\u002FQt6 route through portals **transparently** for common operations —\nwhich is why \"use the toolkit's file dialog\" is usually the whole answer.\n\n```bash\n# Debugging the portal stack — the checklist that resolves most \"file picker won't\n# open\" and \"OBS can't see my screen\" reports:\necho $XDG_SESSION_TYPE $XDG_CURRENT_DESKTOP\nsystemctl --user status xdg-desktop-portal\nsystemctl --user status pipewire wireplumber\njournalctl --user -u xdg-desktop-portal -f\n# Most common cause: multiple portal backends installed, wrong one selected for\n# an interface. The fix is installing the CORRECT backend, not more backends.\n```\n\n**Linux secrets**: the **Secret Service** API (`libsecret`) → GNOME Keyring or KWallet. In\nFlatpak, request `--talk-name=org.freedesktop.secrets` or use the Secret portal.\n\n### 12.4 Supply chain and dependency risk [UNIVERSAL]\n\nDesktop apps ship a full dependency tree to end-user machines and often run with the\nuser's full privileges.\n- **Pin and audit dependencies**; generate an **SBOM** (SPDX\u002FCycloneDX) per release.\n- **Sign everything** with keys held in an HSM or a hosted signing service — never a key\n  file on a laptop or in a repo.\n- **Keep the runtime current.** An Electron app two majors behind ships known Chromium\n  RCEs to your users. A Flatpak on an EOL runtime is the same problem.\n- **Reproducible builds** where you can; at minimum, build in a pinned container so\n  \"it built on my machine\" isn't part of your release process.\n- The **EU Cyber Resilience Act** applies to desktop software sold into the EU: vulnerability\n  and incident **reporting obligations begin 11 September 2026**, full application\n  11 December 2027. If you sell a desktop app in Europe, you need an SBOM, a monitored\n  vulnerability intake, and a reporting runbook — this is not a firmware-only concern.\n\n---\n\n## §13. Testing, Debugging, and CI\n\n### 13.1 The testing pyramid for desktop\n\n```\n        ▲  Crash + telemetry from real users     ← the ultimate integration test\n       ╱ ╲ Manual exploratory on real hardware\u002FDEs\n      ╱   ╲ UI automation (XCUITest \u002F dogtail \u002F Squish \u002F Playwright)\n     ╱     ╲ Integration: real window, real event loop, fake I\u002FO\n    ╱       ╲ Unit tests of domain + view models (no UI)   ← the bulk\n   ╱_________╲ Static analysis + compiler warnings\n```\n**[UNIVERSAL] UI tests are slow, flaky, and expensive — so keep the UI thin.** If your view\nmodels are pure and testable (§8.1 → `desktop-cross-platform-and-architecture`), you need very few UI tests: enough to verify wiring\nand the two or three critical user journeys, not to test logic.\n\n### 13.2 Tools\n\n| Need | macOS | Linux |\n|---|---|---|\n| Unit tests | **Swift Testing** (`@Test`\u002F`#expect`), XCTest | GTest\u002FCatch2, pytest, `cargo test`, QTest |\n| UI automation | **XCUITest**, Accessibility Inspector | **dogtail** (AT-SPI), Squish, `wlheadless`\u002F`weston --backend=headless` for CI |\n| Web-shell UI tests | Playwright\u002FWebdriverIO against Electron | same |\n| Profiling (CPU\u002Falloc\u002Ftime) | **Instruments** (Time Profiler, Allocations, Leaks, Metal, Energy Log, SwiftUI template) | **sysprof**, `perf`, Hotspot, Valgrind\u002FMassif, heaptrack |\n| Graphics debugging | Metal debugger, Quartz Debug | RenderDoc, `GTK_DEBUG=interactive`, `apitrace` |\n| Widget inspection | Xcode View Debugger | **GTK Inspector** (`GTK_DEBUG=interactive`), **Qt's `GammaRay`** |\n| Memory errors | ASan\u002FTSan\u002FUBSan via Xcode schemes | ASan\u002FTSan\u002FUBSan, Valgrind |\n| Leaks | `leaks`, Instruments Leaks, Xcode Memory Graph | heaptrack, `G_DEBUG=gc-friendly` + Valgrind |\n| Logging | **`os.Logger`** (unified logging; `log stream --predicate`) | `journalctl`, `G_MESSAGES_DEBUG=all`, `QT_LOGGING_RULES` |\n| Crash reports | `~\u002FLibrary\u002FLogs\u002FDiagnosticReports`, Xcode Organizer, Sentry\u002FCrashlytics | `coredumpctl`, ABRT, Sentry |\n| D-Bus tracing | — | `busctl monitor`, `dbus-monitor`, `d-feet` |\n\n**The two most underused tools**: on macOS, **Instruments' Time Profiler with \"Record\nWaiting Threads\"** turns \"the app hangs sometimes\" into a stack; on Linux,\n`GTK_DEBUG=interactive` gives you a live widget inspector with CSS editing in any GTK app,\nincluding ones you didn't write.\n\n### 13.3 CI for desktop apps\n\n```\npush\n ├─ lint + format (SwiftLint\u002FSwiftFormat; clang-format; clippy; eslint)\n ├─ unit tests: domain + view models ................ fast, every commit\n ├─ build all targets (macOS universal; Linux x86_64 + aarch64)\n ├─ ASan\u002FTSan run of the test suite (nightly)\n ├─ package: .app + notarize + staple + DMG | Flatpak build + lint\n ├─ SBOM + dependency CVE scan\n ├─ sign artifacts (HSM\u002Fhosted signing, never a laptop key)\n └─ nightly: UI smoke tests on real macOS + headless Wayland; update-flow test\n```\n\n**Platform-specific CI realities:**\n- **macOS builds require macOS runners.** Notarization requires network access and an App\n  Store Connect API key. GitHub-hosted macOS images change their default Xcode on a\n  schedule — **pin your Xcode version** (`sudo xcode-select -s \u002FApplications\u002FXcode_26.4.app`\n  or the setup-xcode action), or a runner-image update will break your build without a\n  commit from you.\n- **Linux GUI tests need a display.** Use a headless Wayland compositor (`weston\n  --backend=headless-backend.so`, `wlheadless-run`, or `cage`) or Xvfb for X11 paths.\n- **Test the update path in CI**, not just the app. A broken updater is unrecoverable\n  without asking users to reinstall manually.\n- **Test on the oldest OS you claim to support.** \"Deployment target macOS 13\" that has\n  only ever run on macOS 26 is a claim, not a fact.\n","# Desktop Apps (macOS & Linux): Packaging, Auto-Update, Sandboxing, and Testing\n\n> **Part 4 of 5** of the *Desktop Application Programming — macOS & Linux* reference (plugin `desktop-apps-macos-linux`), covering §10–§13. Sibling skills: `desktop-macos-platform` (§0–§3), `desktop-linux-platform` (§4–§6), `desktop-cross-platform-and-architecture` (§7–§9), `desktop-reference` (§14–§20). Section numbers are shared across the set; a reference written as §N → `skill` points into that sibling skill.\n>\n> **Currency:** Verified August 2026. See §18 → `desktop-reference` for the currency snapshot and what goes stale first.\n\n> **How to read this.** Reference, not tutorial. Sections are independent. Three markers:\n> - **[UNIVERSAL]** — true of desktop software regardless of platform or toolkit.\n> - **[PLATFORM]** — specific to macOS or a particular Linux stack. Verify against current docs.\n> - **[CONTESTED]** — competent engineers disagree. Both cases given; don't adjudicate for the reader.\n>\n> **⚠️ GOTCHA** boxes mark the failure modes that actually cost people days.\n>\n> **The single most important framing in this document:** macOS is *one* platform with\n> *one* vendor, *one* HIG, and *one* blessed path. Linux is *not a platform* — it is a\n> family of overlapping conventions (freedesktop specs), two dominant toolkits, two\n> display protocols, three packaging formats, and a dozen desktop environments. Advice\n> that treats them symmetrically is wrong. Almost every difficulty in cross-platform\n> desktop work traces back to this asymmetry.\n\n---\n\n## §10. Packaging and Distribution\n\n### 10.1 macOS: the four distribution channels\n\n| Channel | Signing | Sandbox | Notarization | Update mechanism | Trade-off |\n|---|---|---|---|---|---|\n| **Mac App Store** | Apple Distribution cert | **Required** | N\u002FA (review instead) | App Store | Discovery + trust; 15–30% cut; review latency; sandbox limits |\n| **Developer ID (direct)** | Developer ID Application | Optional | **Required** | Sparkle or your own | Full capability, your prices, you own support |\n| **Both** | Two builds | Differs | — | — | Common for pro apps; maintain two entitlement sets |\n| **Homebrew Cask** | Developer ID | Optional | Required | `brew upgrade` | Great for developer tools; not a discovery channel for consumers |\n\n**The Developer ID pipeline, precisely:**\n\n```bash\n# 1. Sign everything inside-out: frameworks, helpers, XPC services, then the app.\n#    --options=runtime enables the Hardened Runtime — REQUIRED for notarization.\ncodesign --force --timestamp --options=runtime \\\n  --sign \"Developer ID Application: Example Inc (TEAMID)\" \\\n  MyApp.app\u002FContents\u002FFrameworks\u002F*.framework\n\ncodesign --force --timestamp --options=runtime \\\n  --entitlements MyApp.entitlements \\\n  --sign \"Developer ID Application: Example Inc (TEAMID)\" \\\n  MyApp.app\n\n# 2. Verify BEFORE you ship, not after a user's bug report.\ncodesign --verify --deep --strict --verbose=2 MyApp.app\nspctl --assess --type exec --verbose=4 MyApp.app\n\n# 3. Notarize. Use an App Store Connect API key in CI — it doesn't expire\n#    and doesn't trip 2FA, unlike an app-specific password.\nditto -c -k --keepParent MyApp.app MyApp.zip\nxcrun notarytool submit MyApp.zip \\\n  --key AuthKey_XXXX.p8 --key-id XXXX --issuer \u003Cissuer-uuid> --wait\n\n# 4. Staple the ticket so Gatekeeper works OFFLINE.\nxcrun stapler staple MyApp.app\nxcrun stapler validate MyApp.app\n\n# 5. Ship a DMG or PKG — and notarize + staple THAT too, not just the .app.\n```\n\n> **⚠️ GOTCHA — notarization failures are almost always one of five things:**\n> (1) Hardened Runtime not enabled on *every* executable, including helpers and embedded\n> binaries in `Contents\u002FMacOS\u002F` subdirectories; (2) a nested binary that wasn't signed;\n> (3) a missing `--timestamp` (signatures without a secure timestamp expire with the\n> certificate); (4) a JIT or unsigned-memory requirement without\n> `com.apple.security.cs.allow-jit` \u002F `allow-unsigned-executable-memory` (this hits every\n> Electron, JVM, Python, and .NET app); (5) an entitlement you're not authorized for.\n> The notarization log URL Apple emails you names the exact file — read it rather than\n> guessing.\n\n> **⚠️ GOTCHA — app translocation.** Gatekeeper runs quarantined apps from a randomized,\n> read-only path on first launch. Anything that assumes it can write next to itself, or\n> that reads its own path to find resources outside the bundle, breaks in a way that never\n> reproduces in development. Fix: ship in a DMG that instructs dragging to \u002FApplications,\n> and never write beside the bundle.\n\n**Entitlements** (`MyApp.entitlements`), the ones that matter:\n```xml\n\u003Ckey>com.apple.security.app-sandbox\u003C\u002Fkey>\u003Ctrue\u002F>              \u003C!-- required for MAS -->\n\u003Ckey>com.apple.security.files.user-selected.read-write\u003C\u002Fkey>\u003Ctrue\u002F>\n\u003Ckey>com.apple.security.files.bookmarks.app-scope\u003C\u002Fkey>\u003Ctrue\u002F> \u003C!-- persist file access -->\n\u003Ckey>com.apple.security.network.client\u003C\u002Fkey>\u003Ctrue\u002F>\n\u003Ckey>com.apple.security.device.camera\u003C\u002Fkey>\u003Ctrue\u002F>\n\u003Ckey>com.apple.security.cs.allow-jit\u003C\u002Fkey>\u003Ctrue\u002F>              \u003C!-- Electron\u002FJVM\u002FJIT -->\n\u003Ckey>com.apple.security.temporary-exception.files.home-relative-path.read-write\u003C\u002Fkey>\n```\n**Security bookmarks are the key sandbox concept**: when the user picks a file, you get\naccess to *that file* for *this launch*. To keep access across launches, create a\n**security-scoped bookmark**, persist it, and resolve it later with\n`startAccessingSecurityScopedResource()` \u002F `stopAccessing…` (balanced — leaking these\nexhausts a limited resource).\n\n### 10.2 Linux: the packaging matrix\n\n| Format | Sandbox | Updates | Store | Distro reach | Best for |\n|---|---|---|---|---|---|\n| **Flatpak** | Bubblewrap + namespaces + portals | Delta via OSTree | **Flathub** (community-governed, self-hostable remotes) | Universal; default on Fedora, Mint, elementary, Steam Deck | **The default recommendation for GUI apps** |\n| **Snap** | AppArmor + seccomp | Automatic, transactional, rollback | Snap Store (**Canonical-only, no alternate remotes**) | Ubuntu-centric | Ubuntu targeting; CLI tools; servers\u002FIoT; daemons |\n| **AppImage** | **None** | **None built in** | AppImageHub (community directory) | Anywhere with FUSE | Portable single-file distribution, no-root environments, testing a version |\n| **.deb \u002F .rpm** | None | Distro repo | Distro archives | Per-distro | System-level software; when a distro packages you |\n| **AUR \u002F Homebrew \u002F nix** | Varies | Varies | — | Per-ecosystem | Developer tools |\n\n**[CONTESTED] but with a clear centre of gravity:** the 2026 consensus in most practitioner\ncomparisons is **Flatpak+Flathub as the primary universal format for desktop GUI apps**\n(largest catalogue — Flathub passed ~3,200 apps and 433M downloads in 2025 and continues\ngrowing; strongest sandboxing story; shared runtimes save disk; OSTree deltas save\nbandwidth), **Snap where you're Ubuntu-aligned or shipping daemons\u002FCLI**, and **AppImage\nfor portability**. The recurring criticisms are also real: universal packages start slower\nthan native ones (Snap notably), theming integration is imperfect, runtimes are large on\nfirst install, and **neither Flathub nor the Snap Store vets aggressively** — both have\nhosted fake crypto wallets and other malware. Verified-publisher badges exist for a reason;\ntell your users to check them.\n\n```yaml\n# com.example.MyApp.yaml — a Flatpak manifest\napp-id: com.example.MyApp\nruntime: org.gnome.Platform\nruntime-version: '48'\nsdk: org.gnome.Sdk\ncommand: myapp\nfinish-args:\n  - --socket=wayland\n  - --socket=fallback-x11          # NOT --socket=x11; fallback prefers Wayland\n  - --device=dri                   # GPU\n  - --share=network\n  # NOTE: no --filesystem=home. Use the FileChooser portal instead — that is\n  # the entire point, and Flathub will flag broad filesystem access.\n  - --talk-name=org.freedesktop.secrets   # keyring, if you need it\nmodules:\n  - name: myapp\n    buildsystem: meson\n    sources:\n      - type: archive\n        url: https:\u002F\u002Fexample.com\u002Fmyapp-1.2.0.tar.xz\n        sha256: \u003Chash>\n```\n\n> **⚠️ GOTCHA — `--filesystem=home` is a sandbox escape hatch, not a solution.** It's the\n> first thing developers reach for and the first thing reviewers push back on. If your app\n> needs \"access to files,\" the answer is the FileChooser portal, which grants access to\n> exactly what the user picked, transparently, through the toolkit's normal file dialog.\n\n**Reduce your distro-support burden**: ship one Flatpak, tell everyone else to use it, and\nlet volunteers maintain AUR\u002Fnixpkgs. Trying to build and test `.deb` and `.rpm` across six\ndistro versions is a full-time job that adds no user value in 2026.\n\n---\n\n## §11. Auto-Update\n\n**[UNIVERSAL] Requirements for any desktop updater**, identical in spirit to firmware OTA:\nsigned, atomic, resumable, rollback-capable, and staged. A half-applied update that leaves\nan unlaunchable app is the worst possible outcome — worse than never updating.\n\n| Platform \u002F stack | Mechanism | Notes |\n|---|---|---|\n| macOS direct | **Sparkle 2** | The de facto standard. EdDSA-signed appcast (RSS\u002FXML), delta updates, atomic installs, **works with sandboxed apps** (a Sparkle 2 feature), fully rebrandable, works with any toolkit (Cocoa, SwiftUI, Qt, .NET). |\n| macOS MAS | App Store | You don't control timing. |\n| Electron | `electron-updater` \u002F Squirrel.Mac | Mature; test the update flow in CI, not just the app. |\n| Tauri | Built-in updater plugin | Signed manifests. |\n| Flatpak | `flatpak update` \u002F GNOME Software | OSTree deltas; you just push to the remote. |\n| Snap | Automatic, transactional | You get rollback for free; you also lose control of update timing. |\n| Distro packages | Distro's updater | Slowest path to users. |\n| Cross-platform .NET | WinSparkle\u002FSparkle wrappers (e.g. UpSparkle) | Thin wrappers over the native frameworks. |\n\n**Ecosystem note (2026):** the third-party Mac update-tracking tool **MacUpdater was\ndiscontinued on 1 January 2026** (final free build 3.5.0; its database is scheduled to go\ndark at the end of 2026), pushing users toward Homebrew, `mas-cli`, and Sparkle-aware tools\nlike Latest and Updatest. **Practical implication:** shipping a working Sparkle appcast is\nnow more important, because the safety net of third-party trackers is gone.\n\n**Rollout discipline [UNIVERSAL]:** canary → percentage → full, with a kill switch. Ship a\ncrash reporter *before* you ship auto-update, so you can tell whether a release is bad\nwithin hours instead of learning it from reviews.\n\n---\n\n## §12. Security, Sandboxing, and Privacy\n\n### 12.1 macOS: the three separate systems people conflate\n\nThey are independent, and you need all three straight:\n\n1. **Code signing** — proves *who* built it. Developer ID or Apple Distribution certificate.\n2. **Entitlements** — declare *what it may do*. Sandbox on\u002Foff plus each specific capability.\n3. **Notarization** — proves *Apple scanned it* for malware. Required for anything\n   distributed outside the App Store since macOS 10.15. **Requires Hardened Runtime.**\n\nPlus, at runtime:\n- **Hardened Runtime** — blocks code injection, DYLD hijacking, and unsigned executable\n  memory. Mandatory for notarization. This is what breaks JIT-based runtimes unless you\n  add the corresponding entitlement.\n- **App Sandbox** — kernel-enforced confinement to your container. **Required for the Mac\n  App Store; optional (and recommended) outside it.**\n- **TCC (Transparency, Consent, Control)** — the per-resource consent database (camera,\n  mic, screen recording, Documents\u002FDesktop\u002FDownloads, Contacts, Automation…). Independent\n  of the sandbox: **a non-sandboxed app is still subject to TCC.**\n- **Gatekeeper** — checks signature + notarization ticket at first launch, tracks\n  provenance of files written by downloaded software, and randomizes launch paths when\n  necessary.\n\n> **⚠️ GOTCHA — enabling the sandbox late is a project, not a checkbox.** It relocates\n> your data directory, revokes filesystem access outside the container, breaks hardcoded\n> paths, breaks direct access to other apps' data, and may break your update mechanism.\n> Decide sandbox\u002Fno-sandbox before v1 and develop with it on.\n\n### 12.2 macOS secrets\n\nUse the **Keychain** (`kSecClass...` \u002F the Security framework) for credentials and tokens.\nNot UserDefaults, not a file in Application Support, not obfuscated in the binary. For\nhigher-value secrets, `kSecAttrAccessibleWhenUnlockedThisDeviceOnly` and the Secure\nEnclave (via `SecKeyCreateRandomKey` with `kSecAttrTokenIDSecureEnclave`).\n\n### 12.3 Linux: portals are the model\n\n**XDG Desktop Portals** are the Linux answer to entitlements\u002FTCC: a set of D-Bus\ninterfaces at `org.freedesktop.portal.Desktop` that mediate access to resources outside an\napp's sandbox, with a user-controlled permission system and per-desktop backends\n(`xdg-desktop-portal-gnome`, `-kde`, `-wlr`, and newer generic backends for COSMIC\u002Fniri).\n\n**[UNIVERSAL for Linux] Use portals even if you are not sandboxed.** The portal docs say\nthis explicitly, and the reasons are practical:\n- Free desktop integration: the FileChooser portal gives you *the user's own* file dialog.\n- Some capabilities are **only** available via portals — screen capture and screenshots on\n  Wayland go through the ScreenCast\u002FScreenshot portals; some desktops expose no other path.\n- Your app works identically packaged and unpackaged.\n\nKey portals: FileChooser, OpenURI, ScreenCast (v6), Screenshot, RemoteDesktop, Camera,\nPrint, Notification, Settings (theme\u002Faccent\u002Fcolor-scheme), Inhibit (prevent sleep),\nGlobalShortcuts, Background\u002FAutostart, Secret, Account, Location, Clipboard, Trash.\n\nGTK3\u002FGTK4 and Qt5\u002FQt6 route through portals **transparently** for common operations —\nwhich is why \"use the toolkit's file dialog\" is usually the whole answer.\n\n```bash\n# Debugging the portal stack — the checklist that resolves most \"file picker won't\n# open\" and \"OBS can't see my screen\" reports:\necho $XDG_SESSION_TYPE $XDG_CURRENT_DESKTOP\nsystemctl --user status xdg-desktop-portal\nsystemctl --user status pipewire wireplumber\njournalctl --user -u xdg-desktop-portal -f\n# Most common cause: multiple portal backends installed, wrong one selected for\n# an interface. The fix is installing the CORRECT backend, not more backends.\n```\n\n**Linux secrets**: the **Secret Service** API (`libsecret`) → GNOME Keyring or KWallet. In\nFlatpak, request `--talk-name=org.freedesktop.secrets` or use the Secret portal.\n\n### 12.4 Supply chain and dependency risk [UNIVERSAL]\n\nDesktop apps ship a full dependency tree to end-user machines and often run with the\nuser's full privileges.\n- **Pin and audit dependencies**; generate an **SBOM** (SPDX\u002FCycloneDX) per release.\n- **Sign everything** with keys held in an HSM or a hosted signing service — never a key\n  file on a laptop or in a repo.\n- **Keep the runtime current.** An Electron app two majors behind ships known Chromium\n  RCEs to your users. A Flatpak on an EOL runtime is the same problem.\n- **Reproducible builds** where you can; at minimum, build in a pinned container so\n  \"it built on my machine\" isn't part of your release process.\n- The **EU Cyber Resilience Act** applies to desktop software sold into the EU: vulnerability\n  and incident **reporting obligations begin 11 September 2026**, full application\n  11 December 2027. If you sell a desktop app in Europe, you need an SBOM, a monitored\n  vulnerability intake, and a reporting runbook — this is not a firmware-only concern.\n\n---\n\n## §13. Testing, Debugging, and CI\n\n### 13.1 The testing pyramid for desktop\n\n```\n        ▲  Crash + telemetry from real users     ← the ultimate integration test\n       ╱ ╲ Manual exploratory on real hardware\u002FDEs\n      ╱   ╲ UI automation (XCUITest \u002F dogtail \u002F Squish \u002F Playwright)\n     ╱     ╲ Integration: real window, real event loop, fake I\u002FO\n    ╱       ╲ Unit tests of domain + view models (no UI)   ← the bulk\n   ╱_________╲ Static analysis + compiler warnings\n```\n**[UNIVERSAL] UI tests are slow, flaky, and expensive — so keep the UI thin.** If your view\nmodels are pure and testable (§8.1 → `desktop-cross-platform-and-architecture`), you need very few UI tests: enough to verify wiring\nand the two or three critical user journeys, not to test logic.\n\n### 13.2 Tools\n\n| Need | macOS | Linux |\n|---|---|---|\n| Unit tests | **Swift Testing** (`@Test`\u002F`#expect`), XCTest | GTest\u002FCatch2, pytest, `cargo test`, QTest |\n| UI automation | **XCUITest**, Accessibility Inspector | **dogtail** (AT-SPI), Squish, `wlheadless`\u002F`weston --backend=headless` for CI |\n| Web-shell UI tests | Playwright\u002FWebdriverIO against Electron | same |\n| Profiling (CPU\u002Falloc\u002Ftime) | **Instruments** (Time Profiler, Allocations, Leaks, Metal, Energy Log, SwiftUI template) | **sysprof**, `perf`, Hotspot, Valgrind\u002FMassif, heaptrack |\n| Graphics debugging | Metal debugger, Quartz Debug | RenderDoc, `GTK_DEBUG=interactive`, `apitrace` |\n| Widget inspection | Xcode View Debugger | **GTK Inspector** (`GTK_DEBUG=interactive`), **Qt's `GammaRay`** |\n| Memory errors | ASan\u002FTSan\u002FUBSan via Xcode schemes | ASan\u002FTSan\u002FUBSan, Valgrind |\n| Leaks | `leaks`, Instruments Leaks, Xcode Memory Graph | heaptrack, `G_DEBUG=gc-friendly` + Valgrind |\n| Logging | **`os.Logger`** (unified logging; `log stream --predicate`) | `journalctl`, `G_MESSAGES_DEBUG=all`, `QT_LOGGING_RULES` |\n| Crash reports | `~\u002FLibrary\u002FLogs\u002FDiagnosticReports`, Xcode Organizer, Sentry\u002FCrashlytics | `coredumpctl`, ABRT, Sentry |\n| D-Bus tracing | — | `busctl monitor`, `dbus-monitor`, `d-feet` |\n\n**The two most underused tools**: on macOS, **Instruments' Time Profiler with \"Record\nWaiting Threads\"** turns \"the app hangs sometimes\" into a stack; on Linux,\n`GTK_DEBUG=interactive` gives you a live widget inspector with CSS editing in any GTK app,\nincluding ones you didn't write.\n\n### 13.3 CI for desktop apps\n\n```\npush\n ├─ lint + format (SwiftLint\u002FSwiftFormat; clang-format; clippy; eslint)\n ├─ unit tests: domain + view models ................ fast, every commit\n ├─ build all targets (macOS universal; Linux x86_64 + aarch64)\n ├─ ASan\u002FTSan run of the test suite (nightly)\n ├─ package: .app + notarize + staple + DMG | Flatpak build + lint\n ├─ SBOM + dependency CVE scan\n ├─ sign artifacts (HSM\u002Fhosted signing, never a laptop key)\n └─ nightly: UI smoke tests on real macOS + headless Wayland; update-flow test\n```\n\n**Platform-specific CI realities:**\n- **macOS builds require macOS runners.** Notarization requires network access and an App\n  Store Connect API key. GitHub-hosted macOS images change their default Xcode on a\n  schedule — **pin your Xcode version** (`sudo xcode-select -s \u002FApplications\u002FXcode_26.4.app`\n  or the setup-xcode action), or a runner-image update will break your build without a\n  commit from you.\n- **Linux GUI tests need a display.** Use a headless Wayland compositor (`weston\n  --backend=headless-backend.so`, `wlheadless-run`, or `cage`) or Xvfb for X11 paths.\n- **Test the update path in CI**, not just the app. A broken updater is unrecoverable\n  without asking users to reinstall manually.\n- **Test on the oldest OS you claim to support.** \"Deployment target macOS 13\" that has\n  only ever run on macOS 26 is a claim, not a fact.\n",{"name":5,"description":7},"develop","ae32736a1aabddabca5d2c96d665aa0ebc7d8700","src\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fdesktop-apps-macos-linux\u002Fskills\u002Fdesktop-packaging-security-and-testing",3,"https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey","https:\u002F\u002Fthe-vibey-project.github.io\u002Fvibey\u002F","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project","https:\u002F\u002Fvibewithadam.matthewsteinberger.com","freedom for software engineers","2026-11-15 05:47:42",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add the-vibey-project\u002Fvibey --skill desktop-packaging-security-and-testing",{"tool":40,"command":41},"bunx","bunx skills add the-vibey-project\u002Fvibey --skill desktop-packaging-security-and-testing",{"tool":43,"command":44},"pnpm","pnpm dlx skills add the-vibey-project\u002Fvibey --skill desktop-packaging-security-and-testing","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fdesktop-apps-macos-linux\u002Fskills\u002Fdesktop-packaging-security-and-testing\u002FSKILL.md",true,[],[49,56,63,70,77,84],{"skillNo":50,"name":51,"nameZh":6,"description":52,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":53,"categories":54,"keywords":55,"publishedAt":19},"01M7AT1FQJAE1FQYAMDTF490Y4","white-paper-writing","Use when writing white papers, technical reports, policy documents, thought leadership pieces, or any long-form authoritative document. Triggers on requests to write, structure, outline, or review white papers, technical reports, position papers, policy briefs, or evidence-driven arguments. Also use for B2B content marketing strategy, technical documentation requiring authority, academic-style reports, or any document that must educate while persuading. Use when someone asks \"how should I structure this\" for a long-form document.","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fwriting-craft\u002Fskills\u002Fwhite-paper-writing\u002FSKILL.md",[],[],{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":19},"01M7AT16BJRJJKK2MASXRZS76G","prose-technical-mechanics","Use when editing or writing prose at a technical\u002Fmechanical level: choosing between Anglo-Saxon and Latinate diction, placing information in topic vs stress positions, writing periodic vs cumulative sentences, handling sentence rhythm, punctuation as logic, transitions, paragraph structure, or phonesthetics. Use when someone wants to understand WHY prose works or doesn't, not just surface-level style advice. Triggers on word choice, sentence structure, emphasis, rhythm, diction, or any deep writing mechanics question.","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fwriting-craft\u002Fskills\u002Fprose-technical-mechanics\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M7AT0W9HT0ZZ9Y287NW99MR3","prose-mechanics","Use when writing, editing, or analyzing prose style; when trying to avoid generic AI-sounding writing; when applying specific prose styles such as journalistic, academic, narrative, KJV biblical, Hemingway plain, Latinate\u002FJamesian, Orwellian, Augustan, Victorian, Early Modern (Bacon, Browne, Milton), or free indirect discourse; or when coaching someone on writing voice and mechanics. Triggers on any request to improve, analyze, or write in a specific prose style, to fix \"AI-sounding\" writing, to make prose more vivid or concrete, to vary sentence rhythm, or to understand how a particular writer achieves their effects.","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fwriting-craft\u002Fskills\u002Fprose-mechanics\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M7AT0KR635JX66X2X6F3E2CP","narrative-structure","Use when structuring stories, pitches, presentations, white papers, or any persuasive narrative; analyzing the hero's journey in fiction or non-fiction; applying StoryBrand for business communication; designing narrative arcs for thought leadership; or understanding Vogler, Snyder, Propp, or Campbell frameworks. Triggers on any narrative structure, storytelling, pitch structure, StoryBrand, hero's journey, three-act structure, Freytag, Save the Cat, narrative arc, or \"how should I structure this story\u002Fpitch\u002Fpresentation\" request.","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fwriting-craft\u002Fskills\u002Fnarrative-structure\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M7AT0AKGW09NKKZDYBT8VRDE","legal-brief-writing","Use when writing legal briefs, motions, or any court filing; when analyzing judicial cognition and persuasion; when applying elite brief-writing techniques from Roberts, Clement, Kagan, Garner; or when structuring legal arguments for maximum persuasion. Also use for autistic\u002Fneurodivergent advocates who need to understand how their natural communication style maps to elite legal advocacy. Triggers on any legal writing, brief drafting, motion preparation, or legal argument structuring request.","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fwriting-craft\u002Fskills\u002Flegal-brief-writing\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M7AT00VWPS4Q8B5VEMXX9NQT","journal-publishability-criteria","Use whenever a research paper, article or preprint is being written, revised, reviewed or published, and specifically before every publication of docs\u002Fpaper.md. Covers what legitimate journals actually gate on, in order of gating — the editor's desk screen (scope, novelty, package problems), what reviewers judge (methodological soundness, claims the evidence can carry, statistical and qualitative reporting), EQUATOR reporting guidelines, the ICMJE authorship criteria, COPE's view of text recycling, the near-universal generative-AI policy (no AI author, disclosure, author responsibility), TOP 2025 transparency standards, how to verify a journal is legitimate, submitting without an institution, and a pre-submission checklist. Triggers on requests to evaluate, review, prepare or submit a paper, to judge publishability, to write a declarations or data-availability section, to disclose AI use, or to check a journal.","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fwriting-craft\u002Fskills\u002Fjournal-publishability-criteria\u002FSKILL.md",[],[]]