adynato-mobile_skill

This skill helps you implement and optimize React Native Expo mobile apps with API-driven UI, navigation, performance, and platform considerations.

1

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill adynato/skills --skill adynato-mobile

SKILL.md8.8 KB

Overview

This skill documents mobile app development conventions for Adynato projects using React Native and Expo. It codifies stack choices, navigation patterns, native API handling, performance guidance, and an API-driven UI approach to minimize app store releases. Use it as the reference when building or modifying Adynato mobile apps to ensure consistency and reliability.

How this skill works

The skill prescribes an Expo-managed workflow with Expo Router for file-based navigation, NativeWind for styling, Zustand or React Context for state, and TanStack Query for data fetching and caching. It emphasizes server-controlled UI (feature flags, copy, lists, navigation) so changes can be made without a new binary. It also lists which pieces must remain native (core navigation, native modules, offline logic, and heavy animations) and provides patterns for remote config, caching, and performance tuning.

When to use it

Starting a new Adynato mobile app or migrating an existing app to the recommended stack
Implementing server-driven UI elements like copy, feature flags, feeds, or navigation changes
Adding or updating native integrations (permissions, secure storage, location)
Optimizing lists, animations, or app performance across iOS and Android
Preparing builds and release checklists before EAS production builds

Best practices

Make as much UI as possible API-driven: feature flags, copy, banners, navigation and form config
Use Expo Router file-based routes for consistent navigation structure and tab layouts
Cache with TanStack Query and balance staleTime for freshness vs offline support
Prefer expo-image for remote and local images and use FlashList for long lists
Handle safe areas, platform-specific styles, and keyboard avoiding views explicitly
Store sensitive data in expo-secure-store and request permissions with Expo APIs, handling denials gracefully

Example use cases

A/B testing onboarding flows and copy by toggling remote config without releasing a new build
Rolling out a new checkout flow behind a feature flag while keeping the legacy flow for rollback
Serving dynamic home screen sections and promotional banners from a /api/home/config endpoint
Optimizing feeds with server-controlled layout (grid vs list) and FlashList for performance
Building deep links and offline-first screens while keeping navigation and native modules in the app

FAQ

Feature flags, copy, images, lists, navigation items, form fields, onboarding flows, pricing and app config should be API-driven so they can be changed without an app update.

What must remain native in the app?

Core navigation structure, native module integrations, performance-critical animations, and offline-first functionality must stay in native code and not be fully server-driven.