@genex-ai/cli-demo 0.1.0

package/templates/skills/genex-threejs-procedural-vegetation/references/vegetation-systems.md

@@ -0,0 +1,37 @@
+# Vegetation Systems
+
+Use this reference for trees, plants, and grass in Genex games.
+
+## Species definition
+
+Declare:
+
+- height and width range;
+- trunk taper and bend;
+- branch count and angles;
+- canopy shape;
+- leaf size and clustering;
+- bark and leaf material identity;
+- wind response;
+- gameplay function such as cover, obstacle, collectible, or landmark.
+
+## Branch hierarchy
+
+- Emit trunk first with a stable radius curve.
+- Spawn primary branches from height bands.
+- Spawn secondary branches from primary branch frames.
+- Align leaf clusters to branch direction and local light bias.
+- Keep branch rings oriented with a stable frame to avoid twisting.
+
+## Placement
+
+- Use terrain slope, moisture, altitude, and gameplay zones as masks.
+- Leave readable paths and playable spaces.
+- Vary seed and scale without changing species identity.
+
+## Wind
+
+- Drive wind from a shared vector field.
+- Use lower-frequency bend for trunk and branches.
+- Use higher-frequency flutter for leaves.
+- Keep wind amplitude within the silhouette promised by collision/proxy shapes.

package/templates/skills/genex-threejs-procedural-vfx/SKILL.md

@@ -0,0 +1,31 @@
+---
+name: genex-threejs-procedural-vfx
+description: Author procedural real-time VFX for Genex Three.js games. Use for particles, trails, plasma, sparks, shockwaves, impacts, dissolving debris, ability effects, reentry wakes, event-timed visuals, effect pools, HDR emission hierarchy, and gameplay-readable spectacle.
+---
+
+# Genex Three.js Procedural VFX
+
+VFX should make player actions legible. Build effects as timed systems with
+budgets, not as one-off bursts.
+
+Read [references/vfx-systems.md](references/vfx-systems.md) for event timing,
+particles, trails, pooling, emission, and diagnostics.
+
+## Build order
+
+1. Define the event: cause, start, peak, decay, gameplay meaning, and interrupt
+   behavior.
+2. Split effect layers into core shape, particles, trails, light, distortion,
+   sound hooks, and decal/debris.
+3. Use seeded variation for repeatable runs.
+4. Pool high-count objects and dispose temporary resources.
+5. Keep emission intensities scene-relative.
+6. Expose debug controls for phase, layer toggles, counts, bounds, and overdraw.
+
+## Rules
+
+- Do not let bloom carry the shape of the effect.
+- Keep impact timing aligned to gameplay state.
+- Bound particle counts and lifetimes.
+- Use additive blending deliberately and inspect overdraw.
+- Provide low-quality versions for dense combat or mobile browsers.

package/templates/skills/genex-threejs-procedural-vfx/references/vfx-systems.md

@@ -0,0 +1,30 @@
+# Procedural VFX
+
+Use this reference for action effects in Genex games.
+
+## Event timeline
+
+- Anticipation: small cue before action when gameplay allows it.
+- Impact: strongest shape and brightness.
+- Decay: particles, trails, smoke, heat, or fragments.
+- Recovery: cleanup and return to readable scene state.
+
+## Layers
+
+- Shape layer: shockwave, shell, beam, ring, or volume.
+- Particle layer: sparks, embers, fragments, droplets, or dust.
+- Trail layer: motion history or projectile path.
+- Light layer: short-lived local light or emissive material.
+- Surface layer: decal, scorch, foam, or dissolve mask.
+
+## Pooling
+
+- Preallocate repeated particles or meshes.
+- Reuse materials and geometries.
+- Track active counts and peak counts.
+- Avoid per-frame allocation during dense events.
+
+## Diagnostics
+
+Expose layer toggles, overdraw view, bounding volumes, active counts, lifetime
+histograms, and final/no-bloom captures.

package/templates/skills/genex-threejs-raymarched-space-effects/SKILL.md

