Expo Native Builder

Preserve the request first

Before proposing anything, extract the user's required screens, behavior, visual direction, file locations, references, and exclusions. Treat every explicitly named screen or feature as required. A supplied implementation plan overrides this skill's defaults. Do not replace the requested journey with a generic template.

Inspect the existing routes, components, tokens, assets, fonts, dependencies, and business logic before choosing an architecture. Preserve working conventions. Ask only for a missing decision that materially changes the result.

For a new multi-step onboarding flow, start from this compact structure and adapt it to the user's names: