jsgui3-lab-experimentation

Validates jsgui3 behavior questions through lab experiments and distills findings into documentation.

1|Updated Sep 12, 2025
One-click install
npx skills add https://github.com/metabench/copilot-dl-news --skill jsgui3-lab-experimentation-metabench
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: jsgui3-lab-experimentation
Source: https://github.com/metabench/copilot-dl-news/tree/main/docs/agi/skills/jsgui3-lab-experimentation
Command: npx skills add https://github.com/metabench/copilot-dl-news --skill jsgui3-lab-experimentation-metabench

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When working with the jsgui3 UI framework, teams often face uncertain questions about event delegation, control activation, MVVM patterns, mixins, and helpers. This Skill provides a structured workflow to answer those questions empirically using the repo's lab experiments instead of guesswork, then preserves the validated findings as durable documentation. ## Core Features & Use Cases - Prior-art discovery: Searches existing docs and session records before running any experiment to avoid duplicate work. - Deterministic experiment execution: Runs targeted check scripts, delegation suites, and Puppeteer scenario suites to confirm jsgui3 behavior across SSR, client activation, and browser event semantics. - Minimal experiment authoring: Guides creation of new numbered experiments with hypothesis READMEs, assertion-based check scripts, and manifest registration when no existing coverage exists. - Knowledge distillation: Promotes validated results into Skills, Patterns, and subsystem guides so findings persist beyond a single session. - Use Case: A developer is unsure whether jsgui3 event delegation handles stopPropagation correctly during control activation. The Skill locates the relevant delegation scenarios, runs the shared browser runner, and records the confirmed behavior in the repo's pattern registry. ## Quick Start Ask the assistant to verify a specific jsgui3 behavior question by running the relevant lab experiment checks and recording the validated result in the repo documentation.

Frequently Asked Questions about jsgui3-lab-experimentation

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify jsgui3 event delegation behavior?▼

Run the shared delegation suite runner with the relevant scenario numbers, such as node jsgui3-experiments/experiments/run-delegation-suite.js --scenario=005,006. It reuses one browser and page to test capture, bubble, selector matching, and stopPropagation semantics.

How do I test jsgui3 control activation with SSR and real interactivity?▼

Use the Puppeteer scenario suite runner, for example node tools/dev/ui-scenario-suite.js with a control harness suite. It validates DOM linking, event listeners, and state updates in a single browser without the cost of full Jest E2E tests.

How do I create a new jsgui3 lab experiment?▼

Create a numbered directory under jsgui3-experiments/experiments with a README stating the hypothesis and expected result, plus a check.js with deterministic assertions. Then register it in manifest.json and the lab README table.

When should I escalate a jsgui3 question instead of running a lab experiment?▼

Escalate when behavior only reproduces with SSR plus activation plus bundling and no harness covers it, when new shared harness utilities are needed, or when performance instrumentation beyond a simple check is required.

Does the lab workflow require checking existing documentation first?▼

Yes. The procedure starts by searching guides and session records with the md-scan tool before running experiments, ensuring prior findings are reused instead of duplicating research effort.