Automated summary
Generates attractive, production-ready mobile interfaces for Expo Go and React Native.
Strengths
- Leverages Expo Go built-in components with zero extra installs
- Provides clear color palettes and typography systems
- Includes concrete examples of reusable components like cards and lists
- Encourages intentional design with visual hierarchy
Limitations
- Does not cover global state or complex data management
- Requires user familiarity with React Native basics
- Suggested styles are a starting point, need customization
Use this skill when you need to quickly generate consistent and aesthetic mobile screens using Expo.
Avoid this skill for web-only projects, or when a specific UI library (e.g., React Native Paper) is mandated.
Security analysis
SafeThe skill provides design principles, code snippets, and reusable components for Expo React Native UI. It does not instruct the agent to execute any commands, run scripts, or perform destructive actions. It only suggests optional package installations for the user, not for the agent to execute automatically. No exfiltration, obfuscation, or safety bypasses are present.
No concerns found
How this analysis is madeExamples
Create a login screen for my mobile app using Expo and React Native, with email and password fields, a sign-in button, and social login options. Dark theme.Generate a dashboard for a finance app with summary cards, recent transactions list, and an expense chart. Use NativeWind for styling.Design a user profile page with avatar, stats, and settings list. Use @expo/vector-icons for icons.name: expo-mobile-ui description: > Genera interfaces móviles atractivas y production-ready para Expo Go / React Native. Usa esta skill siempre que el usuario pida pantallas, componentes, layouts, dashboards, onboarding, login, tarjetas, listas, navegación o cualquier UI para una app móvil con Expo, React Native, NativeWind, o StyleSheet. También aplica cuando el usuario diga "hazlo para móvil", "pantalla de inicio", "diseño de app", "componente nativo" o similar.
Expo Mobile UI Skill
Genera código React Native / Expo Go limpio, atractivo y listo para correr con npx expo start.
Principios de diseño
Antes de escribir código, define:
- Propósito: ¿Qué problema resuelve esta pantalla? ¿Qué acción principal debe ejecutar el usuario?
- Tono visual: Elige una dirección clara. Ejemplos: oscuro/premium, minimalista/blanco, colorido/energético, suave/pastel. Comprométete con una sola.
- Jerarquía: Qué es lo más importante visualmente en pantalla. El ojo del usuario debe ir ahí primero.
CRÍTICO: Nunca produzcas UI genérica. Cada pantalla debe tener un punto de vista visual claro.
Stack y dependencias
Core (ya incluido en Expo Go — sin instalación)
react-native → View, Text, ScrollView, TouchableOpacity, FlatList, Image, etc.
expo-status-bar → StatusBar
expo-linear-gradient → LinearGradient (gradientes)
@expo/vector-icons → Ionicons, MaterialIcons, Feather, FontAwesome5, etc.
Opcional recomendado (instalar si el usuario no los tiene)
npx expo install react-native-safe-area-context react-native-screens
npm install nativewind tailwindcss # si se usa NativeWind
npm install @shopify/restyle # sistema de temas tipado
Siempre indica al usuario qué debe instalar si el código lo requiere.
Íconos disponibles (sin instalación)
@expo/vector-icons ya viene en Expo Go. Úsalos así:
import { Ionicons } from '@expo/vector-icons';
import { Feather } from '@expo/vector-icons';
import { MaterialIcons } from '@expo/vector-icons';
<Ionicons name="home-outline" size={24} color="#fff" />
<Feather name="arrow-right" size={20} color="#000" />
<MaterialIcons name="dashboard" size={28} color="#6C63FF" />
Nombres comunes de Ionicons: home-outline, person-outline, settings-outline,
search-outline, notifications-outline, heart-outline, star-outline,
arrow-back, chevron-forward, add-circle-outline, log-out-outline,
moon-outline, sunny-outline, camera-outline, image-outline.
Sistema de estilos
Paleta base recomendada (oscuro/premium)
const colors = {
bg: '#0D0D0D',
surface: '#1A1A1A',
card: '#222222',
border: '#2E2E2E',
accent: '#7C6FFF', // morado/violeta — color principal
accentSoft:'#3D3580',
text: '#F5F5F5',
muted: '#888888',
success: '#4CAF50',
warning: '#FF9800',
danger: '#F44336',
};
Alternativa claro/minimalista
const colors = {
bg: '#FAFAFA',
surface: '#FFFFFF',
card: '#F2F2F2',
border: '#E5E5E5',
accent: '#5B4FE8',
text: '#111111',
muted: '#777777',
};
Tipografía (System Fonts — sin instalación)
const typography = {
h1: { fontSize: 28, fontWeight: '700' as const, letterSpacing: -0.5 },
h2: { fontSize: 22, fontWeight: '600' as const },
h3: { fontSize: 18, fontWeight: '600' as const },
body: { fontSize: 15, fontWeight: '400' as const, lineHeight: 22 },
small: { fontSize: 13, fontWeight: '400' as const },
label: { fontSize: 11, fontWeight: '500' as const, letterSpacing: 0.8, textTransform: 'uppercase' as const },
};
Espaciado y radios
const spacing = { xs: 4, sm: 8, md: 16, lg: 24, xl: 32, xxl: 48 };
const radius = { sm: 8, md: 12, lg: 20, full: 999 };
Componentes reutilizables
Card base
<View style={{
backgroundColor: colors.card,
borderRadius: radius.lg,
padding: spacing.md,
borderWidth: 1,
borderColor: colors.border,
}}>
{children}
</View>
Botón primario
<TouchableOpacity
activeOpacity={0.8}
style={{
backgroundColor: colors.accent,
borderRadius: radius.full,
paddingVertical: 14,
paddingHorizontal: spacing.xl,
alignItems: 'center',
}}
>
<Text style={{ color: '#fff', fontSize: 16, fontWeight: '600' }}>
Continuar
</Text>
</TouchableOpacity>
Botón secundario / outline
<TouchableOpacity
activeOpacity={0.8}
style={{
borderWidth: 1,
borderColor: colors.accent,
borderRadius: radius.full,
paddingVertical: 14,
paddingHorizontal: spacing.xl,
alignItems: 'center',
}}
>
<Text style={{ color: colors.accent, fontSize: 16, fontWeight: '600' }}>
Cancelar
</Text>
</TouchableOpacity>
Input
<View style={{
backgroundColor: colors.surface,
borderRadius: radius.md,
borderWidth: 1,
borderColor: colors.border,
flexDirection: 'row',
alignItems: 'center',
paddingHorizontal: spacing.md,
height: 52,
}}>
<Feather name="mail" size={18} color={colors.muted} />
<TextInput
placeholder="tu@email.com"
placeholderTextColor={colors.muted}
style={{ flex: 1, marginLeft: 10, color: colors.text, fontSize: 15 }}
/>
</View>
Avatar / iniciales
<View style={{
width: 44, height: 44,
borderRadius: 22,
backgroundColor: colors.accentSoft,
alignItems: 'center',
justifyContent: 'center',
}}>
<Text style={{ color: colors.accent, fontWeight: '700', fontSize: 15 }}>MR</Text>
</View>
Badge / etiqueta
<View style={{
backgroundColor: colors.accentSoft,
borderRadius: radius.full,
paddingHorizontal: 10,
paddingVertical: 3,
}}>
<Text style={{ color: colors.accent, fontSize: 12, fontWeight: '600' }}>Nuevo</Text>
</View>
Tab bar inferior (manual, sin librería)
const tabs = [
{ icon: 'home-outline', label: 'Inicio' },
{ icon: 'search-outline', label: 'Buscar' },
{ icon: 'notifications-outline',label: 'Alertas' },
{ icon: 'person-outline', label: 'Perfil' },
];
<View style={{
flexDirection: 'row',
backgroundColor: colors.surface,
borderTopWidth: 1,
borderTopColor: colors.border,
paddingBottom: 24, // safe area manual
paddingTop: 10,
}}>
{tabs.map((t, i) => (
<TouchableOpacity key={i} style={{ flex: 1, alignItems: 'center', gap: 4 }}>
<Ionicons name={t.icon as any} size={22} color={active === i ? colors.accent : colors.muted} />
<Text style={{ fontSize: 10, color: active === i ? colors.accent : colors.muted }}>{t.label}</Text>
</TouchableOpacity>
))}
</View>
Estructura de pantalla completa
import React from 'react';
import { View, Text, ScrollView, TouchableOpacity, StyleSheet } from 'react-native';
import { StatusBar } from 'expo-status-bar';
import { Ionicons } from '@expo/vector-icons';
export default function HomeScreen() {
return (
<View style={styles.container}>
<StatusBar style="light" />
{/* Header */}
<View style={styles.header}>
<View>
<Text style={styles.greeting}>Buen día,</Text>
<Text style={styles.name}>María García</Text>
</View>
<TouchableOpacity style={styles.avatarBtn}>
<Ionicons name="person-outline" size={20} color="#F5F5F5" />
</TouchableOpacity>
</View>
{/* Contenido */}
<ScrollView
contentContainerStyle={styles.content}
showsVerticalScrollIndicator={false}
>
{/* ... componentes aquí */}
</ScrollView>
</View>
);
}
const styles = StyleSheet.create({
container: { flex: 1, backgroundColor: '#0D0D0D' },
header: { flexDirection: 'row', justifyContent: 'space-between',
alignItems: 'center', paddingHorizontal: 20,
paddingTop: 56, paddingBottom: 16 },
greeting: { color: '#888', fontSize: 14 },
name: { color: '#F5F5F5', fontSize: 22, fontWeight: '700' },
avatarBtn: { width: 40, height: 40, borderRadius: 20,
backgroundColor: '#222', alignItems: 'center',
justifyContent: 'center', borderWidth: 1, borderColor: '#2E2E2E' },
content: { paddingHorizontal: 20, paddingBottom: 32, gap: 16 },
});
Reglas obligatorias
- Un archivo por pantalla — todo el código (estilos incluidos) en un solo
.tsx. - StyleSheet.create() siempre — nunca objetos de estilo inline para estilos repetidos.
- Nada de
position: 'absolute'a menos que sea imprescindible (overlay, FAB). - ScrollView en pantallas con contenido largo; FlatList si hay listas dinámicas.
- TouchableOpacity con
activeOpacity={0.8}para todos los botones. - Safe area manual:
paddingTop: 48–56en el header;paddingBottom: 24en la tab bar. Usarreact-native-safe-area-contextsi está disponible, sino padding manual. - Nunca uses colores hardcoded dispersos — define el objeto
colorsarriba y referencíalo. - Indica al usuario si necesita instalar algo con
npx expo installonpm install.
Patrones de pantalla comunes
| Pantalla | Componentes clave | |-----------------|-------------------------------------------------------------| | Login/Registro | Logo, inputs con ícono, botón primario, link secundario | | Home/Dashboard | Header con saludo, stat cards en grid 2×2, lista de items | | Perfil | Avatar grande, stats horizontales, lista de ajustes | | Detalle | Imagen hero, info superpuesta, botón de acción sticky abajo | | Onboarding | Ilustración centrada, título, subtítulo, dots, botón | | Lista/Feed | FlatList con cards, pull-to-refresh, empty state | | Settings | Secciones con filas, toggle switches, íconos de fila |
Checklists antes de entregar
- [ ] ¿Corre en Expo Go sin errores? (sin dependencias nativas no compatibles)
- [ ] ¿Los colores tienen contraste suficiente (texto sobre fondo)?
- [ ] ¿Hay un estado vacío o de carga si hay datos dinámicos?
- [ ] ¿Los tap targets miden al menos 44×44 puntos?
- [ ] ¿El código es un solo archivo autocontenido?
- [ ] ¿Se indicaron las instalaciones necesarias?
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/expo-mobile-ui-skill-mryiqibw/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/expo-mobile-ui-skill-mryiqibw' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/expo-mobile-ui-skill-mryiqibw/download' --output '.skill-downloads/expo-mobile-ui-skill-mryiqibw/SKILL.md.part' && mv '.skill-downloads/expo-mobile-ui-skill-mryiqibw/SKILL.md.part' '.skill-downloads/expo-mobile-ui-skill-mryiqibw/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.
Claude Code
test -f '.skill-downloads/expo-mobile-ui-skill-mryiqibw/SKILL.md' && test -s '.skill-downloads/expo-mobile-ui-skill-mryiqibw/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/expo-mobile-ui' && cp -R '.skill-downloads/expo-mobile-ui-skill-mryiqibw' '.claude/skills/expo-mobile-ui'Cursor
test -f '.skill-downloads/expo-mobile-ui-skill-mryiqibw/SKILL.md' && test -s '.skill-downloads/expo-mobile-ui-skill-mryiqibw/SKILL.md' && mkdir -p '.cursor/skills' && test ! -e '.cursor/skills/expo-mobile-ui' && cp -R '.skill-downloads/expo-mobile-ui-skill-mryiqibw' '.cursor/skills/expo-mobile-ui'Codex
test -f '.skill-downloads/expo-mobile-ui-skill-mryiqibw/SKILL.md' && test -s '.skill-downloads/expo-mobile-ui-skill-mryiqibw/SKILL.md' && mkdir -p '.agents/skills' && test ! -e '.agents/skills/expo-mobile-ui' && cp -R '.skill-downloads/expo-mobile-ui-skill-mryiqibw' '.agents/skills/expo-mobile-ui'OpenSkills
OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.
Official OpenSkills installationopenskills install './.skill-downloads/expo-mobile-ui-skill-mryiqibw'openskills read 'expo-mobile-ui-skill-mryiqibw'Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.
For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.
openskills syncManual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/expo-mobile-ui-skill-mryiqibw/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
React Hook Form Best Practices
Development
Master React Hook Form: avoid anti-patterns, manage subscriptions, and handle reset, dirty state, and controlled inputs correctly.
Emotion to Mantine Migration
Development
Migrate Emotion styled-components to Mantine components with style props and CSS modules. Use when converting .styled.tsx files or removing @emotion imports.
Scope Creep Detector
Development
Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad PRs, and oversized changes, then suggests keep, split, or justify actions.