Mac Clean
Use this skill when the user asks to clean macOS storage or organize long-accumulated files. Default to low-risk actions and ask confirmation before high-impact changes.
Goals
- Recover space quickly with repeatable, low-risk operations.
- Report before/after sizes for key directories.
- Keep personal data and system-critical areas untouched unless explicitly requested.
- Improve folder order without breaking app behavior or project runtimes.
Safety Rules
- Do not delete personal folders by default:
~/Desktop, ~/Documents, ~/Pictures, ~/Movies, ~/Downloads.
- Do not delete app/system trees by default:
/Applications, /System, /Library.
- Do not touch SIP/protected system settings.
- Keep Codex runtime data untouched unless user explicitly asks.
- If macOS returns
Operation not permitted, skip and continue. Report skipped paths.
- For organization tasks, never touch:
~/Library
/Library
/System
/private/var
- For project folders, move directories only. Do not edit file contents.
Default Workflow (safe)
- Baseline scan:
du -sh ~/Library/Caches ~/Library/Logs ~/.npm ~/.m2 ~/.gradle ~/.Trash 2>/dev/null
- Clean low-risk caches:
rm -rf ~/Library/Caches/*
rm -rf ~/Library/Logs/*
rm -rf ~/.npm/_cacache/*
- Verify:
- Re-run baseline scan and report reclaimed size.
Organization Workflow (organize-safe)
Use this mode when the user wants less chaos, not necessarily more free space.
- Scan only user file zones:
~/Downloads, ~/Documents, ~/Desktop
- Optional work roots like
~/IdeaProjects, ~/vscodeSpace
- Create stable target structure:
~/Workspace/{Projects,Documents,Media,Archive,Installers}
- Classify obvious loose files (no deletion):
mp4/mov -> media folder
pdf/docx/txt/xmind/xml -> typed document folders
- Project hygiene:
- Keep active projects in place.
- Move clear temporary/history candidates into archive folders.
- Keep a conservative first pass; avoid broad repo moves without user signal.
- Record changes:
- Write a migration log under
~/Workspace/Documents/ with moved paths and date.
Aggressive Workflow (aggressive, explicit user request only)
Includes all safe steps, plus optional confirmed actions:
- Maven cache purge:
rm -rf ~/.m2/repository
- Gradle cache purge:
rm -rf ~/.gradle/caches ~/.gradle/wrapper
- Homebrew cleanup:
brew cleanup -s
- Empty Trash:
rm -rf ~/.Trash/*
- Docker cleanup:
docker system prune -a
For each optional action, explain impact first and ask for clear confirmation.
Mode Guide
safe: storage cleanup only, low-risk cache/log cleanup.
aggressive: deeper storage cleanup with explicit approval.
organize-safe: no risky system touches; reorganize user files/projects only.
Output Format
Before: key path sizes
Actions: what was deleted and what was skipped
After: key path sizes
Recovered: estimated reclaimed size
Next: optional high-impact actions for approval
Moved: list of directories/files moved during organization (if organize-safe)
Notes
- On macOS, privacy-protected folders may require Full Disk Access.
- Cache cleanup is usually safe, but first app launch/build after cleanup may be slower.
- Prefer predictable cache directories over ad hoc file deletion.
- For organization, favor traceability over speed: log every move and preserve reversible structure.
1---2name: mac-clean3description: Safely clean macOS with two tracks: storage cleanup and zero-risk file organization, both with explicit safety boundaries and reporting.4---56# Mac Clean78Use this skill when the user asks to clean macOS storage or organize long-accumulated files. Default to low-risk actions and ask confirmation before high-impact changes.910## Goals1112- Recover space quickly with repeatable, low-risk operations.13- Report before/after sizes for key directories.14- Keep personal data and system-critical areas untouched unless explicitly requested.15- Improve folder order without breaking app behavior or project runtimes.1617## Safety Rules1819- Do not delete personal folders by default: `~/Desktop`, `~/Documents`, `~/Pictures`, `~/Movies`, `~/Downloads`.20- Do not delete app/system trees by default: `/Applications`, `/System`, `/Library`.21- Do not touch SIP/protected system settings.22- Keep Codex runtime data untouched unless user explicitly asks.23- If macOS returns `Operation not permitted`, skip and continue. Report skipped paths.24- For organization tasks, never touch:25 - `~/Library`26 - `/Library`27 - `/System`28 - `/private/var`29- For project folders, move directories only. Do not edit file contents.3031## Default Workflow (`safe`)32331. Baseline scan:34 - `du -sh ~/Library/Caches ~/Library/Logs ~/.npm ~/.m2 ~/.gradle ~/.Trash 2>/dev/null`352. Clean low-risk caches:36 - `rm -rf ~/Library/Caches/*`37 - `rm -rf ~/Library/Logs/*`38 - `rm -rf ~/.npm/_cacache/*`393. Verify:40 - Re-run baseline scan and report reclaimed size.4142## Organization Workflow (`organize-safe`)4344Use this mode when the user wants less chaos, not necessarily more free space.45461. Scan only user file zones:47 - `~/Downloads`, `~/Documents`, `~/Desktop`48 - Optional work roots like `~/IdeaProjects`, `~/vscodeSpace`492. Create stable target structure:50 - `~/Workspace/{Projects,Documents,Media,Archive,Installers}`513. Classify obvious loose files (no deletion):52 - `mp4/mov` -> media folder53 - `pdf/docx/txt/xmind/xml` -> typed document folders544. Project hygiene:55 - Keep active projects in place.56 - Move clear temporary/history candidates into archive folders.57 - Keep a conservative first pass; avoid broad repo moves without user signal.585. Record changes:59 - Write a migration log under `~/Workspace/Documents/` with moved paths and date.6061## Aggressive Workflow (`aggressive`, explicit user request only)6263Includes all `safe` steps, plus optional confirmed actions:6465- Maven cache purge: `rm -rf ~/.m2/repository`66- Gradle cache purge: `rm -rf ~/.gradle/caches ~/.gradle/wrapper`67- Homebrew cleanup: `brew cleanup -s`68- Empty Trash: `rm -rf ~/.Trash/*`69- Docker cleanup: `docker system prune -a`7071For each optional action, explain impact first and ask for clear confirmation.7273## Mode Guide7475- `safe`: storage cleanup only, low-risk cache/log cleanup.76- `aggressive`: deeper storage cleanup with explicit approval.77- `organize-safe`: no risky system touches; reorganize user files/projects only.7879## Output Format8081- `Before`: key path sizes82- `Actions`: what was deleted and what was skipped83- `After`: key path sizes84- `Recovered`: estimated reclaimed size85- `Next`: optional high-impact actions for approval86- `Moved`: list of directories/files moved during organization (if `organize-safe`)8788## Notes8990- On macOS, privacy-protected folders may require Full Disk Access.91- Cache cleanup is usually safe, but first app launch/build after cleanup may be slower.92- Prefer predictable cache directories over ad hoc file deletion.93- For organization, favor traceability over speed: log every move and preserve reversible structure.