Test environment system (authored DomeGradient and IBLGradient, component schemas) against the poke example using the iwsdk CLI.
82%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Passed
No findings from the security scan
Run 6 test suites covering authored environment verification, system registration, component registration, scene hierarchy, ECS data modification, and stability.
Configuration:
$IWSDK_REPO_ROOT/examples/pokeTool calls: every tool call is npx @iwsdk/cli <subcommand> [--input-json '<JSON>'] [--timeout <ms>], run from inside the example workspace (cwd $EXAMPLE_DIR). The CLI auto-discovers the IWSDK app root from cwd, so no path tricks are required. Run npx @iwsdk/cli mcp inspect from the example to discover available tools and their CLI subcommands.
<JSON> is a JSON object string. Omit --input-json if no arguments are needed.{ok, workspaceRoot, operation, result}. Parse it to check assertions.--timeout 20000 for operations that may take longer (reload, xr enter, screenshot).IMPORTANT: Run each Bash command one at a time. Parse the JSON output and verify assertions before moving to the next command. Do NOT chain multiple CLI commands together.
IMPORTANT: When the instructions say "wait N seconds", use sleep N as a separate Bash command.
IMPORTANT: Boolean values in ecs set-component must be actual JSON booleans (value: true), NOT strings (value: "true"). Strings silently fail to coerce.
cd $IWSDK_REPO_ROOT/examples/poke && npm run fresh:installWait for this to complete before proceeding.
Start the dev server as a background task using the Bash tool's run_in_background: true parameter:
cd $IWSDK_REPO_ROOT/examples/poke && npm run devIMPORTANT: This command MUST be run with run_in_background: true on the Bash tool — do NOT append & to the command itself.
Once the background task is launched, poll the output for Vite's ready message (up to 60s). You can also run npx @iwsdk/cli dev status from the example directory until state.running becomes true. You do not need to extract or manage the port yourself; subsequent commands resolve the active runtime through the CLI automatically.
If the server fails to start within 60 seconds, report FAIL for all suites and skip to Step 5.
npx @iwsdk/cli ecs systems 2>/dev/nullThis must return JSON with a list of systems. If it fails:
Run these commands in order:
Record the test start time immediately before reloading:
node -p 'Date.now()'Save the output as <test-start-ms>.
npx @iwsdk/cli browser reload --timeout 20000 2>/dev/null
Then: sleep 3
npx @iwsdk/cli xr enter --timeout 20000 2>/dev/null
Then: sleep 2
npx @iwsdk/cli browser logs --input-json '{"since":<test-start-ms>,"count":20,"level":["error","warn"]}' 2>/dev/null
Assert: No error-level logs.
Test 1.1: Find LevelRoot Dynamically
npx @iwsdk/cli ecs find --input-json '{"withComponents":["LevelRoot"]}' 2>/dev/nullAssert: Exactly 1 entity. Save its entityIndex as <root>.
Test 1.2: LevelRoot Has Environment Components
npx @iwsdk/cli ecs query --input-json '{"entityIndex":<root>,"components":["DomeGradient","IBLGradient"]}' 2>/dev/nullAssert: Both components are present with the values explicitly authored in
public/scenes/poke.iwsdk.scene.json:
DomeGradient defaults:
| Field | Expected Value |
|---|---|
sky | [0.2423, 0.6172, 0.8308, 1.0] (soft blue) |
equator | [0.6584, 0.7084, 0.7913, 1.0] (gray-blue) |
ground | [0.807, 0.7758, 0.7454, 1.0] (warm beige) |
intensity | 1.0 |
elevationDeg | 90 (default: sky pole straight up) |
azimuthDeg | 0 (default) |
dither | false (default) |
_needsUpdate | false (already processed) |
IBLGradient defaults:
| Field | Expected Value |
|---|---|
sky | [0.6902, 0.749, 0.7843, 1.0] (soft blue-gray — different from DomeGradient!) |
equator | [0.6584, 0.7084, 0.7913, 1.0] (same as DomeGradient) |
ground | [0.807, 0.7758, 0.7454, 1.0] (same as DomeGradient) |
intensity | 1.0 |
_needsUpdate | false |
Key detail: DomeGradient and IBLGradient have different sky defaults.
Test 2.1: EnvironmentSystem Present
npx @iwsdk/cli ecs systems 2>/dev/nullAssert:
domeGradients: 1, iblGradients: 1, domeTextures: 0, iblTextures: 0Test 3.1: All Environment Components Registered
npx @iwsdk/cli ecs components 2>/dev/nullAssert these components exist with correct schemas. ecs components reports
each field's type and default only:
| Component | Key Fields |
|---|---|
DomeGradient | sky (Color), equator (Color), ground (Color), intensity (Float32), elevationDeg (Float32, default 90), azimuthDeg (Float32, default 0), dither (Boolean, default false), _needsUpdate (Boolean) |
DomeTexture | src (FilePath), blurriness (Float32), intensity (Float32), rotation (Vec3), _needsUpdate (Boolean) |
IBLGradient | sky (Color), equator (Color), ground (Color), intensity (Float32), _needsUpdate (Boolean) |
IBLTexture | src (FilePath, default: "room"), intensity (Float32), rotation (Vec3), _needsUpdate (Boolean) |
Test 3.2: Field Limits in the Scene Capabilities
npx @iwsdk/cli scene capabilities --input-json '{"full":true}' 2>/dev/nullFind each component in result.componentSchemas by id and read its
fields. Assert:
DomeGradient.intensity.min is 0DomeGradient.elevationDeg has min: -90, max: 90DomeGradient.azimuthDeg has min: -180, max: 180IBLGradient.intensity.min is 0Test 4.1: Dome Mesh in Scene
npx @iwsdk/cli scene runtime-hierarchy --input-json '{"maxDepth":2}' 2>/dev/nullThe gradient dome mesh is added directly to the scene (not under LevelRoot). Look for an unnamed mesh node at the scene root level.
Test 5.1: Modify DomeGradient Sky Color
npx @iwsdk/cli ecs set-component --input-json '{"entityIndex":<root>,"componentId":"DomeGradient","field":"sky","value":"[1.0, 0.0, 0.0, 1.0]"}' 2>/dev/nullThen verify:
npx @iwsdk/cli ecs query --input-json '{"entityIndex":<root>,"components":["DomeGradient"]}' 2>/dev/nullAssert: sky = [1.0, 0.0, 0.0, 1.0]
Test 5.2: Tilt the DomeGradient Without _needsUpdate
npx @iwsdk/cli ecs set-component --input-json '{"entityIndex":<root>,"componentId":"DomeGradient","field":"elevationDeg","value":"30"}' 2>/dev/nullThen: sleep 1
npx @iwsdk/cli scene render-stats 2>/dev/nullAssert: result.sceneEnvironment.background is
{ type: "dome-gradient", elevationDeg: 30, azimuthDeg: 0, dither: false, ... }
and its sky is [1, 0, 0, 1] from Test 5.1. Neither edit set
_needsUpdate; DomeGradient and IBLGradient apply edits on the next frame.
Test 5.3: Modify IBLGradient Intensity
npx @iwsdk/cli ecs set-component --input-json '{"entityIndex":<root>,"componentId":"IBLGradient","field":"intensity","value":"2.0"}' 2>/dev/nullThen: sleep 1
npx @iwsdk/cli scene render-stats 2>/dev/nullAssert: result.sceneEnvironment.imageBasedLighting is
{ type: "ibl-gradient", intensity: 2, ... }.
npx @iwsdk/cli browser logs --input-json '{"since":<test-start-ms>,"count":30,"level":["error","warn"]}' 2>/dev/nullAssert: No application-level errors or warnings. Pre-existing 404 resource errors from page load are acceptable.
Kill the dev server:
cd $IWSDK_REPO_ROOT/examples/poke && npx @iwsdk/cli dev downOutput a summary table:
| Suite | Result |
|--------------------------|-----------|
| 1. Authored Environment | PASS/FAIL |
| 2. System Registration | PASS/FAIL |
| 3. Component Registration| PASS/FAIL |
| 4. Scene Hierarchy | PASS/FAIL |
| 5. ECS Data Modification | PASS/FAIL |
| 6. Stability | PASS/FAIL |If any suite fails, include which assertion failed and actual vs expected values.
If at any point a transient error occurs (server crash, WebSocket timeout, connection refused, etc.) that is NOT caused by a source code bug:
cd $IWSDK_REPO_ROOT/examples/poke && npx @iwsdk/cli dev downOnly give up after one retry attempt per suite. If the same suite fails twice, mark it FAIL and continue to the next suite.
_needsUpdateDomeGradient and IBLGradient apply ecs set-component edits on the next frame.
DomeTexture and IBLTexture apply an edit only after _needsUpdate is set to
true.
The _needsUpdate flag is consumed by the EnvironmentSystem and reset to false. The response may already show newValue: false.
LevelSystem does not synthesize dome or IBL components. Their absence is
meaningful, and each scene must author the background and image-based lighting
it wants on the level root. The poke fixture scene includes both gradient
components explicitly.
Never cache entity indices across page reloads. Always re-discover via npx @iwsdk/cli ecs find.
When setting boolean fields (like _needsUpdate) via npx @iwsdk/cli ecs set-component, the value must be a JSON boolean (true), not a string ("true"). Strings silently fail.
facebook/immersive-web-sdk
52f0f50
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.