Expo NativeWind Design

Create mobile interfaces that feel intentional, product-specific, and native to the app. Preserve working navigation, data flow, business logic, dependencies, and established design decisions.

Get a compact design brief

Inspect existing screens, theme tokens, assets, fonts, components, and supplied references first. Do not ask for information the project already answers. In one compact message, ask only for missing decisions:

• app category, audience, screen goal, and primary action;
• primary, secondary, and optional accent colors;
• neutral/background direction and light, dark, or both modes;
• font preference or permission to recommend one;
• compact, comfortable, or spacious density;
• desired feeling or visual references.

If the user provides only a primary color, propose an accessible supporting palette for confirmation. If a screenshot or established app already defines the direction, summarize what was inferred and ask the user to correct it rather than starting a long interview.

Before changing files, show no more than five short bullets covering the screen/flow, design direction, affected files, components/assets, and verification. Wait for confirmation, then implement only that scope.