apple-cleanup

Apple Cleanup — EXHAUSTIVE Engineering Hardening

Purpose: Transform an app from "development mode" to "production hardened" through EXHAUSTIVE engineering excellence — crash-free, App Store compliant, fully optimized. This is MISSION-CRITICAL cleanup. Lives depend on it. No shortcuts. No omissions.

☠️ ULTIMATE RULES (NON-NEGOTIABLE)

1. NEVER START UI TESTS unless the user has explicitly approved it in the current conversation. This stands even if a plan says to run them. UI tests crash this user's Mac Mini.
2. NEVER KEEP MULTIPLE VERSIONS OF A FEATURE IN CODE (v2Enabled, legacyMode, newFlow, etc.). When replacing a feature, replace it. Delete the old path. Systematic modular variants (enum injection, DI, strategy protocols) are allowed; inline boolean forks are forbidden.

Scope: EXHAUSTIVE — ALL priorities must be addressed:

• P0 (Critical): Engineering crashes, data loss, security vulnerabilities — ZERO TOLERANCE
• P1 (High): Compliance rejection risks, Swift 6 improvements, performance, error handling — MUST FIX
• P2 (Medium): Tech debt, style cleanup, optimizations, documentation — MUST FIX
• P3 (Low): Minor refinements — address if identified

THIS IS NOT OPTIONAL CLEANUP. Every identified issue from P0 to P2 MUST be fixed before completion. No exceptions.

No design reviews, no marketing narratives.

When to Use

• Pre-submission hardening — "The app works, now make it bulletproof for App Review"
• Swift 6 compliance pass — "Fix all concurrency warnings and strict mode issues"
• Crash prevention sweep — "Find and fix every potential crash"
• Post-development cleanup — "Clean up accumulated tech debt and AI slop"
• Before TestFlight alpha — "Engineering validation before distributing"

Not for: Design reviews, feature additions, version management, or marketing copy.

---

Command Reference

/apple-cleanup              # Cleanup app in current directory
/apple-cleanup [app]        # Cleanup a specific app target