rn-styling
Styling patterns for React Native with NativeWind and BrandColors. Use when working with styles, themes, colors, responsive layouts, or platform-specific UI in Expo/React Native.
What this skill does
# React Native Styling
## Problem Statement
React Native styling differs fundamentally from web CSS. NativeWind bridges the gap but has its own rules. This codebase uses a hybrid approach: BrandColors for semantic colors, NativeWind for layout utilities.
---
## Pattern: BrandColors vs NativeWind Classes
**Rule:** Use BrandColors for semantic colors, NativeWind for layout/spacing.
```typescript
// ✅ CORRECT: Hybrid approach
<View className="flex-1 p-4 rounded-lg" style={{ backgroundColor: BrandColors.background }}>
<Text className="text-lg font-semibold" style={{ color: BrandColors.textPrimary }}>
Title
</Text>
</View>
// ❌ WRONG: Hardcoded hex colors (violation scanner blocks this)
<View className="flex-1 p-4 bg-[#1a1a2e]">
// ❌ WRONG: NativeWind color classes for brand colors
<View className="flex-1 p-4 bg-blue-500">
// ✅ ACCEPTABLE: NativeWind brand aliases (if configured)
<View className="flex-1 p-4 bg-brand-blue">
```
**When to use which:**
| Use Case | Approach |
|----------|----------|
| Brand colors (primary, secondary) | `BrandColors.primary` |
| Background colors | `BrandColors.background` |
| Text colors | `BrandColors.textPrimary`, `textSecondary` |
| Layout (flex, padding, margin) | NativeWind classes |
| Borders, radius | NativeWind classes |
| Shadows | Style object (NativeWind shadows limited on iOS) |
---
## Pattern: Theme-Aware Colors
**Problem:** Supporting light/dark mode with BrandColors.
```typescript
// BrandColors.ts exports both themes
import { BrandColors, BrandColorsDark } from '@/constants/BrandColors';
// Hook for current theme colors
import { useColorScheme } from 'react-native';
function useThemeColors() {
const colorScheme = useColorScheme();
return colorScheme === 'dark' ? BrandColorsDark : BrandColors;
}
// Component usage
function ThemedCard({ title }: { title: string }) {
const colors = useThemeColors();
return (
<View
className="p-4 rounded-lg"
style={{ backgroundColor: colors.cardBackground }}
>
<Text style={{ color: colors.textPrimary }}>{title}</Text>
</View>
);
}
```
---
## Pattern: NativeWind Class Ordering
**Problem:** Unlike web CSS, React Native doesn't cascade. Last class wins for conflicting properties.
```typescript
// Class order matters!
<View className="p-4 p-2" /> // p-2 wins (last)
<View className="p-2 p-4" /> // p-4 wins (last)
// Conditional classes - be explicit
<View className={`p-4 ${isCompact ? 'p-2' : ''}`} />
// If isCompact: "p-4 p-2" → p-2 wins ✅
// Merging className props
interface Props {
className?: string;
}
function Card({ className }: Props) {
// Parent classes override defaults (they come last)
return <View className={`p-4 rounded-lg ${className ?? ''}`} />;
}
// Usage: <Card className="p-8" /> → p-8 wins over p-4
```
---
## Pattern: Platform-Specific Styles
```typescript
import { Platform, StyleSheet } from 'react-native';
// Option 1: Platform.select
const styles = StyleSheet.create({
shadow: Platform.select({
ios: {
shadowColor: '#000',
shadowOffset: { width: 0, height: 2 },
shadowOpacity: 0.1,
shadowRadius: 4,
},
android: {
elevation: 4,
},
}),
});
// Option 2: Platform.OS check
<View style={Platform.OS === 'ios' ? styles.iosShadow : styles.androidShadow} />
// Option 3: NativeWind platform prefixes
<View className="ios:pt-12 android:pt-8" />
```
---
## Pattern: Safe Area Handling
```typescript
import { SafeAreaView } from 'react-native-safe-area-context';
import { useSafeAreaInsets } from 'react-native-safe-area-context';
// Option 1: SafeAreaView wrapper (simplest)
function Screen() {
return (
<SafeAreaView className="flex-1" edges={['top', 'bottom']}>
<Content />
</SafeAreaView>
);
}
// Option 2: Manual insets (more control)
function Screen() {
const insets = useSafeAreaInsets();
return (
<View
className="flex-1"
style={{ paddingTop: insets.top, paddingBottom: insets.bottom }}
>
<Content />
</View>
);
}
// Option 3: NativeWind safe area utilities (if configured)
<View className="flex-1 pt-safe pb-safe">
```
---
## Pattern: Keyboard Avoiding
```typescript
import { KeyboardAvoidingView, Platform } from 'react-native';
function FormScreen() {
return (
<KeyboardAvoidingView
className="flex-1"
behavior={Platform.OS === 'ios' ? 'padding' : 'height'}
keyboardVerticalOffset={Platform.OS === 'ios' ? 64 : 0} // Adjust for header
>
<ScrollView className="flex-1">
<TextInput />
<TextInput />
<SubmitButton />
</ScrollView>
</KeyboardAvoidingView>
);
}
```
---
## Pattern: Responsive Breakpoints
**Note:** NativeWind v2 breakpoints differ from web Tailwind.
```typescript
// NativeWind v2 breakpoints (based on window width)
// sm: 640px, md: 768px, lg: 1024px, xl: 1280px
// Responsive padding
<View className="p-2 sm:p-4 md:p-6" />
// Responsive flex direction
<View className="flex-col sm:flex-row" />
// Check screen size programmatically
import { useWindowDimensions } from 'react-native';
function ResponsiveLayout() {
const { width } = useWindowDimensions();
const isTablet = width >= 768;
return isTablet ? <TabletLayout /> : <PhoneLayout />;
}
```
---
## Pattern: Animated Styles
**Problem:** Avoiding re-renders with Animated values.
```typescript
import { Animated } from 'react-native';
function FadeInCard() {
// useRef to persist Animated.Value across renders
const fadeAnim = useRef(new Animated.Value(0)).current;
useEffect(() => {
Animated.timing(fadeAnim, {
toValue: 1,
duration: 300,
useNativeDriver: true, // Always use when animating opacity/transform
}).start();
}, []);
return (
<Animated.View
className="p-4 rounded-lg"
style={[
{ backgroundColor: BrandColors.cardBackground },
{ opacity: fadeAnim }, // Animated style in array
]}
>
<Text>Content</Text>
</Animated.View>
);
}
```
**Style arrays:** Combine static + animated styles.
```typescript
// ✅ CORRECT: Style array
style={[styles.card, { opacity: fadeAnim }]}
// ❌ WRONG: Spread (creates new object each render)
style={{ ...styles.card, opacity: fadeAnim }}
```
---
## Pattern: StyleSheet vs Inline
```typescript
// Use StyleSheet for:
// - Complex styles reused across renders
// - Styles with many properties
// - Performance-critical components
const styles = StyleSheet.create({
card: {
padding: 16,
borderRadius: 12,
backgroundColor: BrandColors.cardBackground,
shadowColor: '#000',
shadowOffset: { width: 0, height: 2 },
shadowOpacity: 0.1,
shadowRadius: 4,
},
});
// Use inline/NativeWind for:
// - Simple layout utilities
// - One-off styles
// - Conditional styles
<View className="flex-1 p-4" />
<View style={{ marginTop: dynamicValue }} />
```
---
## BrandColors Pattern
Create a centralized color constants file:
```typescript
// constants/BrandColors.ts
export const BrandColors = {
primary: '#...',
secondary: '#...',
background: '#...',
cardBackground: '#...',
textPrimary: '#...',
textSecondary: '#...',
// ... etc
};
export const BrandColorsDark = {
// Dark mode variants
};
```
### Recommended: Violation Scanner
Consider adding a violation scanner to block:
- Hardcoded hex colors (except allowed exceptions)
- Direct color strings
### NativeWind Notes
If using NativeWind v2 (not v4), note these differences:
- `className` prop on RN components
- Limited web Tailwind parity
- Some utilities unsupported
---
## Common Issues
| Issue | Solution |
|-------|----------|
| Color not applying | Check BrandColors import, verify theme context |
| NativeWind class ignored | Not all Tailwind utilities work - check v2 docs |
| Shadow not showing (iOS) | Use StyleSheet with shadowColor/Offset/Opacity/Radius |
| Shadow not showing (Android) | Use `elevation` property |
| Safe area not respecRelated 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.