@@ -0,0 +1,30 @@
+---
+name: genex-threejs-raymarched-space-effects
+description: Build raymarched space effects for Genex Three.js games. Use for black holes, accretion disks, wormholes, curved-ray distortion, procedural star fields, bounded volumetric structures, relativistic-looking effects, and GPU effects needing numerical integration.
+---
+
+# Genex Three.js Raymarched Space Effects
+
+Use raymarched space effects for strong authored moments. Keep the math bounded,
+diagnosable, and tied to a game purpose.
+
+Read [references/space-effects.md](references/space-effects.md) for curved-ray,
+disk, wormhole, and budget patterns.
+
+## Build order
+
+1. Define the game role: landmark, hazard, portal, sky feature, set piece, or
+   background effect.
+2. Choose ray domain, bounds, step count, and quality tiers.
+3. Implement a no-distortion baseline first.
+4. Add ray steering, density, emission, and environment lookup.
+5. Add compositing with depth and exposure rules.
+6. Expose debug views for steps, ray exit, density, emission, and fallback.
+
+## Rules
+
+- Bound every integration loop.
+- Keep a cheaper fallback for low-end browsers.
+- Avoid unbounded brightness that breaks exposure.
+- Keep controls and collision separate from visual distortion.
+- Validate camera motion and edge cases near the effect.

package/templates/skills/genex-threejs-raymarched-space-effects/references/space-effects.md

@@ -0,0 +1,30 @@
+# Space Effects
+
+Use this reference for black holes, wormholes, and other space phenomena.
+
+## Curved rays
+
+- Start with a straight-ray environment lookup.
+- Add a bounded steering function.
+- Limit step count and maximum bend.
+- Record whether the ray hit, escaped, or exceeded bounds.
+
+## Accretion disks
+
+- Use radial density and temperature bands.
+- Add noise only as structured turbulence.
+- Keep disk emission bounded relative to scene exposure.
+- Allow the disk to be disabled for diagnostics.
+
+## Wormholes and portals
+
+- Define entry and exit transforms clearly.
+- Separate playable teleport state from visual distortion.
+- Provide edge masks and depth rules for compositing.
+
+## Validation
+
+- Capture near, design, and far distances.
+- Check fast camera rotation.
+- Inspect low-quality fallback.
+- Confirm the rest of the game remains readable around the effect.

package/templates/skills/genex-threejs-screen-space-ambient-occlusion/SKILL.md

@@ -0,0 +1,29 @@
+---
+name: genex-threejs-screen-space-ambient-occlusion
+description: Implement screen-space ambient occlusion for Genex Three.js games. Use for GTAO-style horizon sampling, bent normals, contact grounding, depth reconstruction, bilateral upsampling, temporal smoothing, halo diagnosis, and AO that supports readable form.
+---
+
+# Genex Three.js Screen-Space Ambient Occlusion
+
+Use AO to ground form, not to darken the whole image. It should be measurable,
+diagnosable, and easy to disable.
+
+Read [references/ambient-occlusion.md](references/ambient-occlusion.md) for
+sampling, reconstruction, filtering, and failure checks.
+
+## Build order
+
+1. Confirm the render pipeline owns depth and normal signals.
+2. Choose AO resolution, sample count, radius, falloff, and quality tiers.
+3. Reconstruct view-space position consistently.
+4. Generate occlusion and optional bent-normal direction.
+5. Filter with depth/normal-aware reconstruction.
+6. Expose debug views for depth, normals, raw AO, filtered AO, and final apply.
+
+## Rules
+
+- Keep AO radius tied to scene scale.
+- Avoid halos around silhouettes and thin geometry.
+- Do not apply AO twice through materials and post-processing.
+- Keep dynamic resolution and DPR changes safe.
+- Validate no-AO, raw-AO, and final-AO captures.

package/templates/skills/genex-threejs-screen-space-ambient-occlusion/references/ambient-occlusion.md

@@ -0,0 +1,29 @@
+# Ambient Occlusion
+
+Use this reference for screen-space contact grounding.
+
+## Inputs
+
+- Depth with known projection convention.
+- Normals in a documented space.
+- Camera near/far and projection matrix.
+- Optional velocity or history for temporal filtering.
+
+## Sampling
+
+- Use a stable noise pattern or rotated kernel.
+- Tie radius to world or view-space units.
+- Reduce samples for low quality tiers.
+- Keep thin geometry and silhouette cases visible in debug.
+
+## Filtering
+
+- Use bilateral filtering against depth and normal discontinuities.
+- Upsample from half resolution carefully.
+- Avoid bleeding occlusion across foreground/background edges.
+
+## Applying AO
+
+- Apply to indirect or ambient contribution, not direct sunlight.
+- Keep strength subtle enough that materials still read.
+- Provide a no-AO baseline for comparison.

package/templates/skills/genex-threejs-shadow-systems/SKILL.md

@@ -0,0 +1,30 @@
+---
+name: genex-threejs-shadow-systems
+description: Implement stable shadow systems for Genex Three.js games. Use for large worlds, directional cascades, cached clipmaps, terrain shadows, city scenes, moving cameras, targeted invalidation, quality tiers, texel stabilization, and readable contact shadows.
+---
+
+# Genex Three.js Shadow Systems
+
+Shadows ground gameplay and explain scale. They need stability more than maximum
+resolution everywhere.
+
+Read [references/shadow-systems.md](references/shadow-systems.md) for cascades,
+clipmaps, invalidation, and diagnostic captures.
+
+## Build order
+
+1. Define light direction, camera envelope, world scale, dynamic objects, and
+   target shadow budget.
+2. Choose basic maps, cascades, cached clipmaps, or contact-only shadows.
+3. Stabilize shadow texels for moving cameras.
+4. Separate static, dynamic, and invalidated casters.
+5. Add filtering and bias after acne/peter-panning diagnostics.
+6. Expose debug views for cascades, texel density, casters, receivers, and bias.
+
+## Rules
+
+- Do not chase every artifact by raising resolution.
+- Keep shadow distance tied to camera and gameplay scale.
+- Cache static shadows when the world allows it.
+- Validate sun angle extremes and fast camera motion.
+- Provide lower-cost tiers for weaker GPUs.

package/templates/skills/genex-threejs-shadow-systems/references/shadow-systems.md

@@ -0,0 +1,30 @@
+# Shadow Systems
+
+Use this reference for stable shadows in Genex games.
+
+## Cascades
+
+- Split camera depth into near, mid, and far ranges.
+- Allocate more resolution to gameplay-near shadows.
+- Stabilize cascade projections to shadow texels.
+- Show cascade boundaries in debug mode.
+
+## Cached clipmaps
+
+- Use clipmaps for large terrains or cities with slow-changing lighting.
+- Update only dirty regions.
+- Track invalidation from moving objects, time of day, or geometry edits.
+- Keep cache memory visible in diagnostics.
+
+## Bias and filtering
+
+- Tune normal bias and depth bias separately.
+- Inspect acne, peter-panning, and contact loss.
+- Filter only after the map coverage is correct.
+- Keep tiny decorative casters from ruining the budget.
+
+## Quality tiers
+
+- Low: shorter distance, fewer cascades, lower resolution.
+- Medium: stable near shadows and simplified far coverage.
+- High: more cascades or cached large-world coverage.

package/templates/skills/genex-threejs-skill-router/SKILL.md

