← LeaderboardThe Skill Leaderboard

threejs-procedural-fields

Build coherent procedural scalar and vector fields for Three.js materials and geometry. Use for terrain, planets, wear, biomes, clouds, water masks, displacement, roughness, normals, domain warping, and any visual where several channels must derive from shared causes.

Description awaits a fresh source check.

Published by scottstts ↗scottstts/Threejs-Awesome-Graphics-Agent-Skills

Try your first task

Design a shared procedural field bundle

Start a fresh conversation. Replace the highlighted placeholders.

Use the threejs-procedural-fields skill to draft a compact field contract for [target surface]. Define stable coordinates, macro and meso structure, named derived causes, the material channels that reuse them, and one diagnostic view for each named field. Keep the result to a design plan rather than a full implementation.

Required inputs

  • Target surface, such as terrain, a planet, water, or a material
  • Coordinate frame and intended scale
  • Required output channels, such as color, roughness, normal, displacement, emission, or scattering

Previously published starter task based on a pinned source version; check the source and required inputs before running. Task evidence ↗

SKILL.md

name: threejs-procedural-fieldsdescription: Build coherent procedural scalar and vector fields for Three.js materials and geometry. Use for terrain, planets, wear, biomes, clouds, water masks, displacement, roughness, normals, domain warping, and any visual where several channels must derive from shared causes.

Procedural Fields

Do not start by stacking noise. Start by defining the fields the object physically or stylistically needs.

Field contract

Before shader code, write a field bundle:

coordinates
  → macro form
  → meso structure
  → derived causes
  → material channels

Example:

sphereDirection
  → warpedDirection
  → elevation + ridges + craterDepth
  → slope + cavity + latitude + moisture
  → biome + color + roughness + bump

Required workflow

  1. Choose coordinates that remain stable under camera and object motion.
  2. Lock real or perceptual scale for each frequency band.
  3. Create named primary fields. Never hide the whole look in one expression.
  4. Derive secondary fields from causes: slope from normals, shore from sea-level distance, wear from exposure, dirt from cavity.
  5. Reuse the same fields across color, roughness, normal, displacement, emission, and scattering.
  6. Add debug output for every named field.
  7. Filter high-frequency fields by derivatives, tessellation density, or camera distance.

Read references/field-stack-recipes.md before implementation. It records sphere, terrain, water, and structured-placement field contracts plus common parity defects.

Read the procedural planet surface for a shared CPU/GLSL field bundle whose height, continents, climate, biomes, roughness, and normals remain independently inspectable.

Non-negotiable rules

  • Independent noise per channel produces visual soup. Share structure.
  • Domain warp the coordinates, not every result.
  • Warp spherical coordinates tangentially, then renormalize.
  • Use different frequency bands for silhouette, regions, surface breakup, and micro-normal.
  • Do not displace geometry with frequencies the mesh cannot represent.
  • Keep categorical masks broad enough to avoid isolated “bubble” regions.
  • Parameter names must describe perception: ridgeWidth, coastBlend, cavityDarkening, not noise3Amount.

Routing boundary

Use this skill when the shared field model is the task. Use $threejs-procedural-materials when the task is channel assembly and material response, and $threejs-procedural-planets when the deliverable is a complete planetary body.