expo-architecture-enforcer

Refactor Expo applications to align with canonical folder structure and stack conventions.

Updated Mar 3, 2026
One-click install
npx skills add https://github.com/addisualemu/basic_expo --skill expo-architecture-enforcer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: expo-architecture-enforcer
Source: https://github.com/addisualemu/basic_expo/tree/main/generator/.cursor/skills/expo-architecture-enforcer
Command: npx skills add https://github.com/addisualemu/basic_expo --skill expo-architecture-enforcer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill enforces a canonical folder structure and technology stack for Expo applications, ensuring consistency and maintainability.

Core Features & Use Cases

  • Folder Structure Alignment: Moves files to standard locations (e.g., app/, components/, lib/).
  • Stack Enforcement: Helps align the app with conventions like Expo Router, Zustand, and NativeWind.
  • Use Case: When a project's file organization has become messy, or when onboarding new developers, this Skill can refactor the existing structure to match established best practices.

Quick Start

Use the expo-architecture-enforcer skill to refactor the current Expo project to match the standard folder structure and stack conventions.

Frequently Asked Questions about expo-architecture-enforcer

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

FAQPage Schema
How do I refactor an existing Expo app to use Expo Router and a standard folder structure?

To refactor an existing Expo app, you can use an architecture enforcer to move files into standard locations like `app/`, `components/`, and `lib/` while aligning the project with Expo Router and Zustand conventions.

What is the canonical folder structure for an Expo application using Zustand and NativeWind?

The canonical Expo folder structure standardizes file locations into directories such as `app/` for routing, `components/` for UI, and `lib/` for logic, ensuring consistency when using Zustand and NativeWind.

Can I use an architecture enforcer to clean up a messy Expo project layout?

Yes, an architecture enforcer cleans up a messy Expo project layout by refactoring the existing file organization to match established best practices and technology stack conventions.

What's the best way to enforce code structure conventions during Expo onboarding?

The best way to enforce code structure conventions during Expo onboarding is to refactor the project against a canonical layout, aligning files with Expo Router, Zustand, and NativeWind for maintainability.

Does refactoring an Expo app structure require adherence to specific app conventions?

Yes, refactoring an Expo app structure requires adherence to established expo-app-conventions to ensure the target layout, folder structure, and technology stack are applied correctly.