IMMERSIVE WEB SIMULATION FORGE
EXAMPLE ARCHIVEv0.7

A project archive

Interactive browser
examples.

Examples built while developing the Immersive Web Simulation Forge: browser worlds, simulation interfaces, and experimental scenes grouped by generation.

ARTIFACTS11
GENERATIONS04
RUNTIME LAYERSWEBGL / CANVAS / DOM
FEATURED EXAMPLE / 03 FIELD 01 — PELAGIC
01 / PRODUCT STRUCTUREworkflow and feedback 02 / DOMAIN NOTESmodel and limitations 03 / RUNTIME CHECKSlifecycle and measurement

Installation

Install Forge.

Choose the host first. Each host supports a direct skill install and a plugin marketplace install.

CLAUDE CODE

Claude Code

Direct skill install
npx skills add ictseoyoungmin/immersive-web-simulation-forge --agent claude-code
Plugin marketplace
/plugin marketplace add ictseoyoungmin/immersive-web-simulation-forge
/plugin install immersive-web-simulation-forge@immersive-web-simulation-forge
/reload-plugins
CODEX CLI

Codex CLI

Direct skill install
npx skills add ictseoyoungmin/immersive-web-simulation-forge --agent codex
Plugin marketplace
codex plugin marketplace add ictseoyoungmin/immersive-web-simulation-forge
codex plugin add immersive-web-simulation-forge@immersive-web-simulation-forge

The example archive

Selected examples.

Open an example to run it in a new tab. Each card lists its profile, claim level, and the validation record currently stored with the project.

11 SURFACES ONLINE

Project structure

Three areas
kept separate.

The Forge documents the user workflow, the level of domain evidence, and the runtime behavior as separate parts of each project.

01

PRODUCT STRUCTURE

Define the user workflow.

Record the starting state, first useful action, visible consequence, completion step, and recovery path for the chosen product profile.

ENTRY → ACTION → RESULT
02

DOMAIN NOTES

State what the model supports.

Units, assumptions, solver behavior, validation references, tolerances, and limitations are recorded before quantitative claims are displayed.

MODEL → EVIDENCE → LIMITS
03

RUNTIME CHECKS

Record runtime behavior.

Lifecycle, persistence, cancellation, wall-clock frame timing, display fidelity, resource bounds, and package contents are checked separately.

STATE → FRAME → PACKAGE

BUILD WITH THE FORGE

Start with a brief.
Document the result.

Open the skill notes