Use when building, optimizing, and securing expo router v4 mobile interfaces, native bridges, touch gestures, and offline states.
Scanned 9/29/2026
npx -y skills add Harmitx7/tribunal-kit --skill expo-router-v4 --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Expo Router V4?
Add the live security badge to your README โ it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/harmitx7-expo-router-v4)More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.
---
name: expo-router-v4
description: "Use when building, optimizing, and securing expo router v4 mobile interfaces, native bridges, touch gestures, and offline states."
version: 6.0.0
last-updated: 2026-09-29
skills:
- mobile-developer
- mobile-design
- react-specialist
tools: Read, Grep, Glob, Bash, Edit, Write
scripts-binding:
- .agent/scripts/lint_runner.js
- .agent/scripts/verify_all.js
---
# Expo Router v4 & React Native New Architecture
## Mandatory Pre-Flight Context Inspection
Before reading, generating, or refactoring code in the `expo-router-v4` domain, inspect these 5 critical parameters:
1. **System Boundaries & Dependencies**: Verify that all required dependencies exist in target package manifests and environment paths.
2. **Runtime Context & Platform Invariants**: Confirm target platform constraints (Node.js, Browser, Mobile OS, Edge runtime) before applying APIs.
3. **Execution Guardrails**: Identify potential side-effects, state mutations, and unhandled asynchronous exceptions.
4. **Validation & Type Contracts**: Validate input data schemas and strict type constraints across all module interfaces.
5. **Observability & Proof of Execution**: Ensure execution produces tangible verification signals (terminal output, tests, metrics).
## Activation Boundaries
- **Activate when:** Use when building, optimizing, and securing expo router v4 mobile interfaces, native bridges, touch gestures, and offline states.
- **DO NOT activate when:** The task falls outside the `expo-router-v4` domain or is managed by a different dedicated specialist agent.
## ๐ Multi-Pass Execution Protocol
| Pass | Phase | Core Action | Adaptive Depth |
|:---|:---|:---|:---|
| **Pass 1** | **Understand** | Deconstruct the user's explicit objective, implicit requirements, and platform constraints. | Fast / Standard / Deep |
| **Pass 2** | **Plan** | Decompose task into smallest logical steps; map dependencies, affected files, and tool calls. | Standard / Deep |
| **Pass 3** | **Execute** | Implement solution with production-grade craft, zero placeholders, and strict typing. | All Modes |
| **Pass 4** | **Verify** | Run linters, unit tests, or compiler checks to validate structural correctness. | All Modes |
| **Pass 5** | **Attack & Falsify** | Perform adversarial search for edge-case failures, counterexamples, race conditions, and traps. | Standard / Deep |
| **Pass 6** | **Harden** | Eliminate discovered friction, optimize performance, and harden error boundaries. | Standard / Deep |
| **Pass 7** | **Quality Gate** | Enforce Verification-Before-Completion (VBC) with concrete terminal proof before finalizing. | All Modes |
---
## ๐ ๏ธ Technical Architecture & Reference Recipes
## Layout Navigation Architecture (`app/_layout.tsx`)
```tsx
import { Stack } from 'expo-router';
import { StatusBar } from 'expo-status-bar';
import { SafeAreaProvider } from 'react-native-safe-area-context';
export default function RootLayout() {
return (
<SafeAreaProvider>
<StatusBar style="light" />
<Stack
screenOptions={{
headerStyle: { backgroundColor: '#0f172a' },
headerTintColor: '#f8fafc',
animation: 'slide_from_right',
}}
>
<Stack.Screen name="index" options={{ title: 'Feed' }} />
<Stack.Screen name="modal" options={{ presentation: 'modal' }} />
</Stack>
</SafeAreaProvider>
);
}
```
## Native Haptic Touch Button Component
```tsx
import * as Haptics from 'expo-haptics';
import { Pressable, Text, PressableProps } from 'react-native';
interface TouchButtonProps extends PressableProps {
label: string;
}
export function TouchButton({ label, onPress, ...props }: TouchButtonProps) {
return (
<Pressable
{...props}
onPress={e => {
Haptics.impactAsync(Haptics.ImpactFeedbackStyle.Light);
onPress?.(e);
}}
className="px-5 py-3 bg-indigo-600 rounded-xl active:scale-95 transition-transform"
>
<Text className="text-white font-medium text-center">{label}</Text>
</Pressable>
);
}
```
## ๐จ Edge-Case & Failure Mode Matrix
| Scenario | Risk | Production Mitigation |
|:---|:---|:---|
| **Empty or Null Inputs** | Unhandled exception or unexpected rendering collapse | Enforce fallback guards, optional chaining, and explicit empty state handlers |
| **Network Timeout / Latency** | Hanging operations or duplicate side-effects | Implement bounded abort controllers, exponential backoff, and idempotency keys |
| **Concurrency / Race Conditions** | Stale state overwrite or inconsistent data mutations | Use atomic transactions, mutex locking, or cancel-on-resubmit controls |
| **Invalid Schema / Malformed Payload** | Downstream runtime errors or security injection | Validate boundary payloads with Zod/Pydantic schemas prior to execution |
| **Resource / Memory Saturation** | OOM errors, frame drops, or memory leaks | Clean up listeners, cancel active timers, and enforce pagination/virtualization |
## ๐ค LLM-Specific Traps Table
| Anti-Pattern | What AI Commonly Does Wrong | What Is Actually Correct |
|:---|:---|:---|
| **JS Thread Animation Lag** | Driving gestures and scrolling physics on the React Native JS thread | Use React Native Reanimated worklets running directly on the UI thread |
| **Missing Keyboard Offset** | Forms hidden behind native software keyboard on iOS/Android | Wrap form views in KeyboardAvoidingView with platform-calibrated behavior |
| **Uncached Image Flooding** | Rendering raw image URLs in list items without memory caching | Use FastImage or Expo Image with disk cache policies and thumbnail previews |
## ๐๏ธ Tribunal Verification & Guardrails
**Active Reviewers:** `mobile-reviewer` ยท `frontend-reviewer` ยท `type-safety`
**Slash Command:** `/review` or `/tribunal-full`
### ๐ฌ Evidence Standard (Tri-State Verification)
Every finding, audit statement, or completion claim must classify its factual certainty:
- **`[OBSERVED]`**: Directly confirmed in the codebase or verified via executed terminal command.
- **`[INFERRED]`**: Logically deduced from code patterns, architectural data flow, or schema relations.
- **`[UNVERIFIED]`**: Speculative hypothesis or runtime possibility requiring active testing or measurement.
### โ
Pre-Flight Self-Audit Checklist
```
โ
Do touch targets satisfy the 44x44px minimum touch boundary standard?
โ
Are gesture handlers and native animations offloaded via Reanimated worklets on the UI thread?
โ
Are keyboard avoiding views, safe areas, and notch offsets handled?
โ
Is offline storage and state hydration handled with optimistic sync?
โ
Did I verify compatibility across iOS, Android, and varying screen densities?
```
### ๐ Verification-Before-Completion (VBC) Protocol
**CRITICAL:** You must follow a strict "evidence-based closeout" state machine.
- โ **Forbidden:** Declaring a task complete because the output "looks correct."
- โ
**Required:** You are explicitly forbidden from finalizing any task without providing **concrete evidence** (terminal output, passing test suites, compiler success, or equivalent operational proof) that your output works as intended.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!