@@ -0,0 +1,48 @@
+---
+name: genex-threejs-skill-router
+description: Route Genex 3D browser-game work to the smallest useful Three.js skill set. Use for new game scenes, graphics upgrades, visual reference matching, game-feel passes, render-pipeline work, publishing readiness, multiplayer-aware scene architecture, or requests spanning cameras, geometry, materials, atmosphere, water, VFX, shadows, post-processing, and validation.
+---
+
+# Genex Three.js Skill Router
+
+Use this skill first for broad 3D browser-game requests. Load only the skills
+that change the result; do not load the whole pack by default.
+
+Read [references/routing-map.md](references/routing-map.md) for the full routing
+map, execution order, and acceptance gate.
+
+## Route by system
+
+| Work needed | Load |
+| --- | --- |
+| camera rigs, authored shots, chase/orbit/side views, pointer look | `$genex-threejs-camera-direction` |
+| game-object timelines, springs, docking, staging, debris, loops | `$genex-threejs-procedural-animation` |
+| shared scalar/vector fields, masks, domain warping, procedural normals | `$genex-threejs-procedural-fields` |
+| PBR identity, atlas filtering, terrain wetness, dissolves, procedural normals | `$genex-threejs-procedural-materials` |
+| mesh writers, profile sweeps, semantic geometry, UVs, normals, material slots | `$genex-threejs-procedural-geometry` |
+| trees, foliage, roots, branching organisms, wind | `$genex-threejs-procedural-vegetation` |
+| buildings, modular kits, facade grammars, city assets | `$genex-threejs-procedural-architecture` |
+| planets, spherical terrain, craters, biomes, orbit-to-surface detail | `$genex-threejs-procedural-planets` |
+| sky, scattering, aerial perspective, atmosphere-aware lighting | `$genex-threejs-atmosphere-aerial-perspective` |
+| volumetric clouds, weather maps, raymarch budgets, cloud shadows | `$genex-threejs-volumetric-clouds` |
+| large FFT oceans, choppy waves, foam, spectral cascades | `$genex-threejs-spectral-ocean` |
+| analytic water, refraction, absorption, waves, crest foam | `$genex-threejs-water-optics` |
+| black holes, accretion disks, wormholes, curved-ray GPU effects | `$genex-threejs-raymarched-space-effects` |
+| particles, trails, plasma, shockwaves, timed event VFX | `$genex-threejs-procedural-vfx` |
+| accumulated frost, touch history, screen-space temporal masks | `$genex-threejs-temporal-surfaces` |
+| cascades, clipmaps, stable large-world shadows | `$genex-threejs-shadow-systems` |
+| GTAO, bent normals, contact grounding, AO diagnostics | `$genex-threejs-screen-space-ambient-occlusion` |
+| HDR bloom, selective emission, glow diagnostics | `$genex-threejs-bloom` |
+| exposure, tone mapping, color grading, LUTs | `$genex-threejs-exposure-color-grading` |
+| render-target ownership, pass ordering, depth/normal/history signals | `$genex-threejs-image-pipeline` |
+| fixed-view captures, seed sweeps, browser and GPU evidence | `$genex-threejs-visual-validation` |
+
+## Routing rules
+
+- Start from the playable game target: player verb, scene scale, camera distance,
+  input mode, and frame budget.
+- Build silhouette, motion, and material readability before adding image effects.
+- Prefer deterministic seeds and named controls for every procedural system.
+- Keep game logic, simulation state, visual fields, and screen-space passes
+  separated unless coupling is intentional.
+- Use `$genex-threejs-visual-validation` before declaring a visual task done.

package/templates/skills/genex-threejs-skill-router/references/routing-map.md

@@ -0,0 +1,53 @@
+# Routing Map
+
+Use this reference when a Genex game request touches multiple visual systems.
+
+## Three.js version and references
+
+For new Genex browser-game projects, use the current stable Three.js release and
+pin it exactly in `package.json`. As of June 26, 2026, that is
+`"three": "0.185.0"`.
+
+For existing projects, inspect and respect the installed Three.js version unless
+the user asks to upgrade. Use official Three.js docs first, then official
+examples as implementation references. Match examples to the project's installed
+Three.js release or branch, and do not blindly copy demo architecture.
+
+## Execution order
+
+1. Define the game contract: player verb, win/interaction loop, target device,
+   camera distance, scene scale, motion, and frame budget.
+2. Select the minimum scene-generation skills: geometry, materials, vegetation,
+   architecture, planets, water, clouds, or VFX.
+3. Add camera direction when framing, controls, transitions, or scale perception
+   affect play.
+4. Add procedural animation when object motion needs authored phases,
+   convergence, looping, or deterministic timelines.
+5. Add shared fields before writing multiple independent noise layers.
+6. Add lighting, atmosphere, and shadows only after the no-post baseline reads.
+7. Add image-pipeline, bloom, exposure, grading, or AO last.
+8. Validate in a real browser with fixed seeds, captures, interaction checks,
+   and performance evidence.
+
+## Acceptance gate
+
+A routed Genex scene is incomplete until it exposes:
+
+- deterministic or reproducible inputs;
+- camera and input controls suited to the game verb;
+- named perceptual parameters for the important visual systems;
+- debug views for generated fields, masks, or passes;
+- a no-post baseline that still communicates the subject;
+- a clear quality tier or render-budget knob when the effect is expensive;
+- browser evidence showing the canvas renders, moves, and responds to input.
+
+## Publish and multiplayer awareness
+
+Do not invent unavailable Genex service APIs. When preparing a game for Genex
+publishing or multiplayer, inspect the project first. Prefer clean boundaries:
+
+- renderer and scene setup isolated from transport/auth code;
+- deterministic spawn and simulation seeds;
+- serializable player/session state;
+- explicit asset loading paths;
+- one clear start function for local preview and hosted launch.

package/templates/skills/genex-threejs-spectral-ocean/SKILL.md

@@ -0,0 +1,30 @@
+---
+name: genex-threejs-spectral-ocean
+description: Build large procedural oceans for Genex Three.js games. Use for FFT-style wave spectra, multi-cascade wave bands, choppy displacement, derivatives, whitecaps, temporal foam, ocean shading, camera-scale transitions, and GPU-budgeted open-water scenes.
+---
+
+# Genex Three.js Spectral Ocean
+
+Use spectral oceans when the game needs large water bodies with convincing
+scale, directionality, and far-distance motion.
+
+Read [references/spectral-ocean.md](references/spectral-ocean.md) for wave
+cascades, foam, shading, and budget controls.
+
+## Build order
+
+1. Define wind direction, fetch, sea state, camera height range, and frame budget.
+2. Split wavelengths into cascades for far swell, mid waves, and near detail.
+3. Generate displacement, slope, curvature, and choppy derivatives from the
+   same wave state.
+4. Derive whitecaps and foam from slope, compression, and lifetime.
+5. Shade with sky reflection, Fresnel, absorption, and crest response.
+6. Expose no-post, normal, slope, foam, and cascade debug views.
+
+## Rules
+
+- Keep wave state deterministic for a seed and time value.
+- Do not fake large oceans with only scrolling normal maps.
+- Use quality tiers for cascade count, resolution, and update cadence.
+- Keep horizon and camera-relative origin stable.
+- Validate motion, not only still frames.

package/templates/skills/genex-threejs-spectral-ocean/references/spectral-ocean.md

@@ -0,0 +1,31 @@
+# Spectral Ocean
+
+Use this guide for large-scale ocean systems.
+
+## Cascades
+
+- Far cascade: long waves that define horizon rhythm.
+- Mid cascade: gameplay-scale wave shape and directionality.
+- Near cascade: filtered detail near the camera.
+- Keep each cascade's wavelength, amplitude, direction spread, and resolution
+  named in configuration.
+
+## Foam
+
+- Drive whitecaps from wave compression, steepness, slope, or impact events.
+- Store foam history when persistence matters.
+- Fade foam by age and water motion.
+- Keep foam masks inspectable separately from final shading.
+
+## Shading
+
+- Use Fresnel for view-dependent reflection.
+- Add absorption based on path length or depth approximation.
+- Reflect the sky or environment consistently with the scene exposure.
+- Keep crest scatter and emission-like highlights bounded.
+
+## Performance
+
+- Expose low, medium, and high ocean tiers.
+- Reduce update rate or resolution for background water.
+- Keep render-target inventory visible in debug output.

