This skill should be used when the user asks to 'debug', 'fix bug', 'investigate error', 'why is it broken', 'trace root cause', 'find the bug', or needs systematic bug investigation and fixing with verification-driven methodology using ralph loops.

Master debugging techniques for Vue.js, Pinia, and cached state issues. Identify reactivity problems, memory leaks, performance bottlenecks, and complex state synchronization issues with systematic troubleshooting approaches.

<!-- SKILL CHAINING: After completing debugging work, Claude MUST invoke related skills -->

Internal skill used by dev-implement during Phase 5 of /dev workflow. NOT user-facing - should only be invoked by dev-ralph-loop inside each implementation iteration. Handles Task agent spawning with TDD enforcement and two-stage review (spec compliance + code quality).

Package and dependency management patterns across ecosystems (npm, pip, cargo, maven). Covers lockfiles, semantic versioning, dependency security scanning, update strategies, monorepo workspaces, transitive dependencies, and avoiding dependency hell.

**Announce:** "Using dev-design (Phase 4) to propose implementation approaches and obtain user approval."

Run isolated mux desktop (Electron) instances (temp MUX_ROOT + free ports)

ring:dev-devops

Create consistent, reproducible development environments across all machines.

All workspace packages use the `@orient-bot/` namespace:

Standardized development environment configuration including tools, IDE settings, and automation for consistent developer experience.

Unified execution engine for all development workflows. Progressive disclosure for phase execution, quick features, story completion, and scaffolding. Integrates with artifact-tracking and meatycapture-capture. Use when running /dev:execute-phase, /dev:quick-feature, /dev:implement-story, /dev:complete-user-story, or /dev:create-feature commands.

REQUIRED Phase 2 of /dev workflow after dev-brainstorm. This skill should be used when the user asks to 'explore the codebase', 'map architecture', 'find similar features', 'discover test infrastructure', 'trace execution paths', 'identify code patterns', or needs to understand WHERE code lives and HOW it works before implementation. Launches parallel explore agents and returns prioritized key files list.

>-

ring:dev-feedback-loop

DEBUG keyboard shortcuts not working, conflicting hotkeys, and event handling issues. Fix when Ctrl+Z, Ctrl+S, or other shortcuts fail. Use for global keyboard handlers, event conflicts, and shortcut key debugging.

MASTER Pinia task store debugging covering synchronization, CRUD operations, state persistence, IndexedDB conflicts, advanced state management, and complex store architecture. Fix when tasks don't save, disappear unexpectedly, don't update in UI, backup systems read wrong data, store actions fail, or advanced performance issues occur. CRITICAL: All store fixes MUST be tested with Playwright before claiming success.

DEBUG Pomodoro timer state issues, incorrect countdown behavior, and timer synchronization problems. Fix when timer won't start, time display is wrong, or timer gets stuck. Use for timer state management, countdown logic, and session persistence.

Human-in-the-loop iterative development. Use when requirements will emerge during implementation, decisions need human approval at each step, or work will span multiple sessions with frequent feedback loops. Creates problem statement, decisions log, runbook, and progress tracking.

REQUIRED Phase 5 of /dev workflow. Orchestrates per-task ralph loops with delegated TDD implementation.

ring:dev-implementation

개발 환경(폴더 구조, README)을 신속하게 초기화하는 Dev 전용 워크플로우입니다.

Feynman-style technical inquiry for developers. Understand before you decide. Validate before you build.

dev_invoke_gemini-cli

dev_invoke_kimi-cli

FIX ESLint errors safely without breaking code. Prefix unused variables with `_`, fix no-case-declarations, add default props, and verify builds after each batch. Use when lint cleanup is needed for easier refactoring & faster Claude Code editing.

This skill should be used when testing ScreenGraph end-to-end flows (drift detection, agent runs) while monitoring backend and frontend logs in real-time. Use when the user wants to observe system behavior across services, debug live runs, or verify event streaming.

| Item | Value |

Review developer meeting notes from the UCEAP IT Software Engineering wiki to process any outstanding action items. Creates Jira tickets, updates meeting notes, and manages the wiki Home page. Use when processing UCEAP meeting followups or planning a dev meeting.

Colyseus client SDK for React, connection methods, room events, and messaging. Use when connecting to multiplayer server.

Colyseus server setup, room handlers, lifecycle events, and scaling. Use when setting up multiplayer server.

Colyseus state schema definition, types, decorators, and serialization patterns. Use when defining room state.

Server-authoritative multiplayer architecture principles. Use when designing multiplayer features.

Create frictionless first-day experiences for new team members.

Sprite animations, tweens, animation chains, and timeline sequences

Phaser game configuration, scenes, and lifecycle management

Keyboard, mouse, touch, and gamepad input management for Phaser

Particle emitters for visual effects like fire, smoke, explosions, and magic

Arcade physics velocity, acceleration, collision, and bounds

Matter.js physics: realistic bodies, constraints, and simulation

Scene transitions, data passing, and scene lifecycle management

Sprites, sprite sheets, texture atlases, and object pooling for Phaser

Tilemap loading, parsing, layers, and collision detection

UI containers, text objects, buttons, and DOM element integration

Development Philosophy & Standards. Use it everytime you plan or implement any code.

Anthropic의 Best Practice를 기반으로 고성능 프롬프트를 설계하고 최적화합니다.

React Three Fiber core patterns for scene composition and game loop

Material selection, shaders, and visual effects for R3F

Physics integration with Rapier for R3F game development

Per-task ralph loop pattern for implementation and debugging. One loop per task, not one loop per feature.