What problem does it solve? Apps submitted to the App Store with leftover placeholder text, "Coming Soon" tabs, hardcoded test credentials, or staging endpoints are routinely rejected under Apple Guideline 2.1 (App Completeness). This Skill scans an iOS/macOS codebase before submission to catch these rejection signals early. ## Core Features & Use Cases - Placeholder Content Detection: Greps Swift, strings, and plist files for Lorem ipsum, TODO/FIXME, and "Coming Soon" UI copy that reviewers treat as incomplete-app signals. - Security & Environment Checks: Finds hardcoded test credentials (e.g., test@test.com, password123) and non-production endpoints (localhost, staging, .dev domains) in network configuration. - Minimum Functionality Audit: Flags WebView-only apps that violate Guideline 4.2 by wrapping a website without native functionality. - Use Case: Before submitting a build, run the check on your project root to get a prioritized findings list (CRITICAL/HIGH/MEDIUM) with file paths, line numbers, and remediation TODOs mapped to specific Apple guidelines. ## Quick Start Run the app completeness check on my iOS project and list any placeholder content, hardcoded credentials, or staging endpoints that could cause an App Store rejection.
