菜单
Build a mathwave room that simulates a CPU integer/cell grid and displays it via a DataTexture + fullscreen display shader — Wolfram CA, Abelian sandpile, Hopfield network, Conway-style automata. Template — src/wolfram.js (+ the fullscreen-quad display pattern from src/fractal.js).
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Build a mathwave room that runs CPU physics/simulation each frame and renders real Three.js 3D geometry — N-body, boids, cloth (Verlet), spiking neural nets, Kohonen SOM, L-systems, RL cartpole, double pendulum. PerspectiveCamera + OrbitControls. Template — src/nbody.js.
Build a mathwave room that is a GPU field simulation on swapped float render targets (ping-pong) — reaction-diffusion, wave/ripple equations, Schrödinger wavefunctions, Lattice-Boltzmann fluids, Lenia/neural cellular automata, Physarum. Template — src/reaction.js.
Conventions for adding a room to the mathwave Three.js gallery — file layout, the buildless ES-module/import-map setup, kiosk navigation, the shared common.js engine, and the ROOMS registry. Use this first whenever creating or modifying any mathwave room.
Apply the PlayStation-1 rendering aesthetic to a mathwave room — low-res framebuffer + nearest upscale + 4x4 Bayer ordered dither + 15-bit color crunch, plus optional vertex snapping. Reusable module src/ps1.js. Best on rooms with real 3D FORM (fractals), not abstract data clouds.
Build a mathwave room that is a GPU fragment-shader raymarcher/SDF — fractals (mandelbulb, mandelbox, menger, quaternion Julia), volumetrics (nebula), Truchet/metaballs. Single fullscreen quad, all geometry in the fragment shader, custom uCamPos orbit. Template — src/fractal.js.
The verification discipline for mathwave rooms — how to confirm a room ACTUALLY renders before claiming it works, using agent-browser plus window.__err / window.__diag canaries. Critically, node --check and a green fps reading are NOT sufficient. Use before committing any room.
| name | grid-cells-room |
| description | Build a mathwave room that simulates a CPU integer/cell grid and displays it via a DataTexture + fullscreen display shader — Wolfram CA, Abelian sandpile, Hopfield network, Conway-style automata. Template — src/wolfram.js (+ the fullscreen-quad display pattern from src/fractal.js). |
Templates: src/wolfram.js for the grid/stepping pattern, src/fractal.js for
the fullscreen-quad display shader. Working siblings: sandpile.js, hopfield.js.
Keep the simulation as a typed array on the CPU, upload it to a DataTexture each
frame, and draw it with one fullscreen display shader that maps cell values to colors.
Use this (instead of GPU ping-pong) when the rule is integer/branchy/global and easier
to express in JS — sandpile toppling, Hopfield sign(Σ W·s), CA lookups.
const W = 257, H = 257;
const grid = new Int32Array(W*H); // your state
const pix = new Uint8Array(W*H*4); // RGBA upload buffer
const tex = new THREE.DataTexture(pix, W, H, THREE.RGBAFormat); // UnsignedByteType
tex.minFilter = tex.magFilter = THREE.NearestFilter; // crisp cells
// each frame: step the grid, write colors into pix, then:
tex.needsUpdate = true;
Display it on a PlaneGeometry(2,2) + OrthographicCamera, sampling tex. Either
write final colors into pix in JS, or upload raw values and map to a palette in the
shader (more flexible). Letterbox to a square in the shader so the grid isn't stretched.
W_ij = (1/N)Σ_μ ξ_i^μ ξ_j^μ, W_ii=0; recall by
s_i ← sign(Σ_j W_ij s_j); energy E = -½ Σ W s s descends. Capacity ≈ 0.14N, so
store few patterns or recall fails.Distinct vivid colors per cell value on near-black (deep blue / teal / amber / magenta), not purple-dominant.
bindRange for growth/noise/speed; setVariantCycler for grid size / pattern / scheme;
a reset button. window.__err handler + window.__diag. Then verify-on-screen.