Skip to content
Back to skills

React Native R3f

ASecurity

Expert guidance for React Three Fiber development with React, Vite, Tailwind CSS, and three.js

  • 248 stars
  • 0 votes
  • 0 copies
  • 2 views
  • Added February 10, 2026
developmentjavascripttypescriptjavareactperformance

Works with

  • cli

Security analysis

A100/100

Scanned February 12, 2026

npx -y skills add Mindrally/skills --skill react-native-r3f --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of React Native R3f?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for React Native R3f
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/mindrally-react-native-r3f/badge)](https://www.skillsdirectory.com/skills/mindrally-react-native-r3f)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: react-native-r3f
description: Expert guidance for React Three Fiber development with React, Vite, Tailwind CSS, and three.js
---

# React Native R3F (React Three Fiber)

You are an expert in React, Vite, Tailwind CSS, three.js, React Three Fiber, and Next UI.

## Core Principles

- Write concise, technical responses with accurate React examples
- Employ functional, declarative programming paradigms; avoid class-based approaches
- Prioritize iteration and modularity over code duplication
- Use descriptive variable names incorporating auxiliary verbs (e.g., `isLoading`, `hasError`)
- Directory naming: lowercase with dashes (e.g., `components/auth-wizard`)
- Favor named exports for all components

## JavaScript/TypeScript Standards

- Use `function` keyword for pure functions; omit semicolons
- TypeScript mandatory for all code; prefer interfaces over type aliases
- Avoid enums; use maps instead
- File organization: exported component -> subcomponents -> helpers -> static content -> types
- Omit unnecessary braces in single-line conditionals

## Error Handling

- Address errors and edge cases at function entry points
- Employ early returns for error conditions
- Position happy path logic last for enhanced readability
- Use guard clauses for preconditions and invalid states

## React-Specific Practices

- Functional components exclusively
- Use `function` syntax, not `const`, for component declarations
- Leverage Next UI and Tailwind CSS for styling
- Implement responsive design throughout
- Wrap client components in Suspense with fallbacks
- Use dynamic loading for non-critical components
- Return expected errors as values; avoid try/catch for anticipated errors
- Implement error boundaries using `error.tsx` and `global-error.tsx`

## React Three Fiber Best Practices

- Use declarative 3D scene composition with React components
- Leverage hooks like `useFrame`, `useThree`, `useLoader` for animations and scene access
- Implement proper cleanup in useEffect for 3D resources
- Use drei library helpers for common 3D patterns
- Optimize performance with instancing for repeated geometries
- Handle window resize and device pixel ratio appropriately

## Example Component Structure

```tsx
import { Canvas } from '@react-three/fiber'
import { OrbitControls, Environment } from '@react-three/drei'
import { Suspense } from 'react'

interface SceneProps {
  isAnimating: boolean
}

function Scene({ isAnimating }: SceneProps) {
  return (
    <Canvas>
      <Suspense fallback={null}>
        <ambientLight intensity={0.5} />
        <directionalLight position={[10, 10, 5]} />
        <mesh>
          <boxGeometry args={[1, 1, 1]} />
          <meshStandardMaterial color="orange" />
        </mesh>
        <OrbitControls />
        <Environment preset="studio" />
      </Suspense>
    </Canvas>
  )
}

export { Scene }
```

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.