expo-app-conventions

Define canonical folder structure and stack conventions for Expo applications.

Updated Mar 3, 2026

Search Tags:#typescript #conventions #zustand #react native #app structure #expo #nativewind

Ready to run

npx skills add https://github.com/addisualemu/basic_expo --skill expo-app-conventions

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: expo-app-conventions
Source: https://github.com/addisualemu/basic_expo/tree/main/generator/.cursor/skills/expo-app-conventions
Command: npx skills add https://github.com/addisualemu/basic_expo --skill expo-app-conventions

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a definitive, opinionated structure and stack for Expo applications, ensuring consistency and maintainability across projects and developers.

Core Features & Use Cases

Canonical Structure: Defines the exact folder layout for routing, components, state management, API clients, and utilities.
Opinionated Stack: Enforces specific choices for routing (Expo Router), state management (Zustand), and styling (NativeWind).
Use Case: When starting a new Expo project or adding new features, consult this Skill to ensure files are placed in the correct directories and adhere to the established conventions.

Quick Start

Use the expo-app-conventions skill to understand the standard folder structure for a new Expo app.

Frequently Asked Questions about expo-app-conventions

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

FAQPage Schema

What is the best way to structure an Expo app with Expo Router and Zustand?▼

The best way to structure an Expo app is to use a canonical folder layout that enforces Expo Router for routing, Zustand for state management, and NativeWind for styling to ensure architectural consistency.

How do I organize files when adding new features to a React Native Expo project?▼

To organize files in an Expo project, follow a standardized convention that places routing, components, state management, API clients, and utilities into specific predefined directories to maintain consistency.

Does the standard Expo app convention work with NativeWind for styling?▼

Yes, the standard Expo app convention explicitly enforces NativeWind for styling, alongside Expo Router for navigation and Zustand for state management, to provide a definitive, opinionated stack.

Why do I need an opinionated stack for my Expo application?▼

You need an opinionated stack for your Expo application to solve the problem of maintaining consistency and structure across projects and developers, ensuring files are placed correctly and architectural standards are met.

Can I use this Expo app structure for both new projects and existing features?▼

Yes, you can use this Expo app structure for both starting a new project and adding new features, consulting the defined conventions to ensure files are placed in the correct directories and adhere to the established stack.

What are the limitations of using a predefined Expo folder structure?▼

The limitation of using this predefined Expo folder structure is its strictly opinionated nature, requiring the use of Expo Router, Zustand, and NativeWind, which may not suit projects already using alternative routing or state management libraries.