Three.js debug profiler: blank canvases, runtime bugs and measured bottlenecks
Triage Three.js browser games — reproduce first, find the module that owns the failure, fix the root cause, retest the broken path; profile draw calls, triangles, textures, memory, shaders and bundle
- What
- Triage Three.js browser games — reproduce first, find the module that owns the failure, fix the root cause, retest the broken path; profile draw calls, triangles, textures, memory, shaders and bundle
- Cost
- Free
- Needs
- a Three.js browser game project to debug or profile — the skill is a guided workflow, not software to install
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — @majidmanzarpour's Three.js debug-and-profile skill for browser games: a lead-scoped workflow. Debug: reproduce first with the same command and URL the user had, read console/page/network errors, find the module that owns the failure (renderer, loop, camera, scene, assets, audio, input, physics, UI, base path), fix the root cause there, and retest the exact broken path — with an ordered triage playbook (blank canvas, asset and audio loading, loop/animation/physics, input and mobile) covering common causes like duplicate active loops, canvas display size mismatched with the drawing buffer, and wrong delta units. Profile: baseline one fixed production scenario, classify the bottleneck (CPU, GPU draw, fragment, vertex, memory or network), change one thing, re-measure the same scenario, confirm visuals and playability held — across draw calls, triangles, textures, memory, shader and post-processing cost, and bundle size. Report: root cause or measured bottleneck first, then files changed, baseline/post metrics, commands, screenshots, the broken path retested, and residual risks. Honest caveats: methodology plus a detailed debug playbook — reads as part of an agent-led project structure (a "lead" consolidates verification); the reference playbook's diagnostic shape is specific to this skill family. MIT licensed. Skill Harbor never reviews the code, review it yourself before use. Discovered via skills.sh.
Version:
Install
Prerequisites: a Three.js browser game project to debug or profile — the skill is a guided workflow, not software to install Install "Three.js debug profiler: blank canvases, runtime bugs and measured bottlenecks" for me. It teaches my agent @majidmanzarpour's debug-and-profile workflow: reproduce first with the user's exact command and URL, triage the owning module (renderer, loop, camera, scene, assets, audio, input, physics, UI), fix the root cause and retest the broken path, then profile a fixed scenario — classify the bottleneck (CPU, GPU draw, fragment, vertex, memory, network), change one thing, re-measure, confirm playability held — and report root cause, metrics and residual risks. MIT-licensed. Repository: https://github.com/majidmanzarpour/threejs-game-skills/blob/main/skills/threejs-debug-profiler/SKILL.md 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "threejs-debug-profiler". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. point the agent at the game project and the broken path/scenario to reproduce; nothing else — it's a methodology). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.