mac-storage-cleaner

原文涵盖的主题

• Mac Storage Cleaner
• Core principles
• Workflow
• 1. Survey — caches (always first, read-only)
• 2. Clear the safe tier (no per-item permission needed)
• 3. Surface the "ask" tier — recommend, don't delete
• 4. Go beyond caches — the space the cleaners miss (read-only scan)
• 5. Report

Free disk space the way a careful engineer would, and earn the trust one-click cleaners lose: measure first, delete only what provably regenerates, make anything riskier reversible, ask before anything expensive, log every action, and report honestly. The differentiator over CleanMyMac-style tools is judgment and transparency — the user sees what will go and why, and can undo it. Scripts live in scripts/; the full tiered inventory, exact reclaim commands, and gotchas are in references/cache-catalog.md. Read the catalog whenever you hit something a script didn't classify or you need the precise command. Safe tier → delete outright (space back immediately). These are pure caches; the only cost is a slower next build/install. Everything else → Trash, not rm. Ask-tier items, app leftovers, big files — move them to the Trash with trash-items.sh so the user can restore them. Reversibility is the whole point; never hard-delete a user's data. When unsure, demote a tier. A slower rebuild is trivial; deleting a license, an unpushable Xcode archive, or someone's only local backup is not. Every destructive run is logged to /Library/Logs/mac-storage-cleaner/operations.log. Locating the scripts.

这里只展示节选，请以完整原文和当前要求为准。