Mole Mac Cleanup

**Judgement:** A strong macOS-only cleanup and optimization skill built around the `mole` (`mo`) CLI. It is well-suited for automated maintenance on developer and power-user Macs, but it inherently carries some risk due to its ability to delete caches, logs, and project artifacts. **What it’s good for** - Reclaiming disk space by cleaning system and app caches, logs, browser leftovers, trash, and old installers. - Periodic system optimization (rebuilding caches, resetting services, refreshing Finder/Dock, cleaning diagnostic logs). - Developer workflows that need automated purging of heavy project artifacts like `node_modules`, `target`, or virtual environments. - Keeping a Mac lean over time without relying on GUI tools like CleanMyMac or DaisyDisk. **Key risks / cautions** - Destructive operations: cleaning and purging can remove data that may affect app performance or developer workflows (e.g., slower rebuilds, removal of cached assets). Misconfigured purge paths could, in theory, delete important project directories. - macOS-only: the skill is tied to the `mole` CLI and Homebrew ecosystem; it is not applicable outside macOS environments. - Permission and stability considerations: aggressive optimization (clearing system caches, swap, rebuilding indexes) can temporarily affect system responsiveness or require rewarming caches. **Recommended scenarios** - Individual developers or power users on macOS who want scripted, repeatable cleanup and optimization with previews via `--dry-run` and `--debug`. - Automated maintenance tasks on macOS machines where disk usage and build artifacts grow quickly (e.g., local dev machines, possibly CI runners using macOS). - Users comfortable with command-line tools who prefer a controlled, preview-first workflow over one-click GUI cleaners.