A commit to the Skills repository adds three browser-game workflows under its game development category, expanding that section from 22 to 25 skills. According to the updated README, the additions cover build-point-cloud-scan, build-lens-raindrops, and build-3d-character-selector, targeting playable Three.js and WebGL projects.1
How the two-pass raindrop shaders work
According to the build-lens-raindrops guide, the effect takes a rendered 3D scene color target with clamp-to-edge sampling and runs two WebGL 2 fragment shaders. Builders first draw drop-field.frag into a linearly filtered RGBA8 target at half the scene resolution to store droplet slopes and height, then composite the scene with refract.frag. The guide notes that keeping the HUD in a later pass or DOM layer preserves text readability, while speed ramps can drive wetness.1
Building mesh-driven point-cloud cages
The build-point-cloud-scan skill ships an ES module, scan-cage.mjs, whose buildScanCage function takes packed XYZ vertex positions, optional triangle indices, and a positive cell size, according to the source code. It clusters vertices into cells, averages their positions, and connects cells along source triangle edges, returning typed arrays of point positions and edge indices. In the driving game example cited in the guide, a character handoff sweeps bottom-to-top over roughly 1.2 seconds, while a district pulse spans 215 world units over 6.4 seconds.1
From full-body references to a 3D roster
For build-3d-character-selector, the accompanying production guide documents starting from approved identity portraits or existing GLB models. In the driving game's workflow, Seedream 5.5 generated full-body references that fed Tripo H3.1 through Higgsfield, before builders decimated the masters in Blender into browser copies. The skill's stage workflow aligns each model to one canonical rest transform, adds rotation and keyboard controls, and uses request tokens to prevent stale loads during rapid roster switching.1
Stated limits for generated characters
The character production guide states two limits for generated casts. Because the driving game's master models were unrigged and relied on a small vertex-shader deformation for breathing and gaze, builders must add a skeleton and paint weights on a working copy for walking, gesturing, or driving. It also notes that a single reference image leaves the back design to the generator.1