gooseyprime-savr-platform-mobile-instructions.ocm.json json {
"ocm": "1",
"id": "gooseyprime-savr-platform-mobile-instructions",
"kind": "skill",
"name": "platform-mobile",
"description": "SAVR platform mobile rules",
"publisher": "GooseyPrime",
"version": "1.0.0",
"capabilities": {
"domains": [
"general"
],
"tags": [
"skill-md",
"github-instructions"
],
"languages": [
"en"
]
},
"quality_prior": 0.6,
"examples": [
"SAVR platform mobile rules"
],
"primary": false,
"metadata": {
"source": {
"provider": "github-instructions",
"repository": "https://github.com/GooseyPrime/SAVR",
"path": ".github/instructions/platform-mobile.instructions.md",
"ref": "d0e1a5193cb3f89dd57d9a1975ee8a38822e2dd6",
"url": "https://github.com/GooseyPrime/SAVR/blob/d0e1a5193cb3f89dd57d9a1975ee8a38822e2dd6/.github/instructions/platform-mobile.instructions.md",
"key": "GooseyPrime/SAVR/.github/instructions/platform-mobile.instructions.md"
},
"applies_to": "savr-platform/mobile/**"
},
"instructions": "# SAVR platform mobile rules\n\n- Follow the proven Expo/React Native production patterns from `SAVR-old/mobile/` until a documented decision changes them.\n- Preserve navigation clarity, safe-area handling, camera and photo permissions, and mobile-specific validation.\n- Device storage may support explicit offline behavior, but authenticated production state must reconcile with the backend contract.\n- Keep auth, scanner, image upload, and recipe flows aligned with the production backend.\n- Validate native behavior, permission prompts, and screen transitions instead of assuming parity from web cod",
"cost": {
"context_tokens": 150
}
}