project-pn-macos-dmg-package
Automate the packaging, configuration verification, and DMG creation for macOS desktop applications using Tauri.
Install
mkdir -p .claude/skills/project-pn-macos-dmg-package && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/15992" && unzip -o skill.zip -d .claude/skills/project-pn-macos-dmg-package && rm skill.zipInstalls to .claude/skills/project-pn-macos-dmg-package
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Package the Project PN macOS desktop app as a Tauri DMG for direct distribution. Use when the user asks to build, package, rebuild, verify, or distribute the macOS .dmg, especially when setting EXPO_PUBLIC_API_BASE_URL to an IP/domain API endpoint and providing the macOS unidentified-developer trust command.Key capabilities
- →Build the Project PN macOS app into a .dmg
- →Verify the bundled frontend points to the intended API base URL
- →Provide the install/trust command for unsigned testing builds
- →Handle `hdiutil` failures during DMG creation with escalation
- →Inspect packaging configuration before building
- →Report the DMG path, API base URL, and SHA-256
How it works
The skill builds the Expo Web + Tauri macOS app into a .dmg, verifies the API base URL, and provides commands for installation and trust for testing purposes.
Inputs & outputs
When to use project-pn-macos-dmg-package
- →Building a macOS DMG for distribution
- →Verifying frontend API endpoint configuration
- →Rebuilding the desktop app after changes
- →Testing desktop builds on macOS
About this skill
Project PN macOS DMG Package
Overview
Build the Project PN Expo Web + Tauri macOS app into a .dmg, verify that the bundled frontend points at the intended API base URL, and return the install/trust command for unsigned testing builds.
Workflow
- Work from the repo root:
cd /Users/hyungjuyu/Projects/iOS/Project_PN
- Inspect packaging config before building:
sed -n '1,220p' frontend/package.json
sed -n '1,240p' frontend/src-tauri/tauri.conf.json
sed -n '1,120p' frontend/src/config.ts
- Choose the API base URL.
- Use the URL the user provides (Oracle Cloud public domain or IP).
- If the user gives no URL, ask for the current Oracle Cloud
APP_PUBLIC_URLrather than assuming a home-LAN IP. - This URL must match the backend
ALLOWED_ORIGINSpolicy for Tauri. Includetauri://localhostandhttp://tauri.localhoston the backend for desktop builds.
- Build the DMG from
frontend/:
cd frontend
EXPO_PUBLIC_API_BASE_URL=https://YOUR_PUBLIC_DOMAIN npm run desktop:build
Replace the URL with the selected API base URL. The command writes frontend/dist and frontend/src-tauri/target.
- If Tauri builds the
.appbut DMG creation fails with:
hdiutil: create failed - Device not configured
rerun only the generated DMG step with escalation, because macOS hdiutil needs disk-image device access outside the sandbox:
src-tauri/target/release/bundle/dmg/bundle_dmg.sh \
--volname 'Project PN' \
--volicon src-tauri/target/release/bundle/dmg/icon.icns \
--icon 'Project PN.app' 128 170 \
--app-drop-link 372 170 \
--no-internet-enable \
'src-tauri/target/release/bundle/dmg/Project PN_1.0.2_aarch64.dmg' \
'src-tauri/target/release/bundle/macos'
Use the actual version/filename from the current build output if it differs from 1.0.2.
- Verify the result:
ls -lh 'src-tauri/target/release/bundle/dmg/Project PN_1.0.2_aarch64.dmg'
shasum -a 256 'src-tauri/target/release/bundle/dmg/Project PN_1.0.2_aarch64.dmg'
rg -n '124\.59\.225\.59|EXPO_PUBLIC_API_BASE_URL' dist 'src-tauri/target/release/bundle/macos/Project PN.app/Contents/Resources'
Adjust the rg pattern to match the selected API host.
- Report the DMG path, API base URL, SHA-256, and install/trust command.
User Install Command
For unsigned/unnotarized testing builds, provide:
sudo xattr -rd com.apple.quarantine "/Applications/Project PN.app"
open "/Applications/Project PN.app"
Do not suggest globally disabling Gatekeeper. Mention that signing and notarization are preferred for public distribution.
When not to use it
- →When packaging for operating systems other than macOS
- →When building applications not based on Expo Web + Tauri
- →When a signed and notarized build for public distribution is required
Limitations
- →Specific to Project PN Expo Web + Tauri macOS app
- →Focuses on unsigned/unnotarized testing builds
- →Requires manual adjustment of version/filename in `hdiutil` command if it differs
How it compares
This workflow automates the specific build and verification process for a Project PN macOS DMG, including handling `hdiutil` issues and providing testing commands, unlike a generic application packaging process.
Compared to similar skills
project-pn-macos-dmg-package side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| project-pn-macos-dmg-package (this skill) | 0 | 5mo | Review | Intermediate |
| deployment-engineer | 4 | 7mo | No flags | Advanced |
| devops | 2 | 10mo | Review | Intermediate |
| ecs | 2 | 6mo | Review | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
deployment-engineer
sickn33
Expert deployment engineer specializing in modern CI/CD pipelines, GitOps workflows, and advanced deployment automation. Masters GitHub Actions, ArgoCD/Flux, progressive delivery, container security, and platform engineering. Handles zero-downtime deployments, security scanning, and developer experience optimization. Use PROACTIVELY for CI/CD design, GitOps implementation, or deployment automation.
devops
mrgoonie
Deploy to Cloudflare (Workers, R2, D1), Docker, GCP (Cloud Run, GKE), Kubernetes (kubectl, Helm). Use for serverless, containers, CI/CD, GitOps, security audit.
ecs
itsmostafa
AWS ECS container orchestration for running Docker containers. Use when deploying containerized applications, configuring task definitions, setting up services, managing clusters, or troubleshooting container issues.
exa-deploy-integration
jeremylongshore
Deploy Exa integrations to Vercel, Fly.io, and Cloud Run platforms. Use when deploying Exa-powered applications to production, configuring platform-specific secrets, or setting up deployment pipelines. Trigger with phrases like "deploy exa", "exa Vercel", "exa production deploy", "exa Cloud Run", "exa Fly.io".
local-environment
polarsource
Local development environment management for Polar using Docker
openevidence-deploy-integration
jeremylongshore
Deploy OpenEvidence integrations to healthcare production environments. Use when deploying to production, setting up staging environments, or configuring cloud deployments for clinical AI applications. Trigger with phrases like "deploy openevidence", "openevidence staging", "openevidence production deploy", "release openevidence".