building-native-ui
Skill0 starsChanged 2 months agoMITView on GitHub
Complete guide for building beautiful apps with Expo Router. Covers fundamentals, styling, components, navigation, animations, patterns, and native tabs.
- Reads credentials
15 other projects use a version of this, 15 of them edited.
Adopted by
Most recently taken up by
- BrightGold70/skillsedited, first seen Nov 8, 2026
- nnawar706/fluentoedited, first seen Nov 8, 2026
- delorenj/skillsedited, first seen Nov 7, 2026
- xfstudio/skillsedited, first seen Oct 13, 2026
- ramybarsoum/claude-skillsedited, first seen Oct 13, 2026
- openai/pluginsedited, first seen Oct 13, 2026
Used with
Projects with it also use web-design-guidelines and find-skills.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
VercelSkillweb-design-guidelines
Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".
Also in 3 projects that use this
VercelSkillfind-skills
Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.
Also in 3 projects that use this
Other versions15 projects use a version of this.
Word for word · 0
None found.
Edited · 15
- openai/plugins★ 7.8k85% same
- CherryHQ/cherry-studio-app★ 4.1k85% same
- ruizrica/agent-pi★ 27485% same
- happycapy-ai/Happycapy-skills★ 13784% same
- robinebers/skills★ 4885% same
- open-vide/openvide★ 3384% same
- delorenj/skills★ 1785% same
- PIXARTSeu/Synapse★ 985% same
- xfstudio/skills★ 972% same
- matheus-sancha/skills★ 285% same
5 more not listed
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository14 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- expo-cicd-workflowsSkill
- expo-deploymentSkill
- expo-dev-clientSkill
- hig-components-controlsSkill
- hig-components-dialogsSkill
- hig-components-layoutSkill
- hig-foundationsSkill
- hig-patternsSkill
- native-data-fetchingSkill
- no-use-effectSkill
- supabase-postgres-best-practicesSkill
- upgrading-expoSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
38 rules. 23 are common, 0 are distinctive, and 15 are very specific to this project.
23
Common
Most of the 15 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
15
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Common: line 42
Always use import statements at the top of the file.
- Very specific: line 43
Always use kebab-case for file names, e.g.
- Common: line 44
Always remove old route files when moving or restructuring navigation
- Common: line 45
Never use special characters in file names
- Common: line 53
Never co-locate components, types, or utilities in the app directory.
- Common: line 54
Ensure the app always has a route that matches "/", it may be inside a group route.
- Common: line 58
Never use modules removed from React Native such as Picker, WebView, SafeAreaView, or AsyncStorage
- Common: line 59
Never use legacy expo-permissions
- Common: line 71
Always wrap root component in a scroll view for responsiveness
- Very specific: line 72
Use <ScrollView contentInsetAdjustmentBehavior="automatic" /> instead of <SafeAreaView> for smarter safe area insets
- Common: line 74
Use flexbox instead of Dimensions API
- Very specific: line 75
ALWAYS prefer useWindowDimensions over Dimensions.get() to measure screen size
- Common: line 79
Use expo-haptics conditionally on iOS to make more delightful experiences
- Very specific: line 80
Use views with built-in haptics like <Switch /> from React Native and @react-native-community/datetimepicker
- Very specific: line 81
When a route belongs to a Stack, its first child should almost always be a ScrollView with contentInsetAdjustmentBehavior="automatic" set
- Very specific: line 82
When adding a ScrollView to the page it should almost always be the first component inside the route component
- Very specific: line 83
Prefer headerSearchBarOptions in Stack.Screen options to add a search bar
- Very specific: line 84
Use the <Text selectable /> prop on text containing data that could be copied
- Common: line 85
Consider formatting large numbers like 1.4M or 38k
- Common: line 86
Never use intrinsic elements like 'img' or 'div' unless in a webview or Expo DOM component
- Common: line 90
Follow Apple Human Interface Guidelines.
- Common: line 94
Prefer flex gap over margin and padding styles
- Common: line 95
Prefer padding over margin where possible
- Very specific: line 96
Always account for safe area, either with stack headers, tabs, or ScrollView/FlatList contentInsetAdjustmentBehavior="automatic"
- Common: line 97
Ensure both top and bottom safe area insets are accounted for
- Common: line 99
Add entering and exiting animations for state changes
- Very specific: line 100
Use { borderCurve: 'continuous' } for rounded corners unless creating a capsule shape
- Common: line 101
ALWAYS use a navigation stack title instead of a custom text element on the page
- Very specific: line 102
When padding a ScrollView, use contentContainerStyle padding and gap instead of padding on the ScrollView itself (reduces clipping)
- Very specific: line 107
Add the selectable prop to every <Text/> element displaying important data or error messages
- Very specific: line 112
Use CSS boxShadow style prop.
- Very specific: line 124
Use <Link href="/path" /> from 'expo-router' for navigation between routes.
- Very specific: line 142
ALWAYS use _layout.tsx files to define stacks
- Common: line 143
Use Stack from 'expo-router/stack' for native navigation stacks
- Common: line 155
Add long press context menus to Link components:
- Common: line 193
Use link previews frequently to enhance navigation:
- Common: line 216
Prefer this to building a custom modal component.
- Common: line 269
Create a shared group route so both tabs can push common screens:
“Common” is measured: kept by at least 6 in 10 of the 15 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Starter integration: root AGENTS.md and docs define the chosen stack and commands. Use Next.js for backend routes and EAS for native builds. Apply platform principles to React Native; do not create an Xcode project or product specification from these examples. Supporting references describe options, not installed capabilities.
Expo UI Guidelines
References
Consult these resources as needed:
references/
animations.md Reanimated: entering, exiting, layout, scroll-driven, gestures
controls.md Native iOS: Switch, Slider, SegmentedControl, DateTimePicker, Picker
form-sheet.md Form sheets in expo-router: configuration, footers and background interaction.
gradients.md CSS gradients via experimental_backgroundImage (New Arch only)
icons.md SF Symbols via expo-image (sf: source), names, animations, weights
media.md Camera, audio, video, and file saving
route-structure.md Route conventions, dynamic routes, groups, folder organization
search.md Search bar with headers, useSearch hook, filtering patterns
storage.md SQLite, AsyncStorage, SecureStore
tabs.md NativeTabs, migration from JS tabs, iOS 26 features
toolbar-and-headers.md Stack headers and toolbar buttons, menus, search (iOS only)
visual-effects.md Blur (expo-blur) and liquid glass (expo-glass-effect)
webgpu-three.md 3D graphics, games, GPU visualizations with WebGPU and Three.js
zoom-transitions.md Apple Zoom: fluid zoom transitions with Link.AppleZoom (iOS 18+)Running the app in this starter
Use pnpm dev from the repository root and the installed EAS development client. Native builds use the root build:ios:* commands with the owner's authorization. Do not run local native builds. See the root AGENTS.md and docs/releases.md. Upstream platform examples below are references; use the installed Expo SDK's APIs.
Code Style
- Be cautious of unterminated strings. Ensure nested backticks are escaped; never forget to escape quotes correctly.
- Always use import statements at the top of the file.
- Always use kebab-case for file names, e.g.
comment-card.tsx - Always remove old route files when moving or restructuring navigation
- Never use special characters in file names
- Configure tsconfig.json with path aliases, and prefer aliases over relative imports for refactors.
Routes
See ./references/route-structure.md for detailed route conventions.
- Routes belong in the
appdirectory. - Never co-locate components, types, or utilities in the app directory. This is an anti-pattern.
- Ensure the app always has a route that matches "/", it may be inside a group route.
Library Preferences
- Never use modules removed from React Native such as Picker, WebView, SafeAreaView, or AsyncStorage
- Never use legacy expo-permissions
expo-audionotexpo-avexpo-videonotexpo-avexpo-imagewithsource="sf:name"for SF Symbols, notexpo-symbolsor@expo/vector-iconsreact-native-safe-area-contextnot react-native SafeAreaViewprocess.env.EXPO_OSnotPlatform.OSReact.usenotReact.useContextexpo-imageImage component instead of intrinsic elementimgexpo-glass-effectfor liquid glass backdrops
Responsiveness
- Always wrap root component in a scroll view for responsiveness
- Use
<ScrollView contentInsetAdjustmentBehavior="automatic" />instead of<SafeAreaView>for smarter safe area insets contentInsetAdjustmentBehavior="automatic"should be applied to FlatList and SectionList as well- Use flexbox instead of Dimensions API
- ALWAYS prefer
useWindowDimensionsoverDimensions.get()to measure screen size
Behavior
- Use expo-haptics conditionally on iOS to make more delightful experiences
- Use views with built-in haptics like
<Switch />from React Native and@react-native-community/datetimepicker - When a route belongs to a Stack, its first child should almost always be a ScrollView with
contentInsetAdjustmentBehavior="automatic"set - When adding a
ScrollViewto the page it should almost always be the first component inside the route component - Prefer
headerSearchBarOptionsin Stack.Screen options to add a search bar - Use the
<Text selectable />prop on text containing data that could be copied - Consider formatting large numbers like 1.4M or 38k
- Never use intrinsic elements like 'img' or 'div' unless in a webview or Expo DOM component
Styling
Follow Apple Human Interface Guidelines.
General Styling Rules
- Prefer flex gap over margin and padding styles
- Prefer padding over margin where possible
- Always account for safe area, either with stack headers, tabs, or ScrollView/FlatList
contentInsetAdjustmentBehavior="automatic" - Ensure both top and bottom safe area insets are accounted for
- Inline styles not StyleSheet.create unless reusing styles is faster
- Add entering and exiting animations for state changes
- Use
{ borderCurve: 'continuous' }for rounded corners unless creating a capsule shape - ALWAYS use a navigation stack title instead of a custom text element on the page
- When padding a ScrollView, use
contentContainerStylepadding and gap instead of padding on the ScrollView itself (reduces clipping) - CSS and Tailwind are not supported - use inline styles
Text Styling
- Add the
selectableprop to every<Text/>element displaying important data or error messages - Counters should use
{ fontVariant: 'tabular-nums' }for alignment
Shadows
Use CSS boxShadow style prop. NEVER use legacy React Native shadow or elevation styles.
<View style={{ boxShadow: "0 1px 2px rgba(0, 0, 0, 0.05)" }} />'inset' shadows are supported.
Navigation
Link
Use <Link href="/path" /> from 'expo-router' for navigation between routes.
import { Link } from 'expo-router';
// Basic link
<Link href="/path" />
// Wrapping custom components
<Link href="/path" asChild>
<Pressable>...</Pressable>
</Link>Whenever possible, include a <Link.Preview> to follow iOS conventions. Add context menus and previews frequently to enhance navigation.
Stack
- ALWAYS use
_layout.tsxfiles to define stacks - Use Stack from 'expo-router/stack' for native navigation stacks
Page Title
Set the page title in Stack.Screen options:
<Stack.Screen options={{ title: "Home" }} />Context Menus
Add long press context menus to Link components:
import { Link } from "expo-router";
<Link href="/settings" asChild>
<Link.Trigger>
<Pressable>
<Card />
</Pressable>
</Link.Trigger>
<Link.Menu>
<Link.MenuAction
title="Share"
icon="square.and.arrow.up"
onPress={handleSharePress}
/>
<Link.MenuAction
title="Block"
icon="nosign"
destructive
onPress={handleBlockPress}
/>
<Link.Menu title="More" icon="ellipsis">
<Link.MenuAction title="Copy" icon="doc.on.doc" onPress={() => {}} />
<Link.MenuAction
title="Delete"
icon="trash"
destructive
onPress={() => {}}
/>
</Link.Menu>
</Link.Menu>
</Link>;Link Previews
Use link previews frequently to enhance navigation:
<Link href="/settings">
<Link.Trigger>
<Pressable>
<Card />
</Pressable>
</Link.Trigger>
<Link.Preview />
</Link>Link preview can be used with context menus.
Modal
Present a screen as a modal:
<Stack.Screen name="modal" options={{ presentation: "modal" }} />Prefer this to building a custom modal component.
Sheet
Present a screen as a dynamic form sheet:
<Stack.Screen
name="sheet"
options={{
presentation: "formSheet",
sheetGrabberVisible: true,
sheetAllowedDetents: [0.5, 1.0],
contentStyle: { backgroundColor: "transparent" },
}}
/>- Using
contentStyle: { backgroundColor: "transparent" }makes the background liquid glass on iOS 26+.
Common route structure
A standard app layout with tabs and stacks inside each tab:
app/
_layout.tsx — <NativeTabs />
(index,search)/
_layout.tsx — <Stack />
index.tsx — Main list
search.tsx — Search view// app/_layout.tsx
import { NativeTabs, Icon, Label } from "expo-router/unstable-native-tabs";
import { Theme } from "../components/theme";
export default function Layout() {
return (
<Theme>
<NativeTabs>
<NativeTabs.Trigger name="(index)">
<Icon sf="list.dash" />
<Label>Items</Label>
</NativeTabs.Trigger>
<NativeTabs.Trigger name="(search)" role="search" />
</NativeTabs>
</Theme>
);
}Create a shared group route so both tabs can push common screens:
// app/(index,search)/_layout.tsx
import { Stack } from "expo-router/stack";
import { PlatformColor } from "react-native";
export default function Layout({ segment }) {
const screen = segment.match(/\((.*)\)/)?.[1]!;
const titles: Record<string, string> = { index: "Items", search: "Search" };
return (
<Stack
screenOptions={{
headerTransparent: true,
headerShadowVisible: false,
headerLargeTitleShadowVisible: false,
headerLargeStyle: { backgroundColor: "transparent" },
headerTitleStyle: { color: PlatformColor("label") },
headerLargeTitle: true,
headerBlurEffect: "none",
headerBackButtonDisplayMode: "minimal",
}}
>
<Stack.Screen name={screen} options={{ title: titles[screen] }} />
<Stack.Screen name="i/[id]" options={{ headerLargeTitle: false }} />
</Stack>
);
}Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