package/templates/skills/genex-threejs-temporal-surfaces/SKILL.md

@@ -0,0 +1,30 @@
+---
+name: genex-threejs-temporal-surfaces
+description: Build temporal screen-space and surface-history effects for Genex Three.js games. Use for touch history, frost clearing, burn-in masks, wet trails, accumulation buffers, ping-pong render targets, reduced-resolution blur, refraction masks, and interaction effects that persist over time.
+---
+
+# Genex Three.js Temporal Surfaces
+
+Use temporal surfaces when player interaction should leave a visible history.
+Keep the accumulated state inspectable and resettable.
+
+Read [references/temporal-surfaces.md](references/temporal-surfaces.md) for
+ping-pong buffers, history masks, blur, and reset rules.
+
+## Build order
+
+1. Define the surface history: input source, accumulation value, decay, clear
+   behavior, and gameplay meaning.
+2. Allocate explicit history targets.
+3. Write events into the history buffer with stable coordinates.
+4. Apply blur, diffusion, or erosion as separate passes.
+5. Composite the result into material, refraction, opacity, or color.
+6. Expose debug views for input, history, blur, decay, and final composite.
+
+## Rules
+
+- Provide a reset path for scene restart and level changes.
+- Keep history resolution and update cadence configurable.
+- Do not let temporal blur hide bad input mapping.
+- Clamp accumulated values and decay deterministically.
+- Validate pause/resume, resize, and device pixel ratio changes.

package/templates/skills/genex-threejs-temporal-surfaces/references/temporal-surfaces.md

@@ -0,0 +1,29 @@
+# Temporal Surfaces
+
+Use this reference for persistent interaction effects.
+
+## History buffer
+
+- Store history in one or more render targets.
+- Ping-pong read and write targets each update.
+- Keep UV or screen-space mapping explicit.
+- Reset on scene reload, resize, or level restart.
+
+## Event writing
+
+- Convert pointer, collision, projectile, or gameplay events into stable
+  coordinates.
+- Write shape, strength, radius, and timestamp or age.
+- Avoid direct dependence on frame rate.
+
+## Decay and blur
+
+- Apply decay before or after new input intentionally.
+- Use separable blur for large soft effects.
+- Keep low-resolution buffers from causing visible blockiness.
+- Expose unblurred and blurred views.
+
+## Compositing
+
+Temporal history can drive opacity, frost, wetness, scorch, refraction, glow, or
+normal distortion. Keep the visual role clear and provide a no-history fallback.

package/templates/skills/genex-threejs-visual-validation/SKILL.md

@@ -0,0 +1,32 @@
+---
+name: genex-threejs-visual-validation
+description: Validate Genex Three.js game visuals in a real browser. Use for fixed-view captures, no-post baselines, diagnostic mosaics, seed sweeps, camera-distance checks, temporal stability, interaction smoke checks, render-target inventories, GPU budgets, and evidence before claiming a 3D scene is done.
+---
+
+# Genex Three.js Visual Validation
+
+Validate the mechanism that creates the image, not just one attractive frame.
+For Genex games, also validate that the canvas runs and responds to input.
+
+Read [references/visual-validation.md](references/visual-validation.md) for the
+evidence checklist and rejection conditions.
+
+## Validation sequence
+
+1. Freeze seed, camera, time, quality tier, and viewport.
+2. Capture final image and no-post baseline.
+3. Capture system-specific diagnostic views.
+4. Check near, design, and far camera distances.
+5. Sweep at least one alternate seed or parameter extreme.
+6. Check motion, pause/resume, resize, and input response.
+7. Record frame timing and render-target inventory when available.
+8. Keep written invariants and known compromises.
+
+## Failure conditions
+
+- Approval relies on one screenshot.
+- The scene only reads with bloom, haze, or grading enabled.
+- Random seeds are not reproducible.
+- Debug views are unavailable for generated fields or passes.
+- Browser canvas is blank, off-frame, unresponsive, or broken after resize.
+- Temporal artifacts are judged only from still images.

