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

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.

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.

Comprehensive UI/UX design and implementation skill covering visual design principles, color theory, typography, spacing systems, layout composition, accessibility (WCAG 2.2), animation, and systematic implementation workflows

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

ring:dev-implementation

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 |

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

Movement prediction with server reconciliation for WASD controls. Use when implementing player movement.

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

Create frictionless first-day experiences for new team members.

OPTIMIZE slow Vue applications, fix memory leaks, and improve render performance. Reduce unnecessary re-renders, optimize computed properties, and fix expensive operations. Use when application feels slow, memory usage grows, or animations lag.

Grid-based surface coverage tracking for territorial game mechanics

Object pooling for high-performance R3F components (decals, particles, projectiles)

Phaser game configuration, scenes, and lifecycle management

Arcade physics velocity, acceleration, collision, and bounds

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

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.

React Three Fiber core patterns for scene composition and game loop

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.

Analyzes codebase against standards and generates refactoring tasks for ring:dev-cycle.

AUTO-ACTIVATE when working in flow-state-refactor worktree or refactoring large components. MANDATORY port 5550 for refactor worktree. Extract Vue composables, split large files, reduce component size, baseline testing, zero regressions. Triggers on keywords refactor, composable, extract, split component, reduce file size, flow-state-refactor directory.

Developer reporting skill for work documentation and communication. Use when writing journals, devlogs, status updates (22A/22B), progress reports, or documenting development work. Generates reports from git history or manual input.

Find existing code patterns before implementing new features

This skill should be used as REQUIRED Phase 6 of /dev workflow when the implementation is complete and needs code review. Combines spec compliance and code quality checks with confidence-based filtering.

Developer agent skill router - routes to 31 dev skills by category and signal keywords, manages 5 sub-agents.

Run multiple isolated mux dev-server instances (temp MUX_ROOT + free ports)

ring:dev-ring:sre

dev-standards-majo

**Goal:** Implement a story by executing its tasks/subtasks with comprehensive

Comprehensive Storybook skill for Vue 3 - story creation, auditing, component discovery, visual testing, and CI integration. Merged from dev-storybook, storybook-audit, and storybook-master.

Complete backlog implementation in feature-driven development. Read backlog requirements, reference implemented features, design approach, implement code, and document. Use when implementing features, changes, bug fixes, or improvements.

Review and audit code quality, architecture, and implementation. Verify code meets design specs, find bugs, identify improvements, and create change/bug/improve backlogs. Use when reviewing completed code, auditing implementations, or ensuring quality.

Create and execute comprehensive tests including unit tests, integration tests, CLI tests, web/mobile UI tests, API tests, and log analysis. Find bugs, verify requirements, identify improvements, and create change/bug/improve backlogs. Use when testing implementations or ensuring quality.

Draft a conventional commit message when the user asks to commit code.

Capture and inspect specific screen regions (e.g., mobile simulators, app windows) using a background streaming process. Use for UI debugging and troubleshooting.

- [The Iron Law](#the-iron-law-of-tdd)

Chrome MCP browser testing. Console/network debugging, JS execution, GIF recording.

**Announce:** "I'm using dev-test-hammerspoon for macOS desktop automation."

<EXTREMELY-IMPORTANT>

Playwright MCP browser testing. Headless E2E, cross-browser, CI/CD automation.