القائمة
Dùng khi gặp bug, test failure, hoặc unexpected behavior — LUÔN tìm root cause trước khi fix
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Expert in building 3D experiences for the web - Three.js, React Three Fiber, Spline, WebGL, and interactive 3D scenes. Covers product configurators, 3D portfolios, immersive websites, and bringing depth to web experiences. Use when: 3D website, three.js, WebGL, react three fiber, 3D experience.
Game art principles — art style, color theory, animation principles, asset pipeline
Game design principles — core loop, GDD, player psychology, difficulty balancing, progression
Orchestrator game — route to implementation skill (pxhopencode) + principle-based sub-skill (agent-skills-hub)
Mobile game principles — touch input, battery, thermal, app stores, monetization
Multiplayer game principles — networking architecture, synchronization, security, matchmaking
| name | process-systematic-debugging |
| description | Dùng khi gặp bug, test failure, hoặc unexpected behavior — LUÔN tìm root cause trước khi fix |
ALWAYS find root cause before attempting fixes. Symptom fixes are failure.
NO FIXES WITHOUT ROOT CAUSE INVESTIGATION FIRST
Chưa hoàn thành Phase 1 → không được propose fix
Mọi technical issue: test failures, production bugs, unexpected behavior, performance problems, build failures.
ĐẶC BIỆT khi:
| Excuse | Reality |
|---|---|
| "Bug đơn giản, nhìn là biết" | Nhìn = guess. Root cause mới là truth |
| "Không có thời gian, fix đại đi" | Fix đại = 3 lần thời gian sau này debug lại |
| "Log là đủ, không cần reproduction" | Không reproduce → không biết fix đúng |
| "Fix 1 dòng, không cần typecheck" | Typecheck catch 70% bugs |