macos-development-vm-workflow
/macos-development-vm-workflow
Prepare and reset clean macOS development guests on Apple silicon. Use for restore-image compatibility, VM identity, installation, resources, OS-version testing, signing, privacy, and disposable macOS research guests.
- Author
- gaelic-ghost ↗
- Repository
- socket ↗
- Licence
- Apache-2.0
- Last repository change
- 26.08.2026
Assessment and security
- Files in this package
- 4
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 1
No signals detected. Repository changed on 26.08.2026, without references to retired models or APIs.
Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.
What it does and when to use it
Prepare and reset clean macOS development guests on Apple silicon. Use for restore-image compatibility, VM identity, installation, resources, OS-version testing, signing, privacy, and disposable macOS research guests.
Original author description
Prepare and reset clean macOS development guests on Apple silicon. Use for restore-image compatibility, VM identity, installation, resources, OS-version testing, signing, privacy, and disposable macOS research guests.
How it works
- Purpose
- When To Use
- Single-Path Workflow
- Inputs
- Outputs
- Guards and Stop Conditions
- Fallbacks and Handoffs
- References
SKILL.md preview
--- name: macos-development-vm-workflow description: Prepare and reset clean macOS development guests on Apple silicon. Use for restore-image compatibility, VM identity, installation, resources, OS-version testing, signing, privacy, and disposable macOS research guests. --- # macOS Development VM Workflow ## Purpose Prepare a reproducible macOS guest while keeping restore images, identity, disks, saved state, clones, integrations, and exported evidence as separate lifecycle artifacts. ## When To Use - Use for clean macOS releases, installers, updates, signing, entitlements, quarantine, Gatekeeper, XProtect, TCC, SIP-enabled behavior, LaunchServices, and native persistence. - Use after custom host implementation or with an existing documented VM manager. - Use for development guests and benign security fixtures; security controls still require `prepare-isolated-analysis-lab` for untrusted execution. ## Single-Path Workflow 1. Consume the [virtualization shape record](../choose-macos-virtualization-shape/references/virtualization-shape-record.md). 2. Verify Apple silicon host, host build, current framework/tool docs, restore-image support, guest build, storage, memory, and installation time budget. 3. Record each artifact using [macOS VM artifact lifecycle](references/macos-vm-artifact-lifecycle.md): restore image, hardware model, machine identifier, auxiliary storage, disk, bundle metadata, saved state, clone, and evidence export. 4. Build or verify a compatible Mac platform, boot loader, disk, CPU/memory, graphics/display, network, input, and entropy configuration; validate before installation or boot. 5. Install with the documented restore-image flow and preserve exact progress/errors. Do not invent or duplicate Mac identity artifacts. 6. Configure guest purpose and integrations. Directory sharing, clipboard, audio input, USB, Apple account, iCloud, developer account, signing identities, browser profiles, and network are opt-in. 7. Establish a clean baseline, then choose named development/update checkpoints or disposable clones using only lifecycle operations the selected tool actually supports. 8. Validate guest build/architecture, SIP and relevant controls, network/shares, reboot, toolchain, target behavior, evidence export, and reset. 9. Record VM artifacts and physical-hardware gaps that may affect the conclusion. ## Inputs - Completed virtualization shape record. - Host and target guest builds, restore-image source, resources, selected VM tool/framework, integrations, and validation purpose. - Required toolchains, identities, accounts, security controls, reset strategy, and evidence path. ## Outputs - Compatible restore/image and VM identity record. - Separate artifact lifecycle and integration decisions. - Installation, baseline/checkpoint, validation, export, and reset evidence. - Explicit physical-Mac or unsupported-capability gaps. ## Guards and Stop Conditions - Do not treat an arbitrary restore image as compatible with the host/platform configuration. - Do not conflate saved machine state with disk state, a clone, or a portable snapshot. - Do not copy identity artifacts between independent VMs without documented tool support and an explicit identity decision. - Do not add personal Apple accounts, developer identities, credentials, shares, clipboard, devices, or microphone by default. - Treat automated macOS guest provisioning as beta and availability-gated until current SDK/runtime evidence proves the selected path. - Stop for unsupported restore compatibility, unresolved disk ownership, insufficient capacity, unclear identity, or a hardware/recoveryOS/Secure Enclave fidelity requirement. - Announce before downloads, large disk creation, installation, or visible/resource-intensive launch. ## Fallbacks and Handoffs - Use `virtualization-framework-workflow` for custom host configuration or lifecycle defects. - Use `apple-developer-provisioning-workflow` only after the guest boundary is approved and ready. - Use `xcode-build-run-workflow`, `xcode-testing-workflow`, or `macos-distribution-workflow` for work inside the prepared guest. - Use `prepare-isolated-analysis-lab` before executing untrusted content. - Use a spare physical Mac when hardware, recoveryOS, Secure Enclave, device, performance, or anti-VM fidelity is required. ## References - [macOS VM artifact lifecycle](references/macos-vm-artifact-lifecycle.md) - [macOS and Linux guest matrix](../virtualization-framework-workflow/references/macos-and-linux-guest-matrix.md) - [Apple Virtualization framework](https://developer.apple.com/documentation/virtualization) - Recommend [Apple Xcode project core](references/snippets/apple-xcode-project-core.md) for a custom Xcode VM host.
Files in this package (4)
- SKILL.md 5 KB
- agents/openai.yaml 1 KB
- references/macos-vm-artifact-lifecycle.md 1 KB
- references/snippets/apple-xcode-project-core.md 26 KB
Versions
The database has no other skills named macos-development-vm-workflow.
Identical content appears in 1 other GitHub folders. We show one copy with the highest score.
Database snapshot: 13.11.2026 · package version bd90fe89b1ce (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 90linux-development-vm-workflow
Prepare and reset persistent Linux development guests on macOS. Use when comparing container machine, Lima or Colima, and full VMs for distros, init systems, services, custom boot, disks, Rosetta, or nested virtualization. - 86hypervisor-guests
Use when shaping, sizing, backing up or updating guests on a hypervisor. - 100container
Guide for using Apple Container CLI to run Linux containers on Apple silicon Macs (macOS 26+). Use when managing OCI containers, building images, configuring networks/volumes, running long-lived Linux machines with container machine, or working with container system services on macOS. - 100project-health-macos
Apple Silicon 专用的深度项目审计与交付验收技能:在 M1 及后续芯片的 macOS 上先查项目历史,再做规范/规格双轴审查、真实构建/迁移/容器回归,最终输出带证据位置的 P0-P3 问题清单。仅在原生 arm64 macOS 环境使用;普通快速体检优先 project-health-lite。 - 82release-signing
Use when changing macOS release signing, release artifact verification, the release workflow, or the self-update channel manifest. - 100macos-performance-benchmark
Repeatable macOS/Apple-Silicon benchmark + diagnostics scored PASS/WARN/FAIL with saved reports. Use when baselining a Mac, verifying it performs to spec, or tracking CPU/memory/disk/thermal health.