Index of every page on this site: llms.txt
All skills
enzed avatar

/r3f-interaction

@4a11805
by Nicolas Zulloenzed/r3f-skills138 stars
7
Run it yourself

Implement React Three Fiber pointer events, picking, dragging, keyboard input, and camera controls. Use for scene interaction and event propagation, rather than animation or physics simulation itself.

Use this Skill: https://skilld.dev/gh/enzed/r3f-skills/r3f-interaction

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈54 tokens for metadata: the name and description. ≈1.2k when used: this file.

Description uses 2.7% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈218 characters, or 2.7%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

React Three Fiber interaction

Check installed Fiber, Drei, and input-library versions first. Examples target Fiber 9 / React 19. Choose camera movement, object movement, and UI input owners before connecting handlers.

Selectable object

Mount beneath Canvas. Keep accessible DOM controls outside Canvas for important actions; mesh pointer handlers alone do not provide keyboard access.

import { useState } from 'react'
import { OrbitControls } from '@react-three/drei'

export default function Example() {
  const [selected, setSelected] = useState(false)
  return (
    <>
      <mesh
        name="selectable-box"
        onClick={(event) => {
          event.stopPropagation()
          setSelected((value) => !value)
        }}
      >
        <boxGeometry />
        <meshStandardMaterial color={selected ? 'gold' : 'coral'} />
      </mesh>
      <OrbitControls makeDefault />
    </>
  )
}

Event semantics

  • R3F raycasts objects with handlers and delivers hits by distance, then bubbles through ancestors. event.object is the hit object; event.eventObject is the object owning the handler.
  • stopPropagation() blocks delivery to farther hits as well as ancestors. It changes event delivery; it does not avoid raycasts already performed. Calling it can immediately trigger pointerout on previously hovered objects behind the hit.
  • event.point is world space. Clone values you retain and convert into the parent's local space before assigning local transforms. A plane intersection or depth reference is needed to map a 2D drag into 3D.
  • Handle Canvas onPointerMissed for background deselection; distinguish clicks from drags using the event's movement information and the application's gesture policy.
  • Pointer capture is additive to hit testing in R3F. Capture/release via event.target.setPointerCapture(event.pointerId) and the matching release method; also handle cancellation/lost capture.
  • Camera movement beneath a stationary pointer may require state.events.update() to refresh hover results. Call it only when needed, not as a blanket extra raycast every frame.
  • Use simpler hit proxies or layer filtering for expensive picking. Do not rely on visual transparency alone to prevent intersections.

Controls and drag ownership

  • Use OrbitControls for orbiting; use CameraControls when scripted transitions and richer camera behavior are needed. Check the installed Drei/underlying controls version before copying props or methods.
  • Drei controls manage frame updates and demand invalidation. Avoid mounting multiple active controls on the same camera without explicit coordination.
  • makeDefault exposes a controls instance to helpers that coordinate with it. TransformControls can suspend default controls while dragging; verify that custom controls are also disabled/restored correctly.
  • For object dragging, choose Drei DragControls/PivotControls/TransformControls according to required constraints. Distinguish controlled matrices from automatic transforms; do not apply both to the same object.
  • For custom drags, store initial transforms, capture the pointer, project onto a chosen plane, and restore camera controls on pointerup, cancellation, and unmount. Honor touch-action requirements on the actual event target.
  • Shared DOM event sources need a coordinate prefix consistent with the event target and canvas rectangle. Test scrolling and overlays; blindly selecting client coordinates can introduce offsets.

Keyboard and continuous input

  • Drei KeyboardControls provides named actions. Read its getter inside useFrame for movement; subscribe only for discrete events and clean up subscriptions.
  • Normalize diagonal movement if speed must remain constant; multiply visual movement by delta. For a physics body, send input to physics-step logic instead of moving its mesh directly.
  • Clear held input on focus loss and respect text-field focus. Pointer lock/fullscreen/audio may require an explicit user gesture.
  • Use refs for high-frequency pointer positions and React state for semantic events. Avoid adding lodash or a store solely to throttle one handler; clean up timers if throttling is warranted.
  • ScrollControls creates a scroll context; useScroll belongs below it. Its normalized offset/delta are not pixel distances.

Verify

Test overlapping meshes, nested groups, background deselection, dragging outside the canvas, touch, cancellation, focus loss, and keyboard alternatives. Verify camera controls recover after dragging.

Sources

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts2mo5 checks · Risk SAFE
  • Gen Agent Trust Hub2mo

    This skill provides technical documentation and code examples for implementing interactions in React Three Fiber scenes, including pointer events, dragging, and camera controls. The content is strictly informational and contains no security risks.

  • Socket2mo

    No alerts

  • Snyk2mo

    Risk: LOW · No issues

  • Runlayer8mo

    1 file scanned · No issues

  • ZeroLeaks7mo

    Score: 93/100 · 2 sections analyzed

Signed by skilld at 4a11805. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub last week.

Steadyupdated 3 months ago
  • react-three-fiber
  • r3f
  • pointer-events
  • camera-controls
  • interaction
  • three.js
  • 3d
  • gestures
  • raycasting
  • gizmos

README badge

README badge for enzed/r3f-skills/r3f-interaction

Implements pointer events, camera controls, transform gizmos, and keyboard input for React Three Fiber scenes. Covers click detection, hover effects, OrbitControls, drag handlers, and selection via raycasting on 3D meshes.

Generated from the current SKILL.md.

Does this skill cover pointer events on meshes?
Yes. It covers click, double-click, pointer over/out, pointer down/up, wheel, and touch events, plus event object properties like intersection point, distance, UV coordinates, and raycasting control.
What camera control options are included?
The skill documents OrbitControls, MapControls, FlyControls, FirstPersonControls, PointerLockControls, CameraControls, TrackballControls, and ArcballControls from @react-three/drei.
Does this cover transform/gizmo controls?
Yes. It includes TransformControls (translate/rotate/scale), PivotControls, and DragControls, with examples of disabling orbit controls during interaction.
Are keyboard and drag controls covered?
Yes. KeyboardControls from @react-three/drei with key mapping is documented, plus drag support via useDrag from @use-gesture/react and DragControls from @react-three/drei.

Generated from the current SKILL.md. These answers refresh after source changes.