Procedural Planets
Build a planet as a coupled field system evaluated on a unit direction. The same geological causes must drive geometry, color, roughness, normal, atmosphere handoff, and distance filtering.
This skill contains exemplary examples and assets beyond descriptive guidance,
they're worth studying, referencing, or even copying. Use them sufficiently
when relevant and do NOT blindly skip them.
Required build order
- Establish planet-space direction, radius, sea level, and world-unit scale.
- Build macro silhouette fields before any surface material.
- Add named geological structures: continents, basins, ridges, craters, lava fields, or ice.
- Derive slope, cavity, altitude, latitude, exposure, and shoreline fields.
- Classify broad biomes from those causes.
- Derive displacement, color, roughness, and normal from the shared field bundle.
- Filter bands by represented mesh scale and camera altitude.
- Couple the material to atmosphere and lighting using the same planet transform.
Read references/planet-field-and-atmosphere-systems.md for terrain, biome, gas-giant, material, altitude-LOD, and atmosphere-handoff mechanisms, including a known CPU/GPU field-parity failure mode.
Read the procedural planet surface implementation
and its shared terrain field
for undeformed sphere coordinates, shared CPU/GLSL terrain, coupled biome and
material causes, derivative bump, and altitude-filtered detail.
Non-negotiable constraints
- Domain-warp tangentially and renormalize; do not distort the sphere radially.
- Craters need floor, wall, rim, and optional ejecta—not dark circles.
- Continents and biomes must be region fields, not isolated threshold bubbles.
- Geometry displacement and shader normals must describe the same height function.
- Close detail may disappear with altitude; the macro silhouette may not.
- Expose individual field views and a displacement exaggeration mode.
Completion test
The body must remain intentional in:
- unlit silhouette;
- flat albedo with no atmosphere;
- grazing directional light;
- orbit view;
- close approach;
- biome-mask and normal-only views;
- at least three seeds without losing the chosen planetary identity.
Routing boundary
Use $threejs-procedural-fields for a reusable field bundle without a complete
body, and $threejs-atmosphere-aerial-perspective for scattering independent
of planet generation. This skill owns the coupled planetary surface.
1---2name: threejs-procedural-planets3description: Author procedural planetary bodies in Three.js. Use for spherical terrain, continents, ridges, craters, biome masks, coastlines, material variation, analytic normals, altitude LOD, and bodies that must hold up from orbit through close approach.4---5
6# Procedural Planets
7
8Build a planet as a coupled field system evaluated on a unit direction. The same geological causes must drive geometry, color, roughness, normal, atmosphere handoff, and distance filtering.
9
10This skill contains exemplary examples and assets beyond descriptive guidance,
11they're worth studying, referencing, or even copying. Use them sufficiently
12when relevant and do NOT blindly skip them.
13
14## Required build order
15
161. Establish planet-space direction, radius, sea level, and world-unit scale.
172. Build macro silhouette fields before any surface material.
183. Add named geological structures: continents, basins, ridges, craters, lava fields, or ice.
194. Derive slope, cavity, altitude, latitude, exposure, and shoreline fields.
205. Classify broad biomes from those causes.
216. Derive displacement, color, roughness, and normal from the shared field bundle.
227. Filter bands by represented mesh scale and camera altitude.
238. Couple the material to atmosphere and lighting using the same planet transform.
24
25Read [references/planet-field-and-atmosphere-systems.md](references/planet-field-and-atmosphere-systems.md) for terrain, biome, gas-giant, material, altitude-LOD, and atmosphere-handoff mechanisms, including a known CPU/GPU field-parity failure mode.
26
27Read the [procedural planet surface implementation](examples/procedural-planet-surface/planet-system.js)
28and its [shared terrain field](examples/procedural-planet-surface/terrain-field.js)
29for undeformed sphere coordinates, shared CPU/GLSL terrain, coupled biome and
30material causes, derivative bump, and altitude-filtered detail.
31
32## Non-negotiable constraints
33
34- Domain-warp tangentially and renormalize; do not distort the sphere radially.
35- Craters need floor, wall, rim, and optional ejecta—not dark circles.
36- Continents and biomes must be region fields, not isolated threshold bubbles.
37- Geometry displacement and shader normals must describe the same height function.
38- Close detail may disappear with altitude; the macro silhouette may not.
39- Expose individual field views and a displacement exaggeration mode.
40
41## Completion test
42
43The body must remain intentional in:
44
45- unlit silhouette;
46- flat albedo with no atmosphere;
47- grazing directional light;
48- orbit view;
49- close approach;
50- biome-mask and normal-only views;
51- at least three seeds without losing the chosen planetary identity.
52
53## Routing boundary
54
55Use `$threejs-procedural-fields` for a reusable field bundle without a complete
56body, and `$threejs-atmosphere-aerial-perspective` for scattering independent
57of planet generation. This skill owns the coupled planetary surface.
gabrielmoreira