macos-recipeslisted

# macOS Recipes Exact commands, expected output shape, and gotchas. Use these verbatim rather than improvising — the gotchas are the value. ## Scope note This skill covers **command mechanics only** — what to run, what the output means, and where each command lies or fails silently. It deliberately holds no policy. Read the companions for the rules that govern using these commands: `mac-it-guy-pro:it-core` for the safety contract (Trash instead of delete, dry-run first, undo manifests, admin work handed to the user), `mac-it-guy-pro:machine-profile` for what may be written down afterwards, and `mac-it-guy-pro:toolbox-contract` for turning a recipe into a tool the user keeps. Network measurement lives in `mac-it-guy-pro:home-network`, not here. A recipe in this file is never authority to run it — the contract decides that. ## Diagnostics (read-only) ### Disk - Free space: `df -h /` — use the `Avail` and `Capacity` columns of the `/System/Volumes/Data` or `/` line. - What's big (one level): `du -x -h -d 1 ~ 2>/dev/null | sort -rh | head -15` - Top 10 largest files: `find ~ -xdev -type f -size +500M -not -path "*/Library/*" 2>/dev/null -exec du -h {} + | sort -rh | head -10` - Gotcha: `du` over the whole home folder takes 1–4 minutes on a full disk. Say so before running; use a 300000 ms timeout. - Gotcha: macOS "purgeable" space makes Finder and `df` disagree. If they differ, trust `df` and explain the difference in one sentence. ### Memory & CPU - Memory pressure: `mem