Menu
Baseline architecture for Axolotl mobile starter (Expo Router + reusable blocks)
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Reusable native component and template patterns for starter implementation
Starter data layer pattern with React Query + Zeus for Expo app
i18n baseline and dev-translate setup for Expo mobile starter
Expo Router conventions for route groups, native headers, and starter navigation
Playwright E2E execution rules - domain-oriented specs, shared auth setup/storageState, idempotent zero-flake runs, verify-email-disabled support, and canonical Mailgun local email path
GraphQL error extraction, global toast handling via QueryCache/MutationCache, auth error auto-logout, and per-hook success toast patterns
| name | mobile-starter-architecture |
| description | Baseline architecture for Axolotl mobile starter (Expo Router + reusable blocks) |
Create starter-level, reusable mobile foundations in examples/new/mobile.
Do not implement full product logic here.
mobile/AGENTS.md.app/ for route files and route groupssrc/components/ for reusable native primitivessrc/templates/ for reusable screen templatessrc/features/ for feature hooks/modulessrc/lib/graphql/ for Zeus + query wrapperssrc/lib/i18n/ for i18n bootstrap and resourcessrc/providers/ for app providerssrc/stores/ for Zustand storessrc/theme/ for tokens and style helperssrc/zeus/ placeholder until generation is wiredtestID on all interactive elements.SafeArea -> RuntimeInit -> Keyboard -> Theme -> Suspense -> (optional integrations) -> Query -> Toast (see src/providers/AppProviders.tsx).runRuntimeInit() (initThemeBase() + initI18n()), fail-safe (must not block first render).templates/** are opt-in blueprints; runtime only from app/** + src/**.testID.useStateView with LoadingState/ErrorState/EmptyState for loading/error/empty/success rendering.