ux-testing

Automate browser-based UX testing for Three.js games via Chrome DevTools MCP.

Updated Mar 21, 2026

Search Tags:#automation #performance #lighthouse #three.js #ux-testing #browser-testing #chrome-devtools

Ready to run

npx skills add https://github.com/pwretmo/deep-underworld --skill ux-testing

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ux-testing
Source: https://github.com/pwretmo/deep-underworld/tree/main/.github/skills/ux-testing
Command: npx skills add https://github.com/pwretmo/deep-underworld --skill ux-testing

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Streamlines browser-based UX testing for Three.js games by enforcing Chrome DevTools MCP workflows and automated interaction checks.

Core Features & Use Cases

Automated UI testing using Chrome DevTools MCP for gameplay pages
Screenshots, keyboard input handling, console monitoring, performance tracing, memory analysis, Lighthouse audits
Dispatching fix workers for UX issues and coordinating reproducible test runs

Quick Start

Start the dev server and run automated UX tests against http://localhost:5173?autoplay

Frequently Asked Questions about ux-testing

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

FAQPage Schema

How do I automate UX testing for Three.js games in the browser?▼

Automated UX testing for Three.js games is handled by navigating gameplay pages, capturing screenshots, monitoring console logs, and executing performance traces via Chrome Devtools to ensure stable browser interactions.

Can I run Lighthouse audits and memory snapshots on a localhost dev server?▼

Yes, Lighthouse audits and memory snapshots can be executed against a dev server running at localhost:5173, automatically analyzing performance metrics and memory usage during automated browser testing workflows.

What do I need to run automated browser-testing workflows for Three.js gameplay?▼

Automated browser-testing requires the Chrome DevTools MCP environment, an active dev server running at http://localhost:5173, and the autoplay mode flag enabled to operate safely and repeatably.

What is the best way to capture performance traces and console logs during Three.js gameplay?▼

The best way to capture performance traces and console logs is by using Chrome DevTools MCP workflows, which automate page navigation, monitor console output, and record performance traces during Three.js gameplay interactions.

Does automated UX testing dispatch fix workers for detected console and performance issues?▼

Yes, automated UX testing dispatches fix workers to resolve detected UX issues, coordinating reproducible test runs that monitor console logs, analyze memory, and execute performance traces for comprehensive browser testing.

Why does automated UX testing require the autoplay mode flag for Three.js games?▼

The autoplay mode flag is required for automated UX testing to ensure safe and repeatable browser interactions, allowing Chrome DevTools MCP to autonomously navigate gameplay pages and execute performance traces without manual input.