{"id":77636,"plugin_id":"plugins_6ae8cc5ee77c81918ab31ed7701a28de","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-11-03T00:15:26.846Z","digest":"fa28edc831c1eccf981c148844c1de82cc567a88f5d67b334bfb8e40b55f594b","against":null,"payload":{"description":"Build or maintain a shared-codebase iOS and Android app using Expo/React Native or Flutter, preserving platform-specific behavior and release constraints.","included_files":[],"name":"build-cross-platform-app","skill_md_contents":"---\nname: build-cross-platform-app\ndescription: Build or maintain a shared-codebase iOS and Android app using Expo/React Native or Flutter, preserving platform-specific behavior and release constraints.\n---\n\n# Build Cross Platform App\n\n1. Read `../../references/cross-platform.md` and select Expo/React Native vs Flutter based on existing repository, team capabilities, native modules, UX requirements, web needs and performance.\n2. Shared core does **not** imply identical screens. Respect iOS navigation/safe areas and Android back navigation/system UI/Material conventions; use platform-specific components when warranted.\n3. Implement coherent navigation, forms, offline/persistence model, accessibility and error states. Do not claim Web, Android and iOS functionality tested because one platform builds.\n4. Separate app state, network/adapters and platform permissions; audit third-party native packages, build plugins and secrets.\n5. Run available platform tests/builds separately; for iOS signing/simulators require macOS/Apple tooling, Android builds require proper SDK. Clearly mark unrun platforms.\n6. Provide actual source, setup instructions, dependency versions, proof of builds and remaining platform risks; request approval for EAS/App Store/Play publishing.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}