liftori-mobile

Document Liftori Mobile's SDK patterns, architecture, and Supabase storage integration.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/JaxRhino/liftori-mobile --skill liftori-mobile
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: liftori-mobile
Source: https://github.com/JaxRhino/liftori-mobile/tree/main
Command: npx skills add https://github.com/JaxRhino/liftori-mobile --skill liftori-mobile

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires sharp, and includes scripts (resource) components.

What problem does it solve?

Liftori's mobile codebase is complex, with SDK 51 constraints, expo-router conventions, SafeScreen usage, haptics semantics, and on-device Supabase storage. This skill captures the patterns and practices to help engineers write, debug, and plan changes that fit the Liftori mobile architecture.

Core Features & Use Cases

  • Guides how to work within the Expo SDK 51 stack, including typed routes, SafeScreen, and design primitives.
  • Documents the two-layer service/hook pattern and the Supabase-on-device storage adapter, plus the OneDrive-safe refactor moves.
  • Supports planning, coding, and debugging across Wave-based development for liftori-mobile.

Quick Start

Review the Liftori Mobile's codebase and apply the documented conventions for a new feature following the standard Wave patterns and primitives.

Frequently Asked Questions about liftori-mobile

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I structure Expo Router typed routes in a React Native app?

Expo Router typed routes in React Native require strict type safety configurations within the Expo SDK 51 stack. You must define route declarations and integrate SafeScreen to ensure consistent layout rendering across device safe areas.

What is the best way to integrate Supabase on-device storage with React Native?

Supabase on-device storage integration uses a SecureStore adapter to persist data locally within React Native applications. This adapter bridges the storage layer with the two-layer service/hook pattern to manage authenticated sessions safely.

Does Expo SDK 51 support SafeScreen and haptic feedback patterns?

Expo SDK 51 supports SafeScreen implementations for safe area layouts and includes haptic semantics for tactile feedback. Developers apply these design primitives to maintain consistent UI rendering and user interaction standards across devices.

How do I implement a two-layer service and hook pattern for React Native authentication?

A two-layer service and hook pattern separates data access from UI state in React Native authentication. The service layer handles Supabase calls while the hook layer manages component state, ensuring clean integration with the SecureStore adapter.

Why use SafeScreen instead of standard SafeAreaView in Expo Router?

SafeScreen provides specialized layout handling tailored for expo-router conventions and theme tokens. It standardizes safe area rendering across the application, ensuring consistent UI primitives that match the architectural constraints of Expo SDK 51.