react-native-component-generator
Generates React Native components with platform-specific code, TypeScript support, and mobile-first patterns. Use when user asks to "create React Native component", "generate RN component", "scaffold mobile component", or "create cross-platform component".
What this skill does
# React Native Component Generator
Generates React Native components with platform-specific optimizations, TypeScript support, and mobile best practices.
## When to Use
- "Create a React Native Button component"
- "Generate mobile component"
- "Scaffold cross-platform component"
- "Create RN component with platform code"
- "Generate native module wrapper"
## Instructions
### 1. Gather Requirements
Ask for:
- Component name (PascalCase)
- Platform support (iOS, Android, or both)
- Props and their types
- Native modules needed
- Styling approach (StyleSheet, styled-components, etc.)
- Animations needed
### 2. Generate Base Component
**Basic Functional Component:**
```typescript
// components/Button/Button.tsx
import React from 'react';
import {
TouchableOpacity,
Text,
StyleSheet,
TouchableOpacityProps,
ViewStyle,
TextStyle,
} from 'react-native';
interface ButtonProps extends TouchableOpacityProps {
title: string;
onPress: () => void;
variant?: 'primary' | 'secondary' | 'outline';
size?: 'small' | 'medium' | 'large';
}
export const Button: React.FC<ButtonProps> = ({
title,
onPress,
variant = 'primary',
size = 'medium',
style,
...props
}) => {
return (
<TouchableOpacity
style={[
styles.button,
styles[variant],
styles[size],
style,
]}
onPress={onPress}
activeOpacity={0.7}
{...props}
>
<Text style={[styles.text, styles[`${variant}Text`]]}>
{title}
</Text>
</TouchableOpacity>
);
};
const styles = StyleSheet.create({
button: {
borderRadius: 8,
justifyContent: 'center',
alignItems: 'center',
},
primary: {
backgroundColor: '#007AFF',
},
secondary: {
backgroundColor: '#6c757d',
},
outline: {
backgroundColor: 'transparent',
borderWidth: 1,
borderColor: '#007AFF',
},
small: {
paddingVertical: 8,
paddingHorizontal: 16,
},
medium: {
paddingVertical: 12,
paddingHorizontal: 24,
},
large: {
paddingVertical: 16,
paddingHorizontal: 32,
},
text: {
fontSize: 16,
fontWeight: '600',
},
primaryText: {
color: '#ffffff',
},
secondaryText: {
color: '#ffffff',
},
outlineText: {
color: '#007AFF',
},
});
```
**Component with State and Hooks:**
```typescript
// components/SearchInput/SearchInput.tsx
import React, { useState, useCallback, useEffect } from 'react';
import {
TextInput,
View,
StyleSheet,
TextInputProps,
TouchableOpacity,
ActivityIndicator,
} from 'react-native';
import { Ionicons } from '@expo/vector-icons';
interface SearchInputProps extends Omit<TextInputProps, 'onChangeText'> {
onSearch: (query: string) => void;
onClear?: () => void;
debounceMs?: number;
loading?: boolean;
}
export const SearchInput: React.FC<SearchInputProps> = ({
onSearch,
onClear,
debounceMs = 300,
loading = false,
placeholder = 'Search...',
...props
}) => {
const [query, setQuery] = useState('');
useEffect(() => {
const timer = setTimeout(() => {
if (query) {
onSearch(query);
}
}, debounceMs);
return () => clearTimeout(timer);
}, [query, debounceMs, onSearch]);
const handleClear = useCallback(() => {
setQuery('');
onClear?.();
}, [onClear]);
return (
<View style={styles.container}>
<Ionicons name="search" size={20} color="#666" style={styles.icon} />
<TextInput
style={styles.input}
value={query}
onChangeText={setQuery}
placeholder={placeholder}
placeholderTextColor="#999"
autoCapitalize="none"
autoCorrect={false}
{...props}
/>
{loading && <ActivityIndicator size="small" color="#007AFF" />}
{query.length > 0 && !loading && (
<TouchableOpacity onPress={handleClear}>
<Ionicons name="close-circle" size={20} color="#666" />
</TouchableOpacity>
)}
</View>
);
};
const styles = StyleSheet.create({
container: {
flexDirection: 'row',
alignItems: 'center',
backgroundColor: '#f0f0f0',
borderRadius: 10,
paddingHorizontal: 12,
height: 44,
},
icon: {
marginRight: 8,
},
input: {
flex: 1,
fontSize: 16,
color: '#000',
},
});
```
### 3. Platform-Specific Code
**Using Platform Module:**
```typescript
// components/Header/Header.tsx
import React from 'react';
import { View, Text, StyleSheet, Platform, StatusBar } from 'react-native';
interface HeaderProps {
title: string;
}
export const Header: React.FC<HeaderProps> = ({ title }) => {
return (
<View style={styles.container}>
<Text style={styles.title}>{title}</Text>
</View>
);
};
const styles = StyleSheet.create({
container: {
paddingTop: Platform.select({
ios: 50,
android: StatusBar.currentHeight || 0,
default: 0,
}),
paddingBottom: 10,
paddingHorizontal: 16,
backgroundColor: '#007AFF',
...Platform.select({
ios: {
shadowColor: '#000',
shadowOffset: { width: 0, height: 2 },
shadowOpacity: 0.1,
shadowRadius: 4,
},
android: {
elevation: 4,
},
}),
},
title: {
fontSize: 20,
fontWeight: 'bold',
color: '#fff',
...Platform.select({
ios: {
fontFamily: 'System',
},
android: {
fontFamily: 'Roboto',
},
}),
},
});
```
**Using Platform-Specific Files:**
```typescript
// components/DatePicker/DatePicker.ios.tsx
import React from 'react';
import { DatePickerIOS } from '@react-native-community/datetimepicker';
interface DatePickerProps {
date: Date;
onDateChange: (date: Date) => void;
}
export const DatePicker: React.FC<DatePickerProps> = ({ date, onDateChange }) => {
return <DatePickerIOS date={date} onDateChange={onDateChange} mode="date" />;
};
```
```typescript
// components/DatePicker/DatePicker.android.tsx
import React, { useState } from 'react';
import { TouchableOpacity, Text, StyleSheet } from 'react-native';
import DateTimePicker from '@react-native-community/datetimepicker';
interface DatePickerProps {
date: Date;
onDateChange: (date: Date) => void;
}
export const DatePicker: React.FC<DatePickerProps> = ({ date, onDateChange }) => {
const [show, setShow] = useState(false);
const onChange = (_event: any, selectedDate?: Date) => {
setShow(false);
if (selectedDate) {
onDateChange(selectedDate);
}
};
return (
<>
<TouchableOpacity onPress={() => setShow(true)} style={styles.button}>
<Text>{date.toLocaleDateString()}</Text>
</TouchableOpacity>
{show && (
<DateTimePicker value={date} mode="date" display="default" onChange={onChange} />
)}
</>
);
};
const styles = StyleSheet.create({
button: {
padding: 12,
backgroundColor: '#f0f0f0',
borderRadius: 8,
},
});
```
```typescript
// components/DatePicker/index.ts
export { DatePicker } from './DatePicker';
```
### 4. Animated Components
**Basic Animation:**
```typescript
// components/FadeIn/FadeIn.tsx
import React, { useEffect, useRef } from 'react';
import { Animated, ViewProps } from 'react-native';
interface FadeInProps extends ViewProps {
duration?: number;
delay?: number;
}
export const FadeIn: React.FC<FadeInProps> = ({
children,
duration = 300,
delay = 0,
style,
...props
}) => {
const fadeAnim = useRef(new Animated.Value(0)).current;
useEffect(() => {
Animated.timing(fadeAnim, {
toValue: 1,
duration,
delay,
useNativeDriver: true,
}).start();
}, [fadeAnim, duration, delay]);
return (
<Animated.View style={[style, { opacity: fadeAnim }]} {...props}>
{children}
</Animated.View>
);
};
```
**Complex Animation:**
```typescript
// components/SlideUp/SlideUp.tsx
import React, { useEffect, useRef } from 'react';
import { Animated, Dimensions } from 'react-native';
const { height } = Dimensions.get('window');
interfRelated in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.