package/templates/skills/genex-threejs-visual-validation/references/visual-validation.md

@@ -0,0 +1,42 @@
+# Visual Validation
+
+Use this checklist before considering a Genex 3D browser-game visual complete.
+
+## Evidence set
+
+- Fixed seed and configuration.
+- Fixed camera positions: near, design distance, and far.
+- Final capture.
+- No-post baseline.
+- Diagnostic views for major fields, masks, passes, or buffers.
+- Motion capture or interactive check for temporal effects.
+- Frame time and render-target inventory when available.
+
+## Browser checks
+
+- Canvas is nonblank.
+- Scene is framed correctly on desktop and mobile-sized viewports.
+- Resize keeps camera aspect and render targets correct.
+- Pointer, keyboard, touch, or gamepad input works for the intended controls.
+- Assets load without broken URLs.
+- The main loop can pause/resume without exploding `deltaTime`.
+
+## Diagnostic views
+
+Prefer simple toggles over hidden assumptions:
+
+- wireframe or bounds;
+- normals;
+- depth;
+- masks;
+- raw fields;
+- no-light and no-post modes;
+- individual post effects.
+
+## Rejection conditions
+
+- The result depends on a single lucky seed.
+- Fine detail shimmers in motion.
+- Camera movement reveals parallax or precision errors.
+- Post-processing hides unreadable geometry or materials.
+- Performance cost has no lower-quality escape hatch.

package/templates/skills/genex-threejs-volumetric-clouds/SKILL.md

@@ -0,0 +1,29 @@
+---
+name: genex-threejs-volumetric-clouds
+description: Build volumetric cloud systems for Genex Three.js games. Use for weather-shaped density, bounded raymarching, cloud layers, erosion detail, lighting cones, silver lining, temporal reconstruction, cloud shadows, quality tiers, and sky drama with controlled budgets.
+---
+
+# Genex Three.js Volumetric Clouds
+
+Clouds are expensive and scene-defining. Use them when they support scale,
+weather, mood, navigation, or gameplay.
+
+Read [references/volumetric-clouds.md](references/volumetric-clouds.md) for
+density, lighting, reconstruction, and budget controls.
+
+## Build order
+
+1. Define cloud role, altitude, coverage, wind, lighting, and performance tier.
+2. Create a weather map for coverage, type, height, and erosion.
+3. Raymarch inside bounded volumes or layers.
+4. Add lighting, phase response, self-shadow approximation, and silver lining.
+5. Add temporal reconstruction only after single-frame clouds are inspectable.
+6. Expose debug views for weather, density, steps, lighting, history, and shadow.
+
+## Rules
+
+- Bound raymarch distance and step count.
+- Keep quality tiers explicit.
+- Do not hide poor terrain or lighting behind cloud opacity.
+- Keep wind and cloud evolution deterministic.
+- Validate ghosting, shimmer, and camera motion.

package/templates/skills/genex-threejs-volumetric-clouds/references/volumetric-clouds.md

@@ -0,0 +1,30 @@
+# Volumetric Clouds
+
+Use this reference for cloud rendering in Genex games.
+
+## Density model
+
+- Weather map controls coverage, cloud type, and density scale.
+- Height profile controls base, body, and top falloff.
+- Detail erosion breaks up silhouettes.
+- Wind moves the sample domain consistently over time.
+
+## Raymarching
+
+- Intersect the camera ray with a bounded cloud volume.
+- Use coarse steps before expensive lighting.
+- Early-exit when transmittance is low.
+- Keep step count and resolution adjustable.
+
+## Lighting
+
+- Use sun direction from the scene.
+- Add forward-scattering emphasis for bright cloud edges.
+- Approximate self-shadow with short secondary samples or cached maps.
+- Keep cloud shadows optional and low-frequency.
+
+## Temporal behavior
+
+- Reprojection can reduce cost but must expose history diagnostics.
+- Validate camera cuts, fast turns, and pause/resume behavior.
+- Provide a single-frame mode for debugging.