사용 방법
- 설치 명령을 복사하고 자신의 에이전트 환경에 설치하기 전에 소스 패키지를 확인하세요.
- 필요한 도구, 인증 정보, 지원 환경은 원본 문서에서 확인하세요.
- 입력과 원하는 산출물을 설명하고 출처와 결과를 대조하세요.
npx skills add https://github.com/leanentropy/threejs-phaser-game-skills --skill threejs-game-ui-designer시작 전 확인
- 설치에는 모델 구독, API 한도, 파일 접근 권한이 포함되지 않습니다.
- 별점 수와 설치 수는 활동 지표이며 독립적인 품질·보안 검증이 아닙니다.
원본 저장소의 제목, 예시, 코드, 표, 링크, 이미지를 유지해 표시합니다.
Three.js Game UI Designer
Purpose
Make game UI intentional, readable, responsive, and genre-specific.
Workflow
Load references/ui-patterns.md as the first action when designing HUDs, menus, overlays, pause/win/lose screens, settings, touch controls, typography, responsive layout, safe areas, text fit, icons, or UI/world cohesion. Track it in a reference ledger with yes/no, path, and failure reason. Do not mark the UI phase complete while this reference is skipped for interface work.
Load references/checklists/game-ui-quality.md, references/checklists/hud-readability.md, and references/checklists/responsive-ui-fit.md before claiming UI/HUD/menu work is complete. Load references/checklists/mobile-input.md when touch controls or mobile safe areas are in scope.
Load references/prompt-templates.md only when the user asks for reusable prompts, a UI pass prompt, or a task template.
Load threejs-image-generator when logos, icons, GUI art, faction marks, menu backgrounds, decals, or 2D HUD assets would improve quality. Use threejs-3d-generator only for 3D menu/showcase objects or diegetic 3D UI props, not normal flat HUD elements.
- Capture/inspect desktop and mobile screenshots.
- Inventory UI states: gameplay, pause, settings, fail/retry, win/milestone, loading, touch controls.
- Define hierarchy: survival/status, objective, feedback, flavor.
- Replace utility stat cards with authored clusters, meters, badges, icons, alerts, and modal states.
- Use stable dimensions, safe-area padding, text-fit constraints, hover/pressed/focus/disabled states.
- Wire UI to game state, not duplicated rules.
- Verify text fit, overlap, safe areas, touch targets, responsive screenshots, and real state changes.
Common Failure Modes
- Generic dashboard/stat-card HUD.
- UI covers player/threats.
- Text shifts/clips on mobile.
- Decorative panels reduce readability.
- Touch controls look right but do not emit intents.
Final Response
Report the reference ledger, UI state checklist, UI intent, states covered, files changed, screenshots, text-fit/overlap checks, safe-area/touch-target evidence, controls, and remaining risks.
