mobile-react-native
- Repo stars 0
- Author updated Live
- Author repo skills-registry
- Domain
- Other
- Compatible agents
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- Trust score
- 88 / 100 · community maintained
- Author / version / license
- @tomevault-io · no license declared
- Token usage
- Lean
- Setup complexity
- Plug-and-play
- External API key
- Not required
- Operating systems
- macOS · Linux · Windows
- Runtime requirements
- No special requirements
- Permissions
-
- Read-only
- Write / modify
- Network behavior
- External requests
- Install commands
- 26 variants
Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.
Heads up: 未限定 allowed-tools,默认拥有全部工具权限。
---
name: mobile-react-native
description: >- Use when this capability is needed. npx create-expo-app@latest my-app --template blank-typesc…
category: other
runtime: no special runtime
---
# mobile-react-native output preview
## PART A: Task fit
- Use case: >- Use when this capability is needed. npx create-expo-app@latest my-app --template blank-typescript npx expo install expo-router expo-linking expo-constants npx expo install nativewind tailwindcss ├── _layout.tsx # Root layout (navigation) makes outbound network calls. Works with Claude Code, Cursor, Cline and 23 more..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “Initial Setup / Directory Structure / Key Patterns” and do not present inference as author intent.
## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “>- Use when this capability is needed. npx create-expo-app@latest my-app --template blank-typescript npx expo install expo-router expo-linking expo-constants npx expo install nativewind tailwindcss ├── _layout.tsx # Root layout (navigation) makes outbound network calls. Works with Claude Code, Cursor, Cline and 23 more.”.
- **02** When the source has headings, the agent prioritizes “Initial Setup / Directory Structure / Key Patterns” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, write/modify files; may access external network resources; usually needs no extra API key.
## Running Rules
- read files, write/modify files; may access external network resources; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options. The source does not require a stable slash command. After installation, invoke the skill by name and describe the task.
Name target files or source material, expected output, forbidden changes, and whether network or shell access is allowed. Permission fingerprint: read files, write/modify files.
Start with a small task and check whether the result follows “Initial Setup / Directory Structure / Key Patterns”. Inspect diffs, logs, previews, or tests before expanding scope.
Confirm the final output includes a concrete result, evidence, and next action. If it stays generic, tighten inputs, boundaries, and acceptance criteria.
---
name: mobile-react-native
description: >- Use when this capability is needed. npx create-expo-app@latest my-app --template blank-typesc…
category: other
source: tomevault-io/skills-registry
---
# mobile-react-native
## When to use
- >- Use when this capability is needed. npx create-expo-app@latest my-app --template blank-typescript npx expo install…
- Use it when the task has clear inputs, repeatable steps, and validation criteria.
## What to provide
- Target material, scope, expected result, and forbidden changes.
- Whether network, commands, file writes, or external services are allowed.
## Execution rules
- Organize steps around “Initial Setup / Directory Structure / Key Patterns” and keep inference separate from source facts.
- read files, write/modify files; may access external network resources; usually needs no extra API key.
- Validate with a small sample before expanding the task.
## Output requirements
- Return the deliverable, key evidence, validation method, and next action.
- Mark missing information as unknown; do not invent commands, platforms, or dependencies. The author source anchors workflow facts; repository files anchor sources and commands; Fluxly only adds fit, limitations, and quality judgment.
skill "mobile-react-native" {
input -> user goal + target files + boundaries + acceptance criteria
context -> Initial Setup / Directory Structure / Key Patterns
rules -> SKILL.md triggers / order / output contract
runtime -> no special runtime | read files, write/modify files | may access external network resources
guardrails -> usually needs no extra API key + small-sample validation + diff/log review
output -> copyable result + checklist + next iteration
} Mobile — React Native + Expo
Mobile app only. Do not apply to web-only projects. Verify stack matches
PROJECT_RULES.md. Record architecture decisions indocs/ai-dev/.
Initial Setup
npx create-expo-app@latest my-app --template blank-typescript
cd my-app
npx expo install expo-router expo-linking expo-constants
npx expo install nativewind tailwindcss
Directory Structure
app/
├── _layout.tsx # Root layout (navigation)
├── index.tsx # Home screen
├── (tabs)/
│ ├── _layout.tsx # Tab navigator
│ ├── home.tsx
│ └── profile.tsx
├── (auth)/
│ ├── login.tsx
│ └── signup.tsx
└── [id].tsx # Dynamic route
components/
├── ui/ # Reusable UI components
└── {feature}/ # Feature-specific components
lib/
├── api.ts # API client (fetch)
└── storage.ts # AsyncStorage helpers
types/
└── index.ts # Shared types
Key Patterns
- One component = max 150 lines. Split if exceeded
- Use RN core components first (
View,Text,Pressable,FlatList) - Props: define with TypeScript interfaces
- State: useState first, Zustand if complex
- HTTP requests: use built-in
fetchonly. Do NOT install Axios - Navigation: Expo Router (file-based, like Next.js App Router)
NativeWind Patterns
// Layout
<View className="flex-1 px-4">
<Text className="text-2xl font-bold text-gray-900 dark:text-white">Title</Text>
</View>
// Card
<View className="bg-white dark:bg-gray-800 rounded-xl p-4 shadow-sm">
<Text className="text-lg font-semibold">{title}</Text>
</View>
// List
<FlatList
data={items}
keyExtractor={(item) => item.id}
renderItem={({ item }) => <ItemCard item={item} />}
contentContainerClassName="gap-3 p-4"
/>
Running
npx expo start
# Phone: install "Expo Go" app, scan QR code
# iOS simulator: press "i" | Android emulator: press "a"
Building Screens
- Create
app/{path}.tsx - Build in order: layout -> components -> data connection
- Handle empty, loading, error states
- Test on Expo Go (scan QR with phone)
- ESLint pass
Source: ccivlcid/VibeHarness — distributed by TomeVault.
Decide Fit First
Design Intent
How To Use It
Boundaries And Review