build-dmg
Skill15 starsChanged 8 months agoApache-2.0View on GitHub
Build a distributable DMG installer for any macOS Xcode project. Handles archiving, code signing, DMG creation with styled Finder window, and version management. Trigger on: "build a DMG", "create DMG installer", "package as DMG", "build for distribution", or when the user wants to distribute a macOS app outside the App Store.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- giulio333/ClaudeLenstheir own version, first seen Oct 7, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- giulio333/ClaudeLens★ 67same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository63 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- agent-browserSkill
- ast-grepSkill
- branch-review-before-prSkill
- browse-qaSkill
- browser-useSkill
- browseSkill
- bugfixSkill
- claude-reviewSkill
- codemapSkill
- code-simplifySkill
- codex-reviewSkill
- commitSkill
- cost-estimateSkill
- create-prSkill
- find-agentsSkill
- find-bugsSkill
- frontend-design-ui-uxSkill
- git-merge-expertSkill
- git-merge-expert-worktreeSkill
- kiro-reviewSkill
- laravel-filamentSkill
- laravelSkill
- lokeiSkill
- map-project-monorepoSkill
- map-projectSkill
- nextjsSkill
- plan-founder-reviewSkill
- plan-to-task-list-with-dagSkill
- pr-retroSkill
- run-parallel-agents-feature-buildSkill
- run-parallel-agents-feature-debugSkill
- rustSkill
- secretsSkill
- startSkill
- update-agent-learningsSkill
- update-claude-learningsSkill
- update-claude-settingsSkill
- update-skill-learningsSkill
- ast-grepSkill
- branch-review-before-prSkill
- codemapSkill
- code-simplifySkill
- commitSkill
- cost-estimateSkill
- create-prSkill
- find-bugsSkill
- frontend-design-ui-uxSkill
- git-merge-expertSkill
- git-merge-expert-worktreeSkill
- map-project-monorepoSkill
- map-projectSkill
- plan-founder-reviewSkill
- plan-to-task-list-with-dagSkill
- pr-retroSkill
- run-parallel-agents-feature-buildSkill
- run-parallel-agents-feature-debugSkill
- startSkill
- update-agent-learningsSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 71
If the project doesn't have one, create a minimal scripts/ExportOptions.plist:
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
build-dmg
Build a styled DMG installer from any macOS Xcode project.
Before Running
Detect the project settings by reading available files:
- App name — from
package.jsonname,project.ymlname,.xcodeprojdirectory name, or ask the user - Scheme — run
xcodebuild -listto discover available schemes, or ask the user - Project/Workspace — auto-detected if only one
.xcodeprojor.xcworkspaceexists at root - ExportOptions.plist — check if
scripts/ExportOptions.plistexists. If not, ask the user for the path or whether to create one - VERSION file — check if a
VERSIONfile exists at project root - xcodegen — check if
project.ymlexists (indicates xcodegen usage) - Team ID — check existing build settings or ask the user
Present the detected configuration to the user and confirm before building.
Running the Build
The build script is at .claude/skills/build-dmg/helpers/build-dmg.sh. Run it directly from the project root with the required env vars:
APP_NAME="<app>" SCHEME="<scheme>" bash .claude/skills/build-dmg/helpers/build-dmg.shThe script uses the current working directory as the project root. Do NOT copy the script into the project.
Required Environment Variables
| Variable | Description |
APP_NAME | Display name for the .app and DMG volume |
SCHEME | Xcode scheme to build |
Optional Environment Variables
| Variable | Default | Description |
PROJECT | auto-detected | Path to .xcodeproj |
WORKSPACE | — | Path to .xcworkspace (takes precedence over PROJECT) |
INFO_PLIST | <SCHEME>/Info.plist | Path to Info.plist for version injection |
EXPORT_OPTIONS | scripts/ExportOptions.plist | Path to ExportOptions.plist |
TEAM_ID | — | Apple Development Team ID |
VERSION_FILE | VERSION | Path to VERSION file. Set to "none" to skip version management |
USE_XCODEGEN | 0 | Set to "1" to run xcodegen generate before building |
DMG_BACKGROUND | — | Path to a background image for the DMG window |
After the Build
- Success — report the DMG path, version, and build number from the script output
- Failure — extract the error lines from xcodebuild output and summarize what went wrong
- Version bump — if the script bumped the VERSION file, remind the user to commit it
ExportOptions.plist
If the project doesn't have one, create a minimal scripts/ExportOptions.plist:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>method</key>
<string>development</string>
<key>signingStyle</key>
<string>automatic</string>
</dict>
</plist>For distribution outside the App Store, change method to developer-id and ensure the team has a Developer ID certificate.
Do NOT create or modify ExportOptions.plist without asking the user first.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

