shadow-mobile
Skill1 starsChanged yesterdayMITView on GitHub
Mobile Build, MASVS v2.1.0 & Store Release Engineering. Use when hardening, signing, or releasing Android/iOS/Flutter/React Native apps, checking PrivacyInfo.xcprivacy, Play Integrity API, targetSdkVersion, Universal/App Links, or Maestro/Detox E2E.
In this repository51 other files it gives its agents.
- antislop-codeSkill
- antislop-copywritingSkill
- antislop-humanSkill
- antislop-layoutmobileSkill
- antislopSkill
- antislop-uiSkill
- context7Skill
- handoffSkill
- shadow-accessibilitySkill
- shadow-apiSkill
- shadow-architectSkill
- shadow-authSkill
- shadow-bootstrapSkill
- shadow-browserSkill
- shadow-cacheSkill
- shadow-compatSkill
- shadow-concurrencySkill
- shadow-dataSkill
- shadow-dbSkill
- shadow-debugSkill
- shadow-designSkill
- shadow-discoverySkill
- shadow-docSkill
- shadow-domainSkill
- shadow-eaSkill
- shadow-evalSkill
- shadow-finopsSkill
- shadow-gitSkill
- shadow-grcSkill
- shadow-handoverSkill
- shadow-integrateSkill
- shadow-maintainSkill
- shadow-modernizeSkill
- shadow-monarchSkill
- shadow-observeSkill
- shadow-opsSkill
- shadow-perfSkill
- shadow-planSkill
- shadow-pmoSkill
- shadow-presalesSkill
- shadow-privacySkill
- shadow-qualitySkill
- shadow-realtimeSkill
- shadow-refactorSkill
- shadow-releaseSkill
- shadow-resilienceSkill
- shadow-searchSkill
- shadow-secSkill
- shadow-supplychainSkill
- shadow-testSkill
- shadow-uatSkill
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 0 are distinctive, and 6 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
6
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 8
Use this skill whenever the Monarch invokes /shadow-mobile, configures Android/iOS/Flutter/React Native production builds, sets up deep …
- Very specific: line 22
MASVS-RESILIENCE: Use Google Play Integrity API (not deprecated SafetyNet) and iOS App Attest (DCAppAttestService) for high-risk … - Very specific: line 26
Verify Info.plist purpose strings (NSCameraUsageDescription, NSFaceIDUsageDescription, etc.) are specific and accurate.
- Very specific: line 30
Verify 16 KB ELF alignment for native .so libraries on Android 15+ devices (NDK r27+ / AGP 8.5.1+).
- Very specific: line 31
Never hardcode storePassword, keyPassword, or .jks/.p12 credentials in build.gradle or Git — load exclusively from CI secrets/environment …
- Very specific: line 38
Run automated mobile E2E flows (Maestro / Detox / Flutter integration_test) across key auth, offline-resume, deep-link, and payment/form …
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
/shadow-mobile — Mobile Hardening (OWASP MASVS v2.1.0), Signing & Store Release Gate
Use this skill whenever the Monarch invokes /shadow-mobile, configures Android/iOS/Flutter/React Native production builds, sets up deep links or attestation, or prepares binaries for Google Play Console or Apple App Store Connect submission.
Grounded in authoritative standards and platform rules documented in references/MASVS-2-1-AND-STORE-RELEASE-GATES.md:
- OWASP MASVS v2.1.0 (Mobile Application Security Verification Standard) —
https://mas.owasp.org/MASVS/(MASVS-STORAGE,MASVS-CRYPTO,MASVS-AUTH,MASVS-NETWORK,MASVS-PLATFORM,MASVS-CODE,MASVS-RESILIENCE,MASVS-PRIVACY). - Apple App Store &
PrivacyInfo.xcprivacyRequirements + Google Play Policy,targetSdkVersion& Play Integrity API.
1. The 5-Gate Mobile Production & Store Readiness Workflow
Gate 1: OWASP MASVS v2.1.0 Security & Storage Audit
MASVS-STORAGE: Sensitive tokens/keys live strictly in iOS Keychain (kSecAttrAccessibleAfterFirstUnlockThisDeviceOnly) or Android Keystore / EncryptedSharedPreferences — never plaintextAsyncStorage,UserDefaults, orSharedPreferences.MASVS-NETWORK: Enforce TLS 1.2+/1.3 (android:usesCleartextTraffic="false"and iOSNSAllowsArbitraryLoads=false); disable WebView file/universal access unless strictly sandboxed.MASVS-PLATFORM: Explicitly setandroid:exported="false"on internalActivity,Service,BroadcastReceiver, andContentProvidercomponents; validate deep-link URLs against allowlists.MASVS-RESILIENCE: Use Google Play Integrity API (not deprecated SafetyNet) and iOS App Attest (DCAppAttestService) for high-risk financial/auth requests, plus R8/ProGuard obfuscation (minifyEnabled true,shrinkResources true) and symbol upload (mapping.txt/.dSYM).
Gate 2: Apple App Store & PrivacyInfo.xcprivacy (MASVS-PRIVACY)
- Ship
PrivacyInfo.xcprivacydeclaringNSPrivacyTracking,NSPrivacyTrackingDomains,NSPrivacyCollectedDataTypes, andNSPrivacyAccessedAPITypesfor Apple's Required Reason APIs (FileTimestamp,SystemBootTime,DiskSpace,ActiveKeyboards,UserDefaults) so App Store Connect does not reject the build (ITMS-91053). - Verify
Info.plistpurpose strings (NSCameraUsageDescription,NSFaceIDUsageDescription, etc.) are specific and accurate.
Gate 3: Google Play Console & Android Build Readiness
- Build signed Android App Bundle (
.aab) with Play App Signing; verifytargetSdkVersionmeets current Google Play minimum API level policy. - Verify 16 KB ELF alignment for native
.solibraries on Android 15+ devices (NDK r27+/ AGP 8.5.1+). - Never hardcode
storePassword,keyPassword, or.jks/.p12credentials inbuild.gradleor Git — load exclusively from CI secrets/environment variables.
Gate 4: Verified Deep Linking (Universal Links & App Links)
- iOS Universal Links: Serve signed
/.well-known/apple-app-site-associationover HTTPS (200 OK, no redirects,application/json). - Android App Links: Serve
/.well-known/assetlinks.jsoncontaining the exact Play App Signing SHA-256 fingerprint (adb shell pm get-app-links).
Gate 5: Mobile E2E & Crash-Free Gate
- Run automated mobile E2E flows (Maestro / Detox / Flutter
integration_test) across key auth, offline-resume, deep-link, and payment/form journeys before signing the store release candidate.
2. Automated Mobile Release & MASVS Gate Script
python "shadow-mobile/scripts/mobile_release_gate.py" --scan .
python "shadow-mobile/scripts/mobile_release_gate.py" --self-testReport findings with exact MASVS ID / Store Policy, file:line, impact (rejection risk vs security exploit), and concrete XML/Gradle/Plist patch.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

