Yuwakisa Game Factor
Factor a single-file browser game (a yuwakisaweb-style canvas prototype — one big index.js of module-level state, an immediate-mode render(), and inline event listeners) into a server-portable five-module split: GameArtifacts, GameDisplayArtifacts, GameState, GameEngine, GameUI. Use when asked to "factor/refactor this game", split a monolithic game into GameEngine/GameState/GameUI, make a prototype "portable to a server" or to yuwakisacloud, separate rules from rendering, or add seeded/reproducible RNG to a canvas game. Also use when deciding where a new game feature (terrain, skills, affixes,
Install
npx skills add roby2358/skills --skill yuwakisa_game_factorgit clone --depth 1 https://github.com/roby2358/skills.git /tmp/skills
mkdir -p ~/.claude/skills
cp -r /tmp/skills/yuwakisa_game_factor ~/.claude/skills/yuwakisa_game_factorPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Factoring a browser game for server-readiness Split a monolithic canvas game so the **authoritative half runs headless** and the browser half is a thin client. The seam is drawn once; the actual client/server wiring is added later (see Deferred). ## Target modules Five modules plus unchanged shared libs (`hex.js`/grid math, `rando.js`, `colortheory.js`). Each new file wraps its definition in an IIFE that returns **one global** (see Globals). | Module | Global | Holds | |---|---|---| | `artifacts.js` | `GameArtifacts` | Static **rules-data** the engine adjudicates over: terrain/unit types, movement/action costs, MP, map dims. No colors, no pixels. Server-side. | | `displayartifacts.js` | `GameDisplayArtifacts` | Client-only **display attrs**: sizes/geometry, colors, on-screen names, flavor. Keyed off `GameArtifacts` ids, so loads after it. | | `gamestate.js` | `GameState` | Authoritative, **serializable data only** — `seed`, the grid, units/player, turn, resources, win flags, whose-turn `phase`. No behavior, no DOM, no view/interaction state. | | `gameengine.js` | `GameEngine` | **Rules + world generation** over a `GameState`. DOM-free and render-free. | | `gameui.js` | `GameUI` | The **client**: canvas rendering, DOM HUD, camera/pan, hover, selection/targeting/overlay modal state, all input wiring. | `index.js` becomes a ~4-line bootstrap:
Details
- Skill name
yuwakisa_game_factor- Repository
- roby2358/skills
- Path
yuwakisa_game_factor/SKILL.md- Repo updated
- 14 November 2026
FAQ
What does the Yuwakisa Game Factor skill do?
Factor a single-file browser game (a yuwakisaweb-style canvas prototype — one big index.js of module-level state, an immediate-mode render(), and inline event listeners) into a server-portable five-module split: GameArtifacts, GameDisplayArtifacts, GameState, GameEngine, GameUI. Use when asked to "factor/refactor this game", split a monolithic game into GameEngine/GameState/GameUI, make a prototype "portable to a server" or to yuwakisacloud, separate rules from rendering, or add seeded/reproducible RNG to a canvas game. Also use when deciding where a new game feature (terrain, skills, affixes,
How do I install the Yuwakisa Game Factor skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add roby2358/skills --skill yuwakisa_game_factor. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Yuwakisa Game Factor popular?
It lives in roby2358/skills, which has 5 GitHub stars and 0 forks.
Related skills
Coding
5roby2358/skills
Project-specific coding conventions and constraints. Use when writing, modifying, or refactoring any code, implementing features, writing tests, or building MCP servers in this project.
Game Design
5roby2358/skills
Design principles for tactics and strategy games. Use when designing new mechanics, tuning existing systems, adding units or abilities, adjusting difficulty, or making any game design decision. Triggers on discussions about game balance, unit roles, terrain, pacing, spawning, healing, combat, win/loss conditions, or UI for conveying game state.
Game Productize
5roby2358/skills
Audit a browser game for ship-readiness and produce a tiered gap list: a SHIP.md in the game repo plus pjpd tasks. Finds what gets forgotten between "the game works" and "a stranger can play it": title/menus/end screens, save and resume, audio and settings, onboarding, the mobile "sorry" screen, localization readiness, error recovery, hosting on the author's site and on portals (itch.io, Newgrounds), credits, asset licenses, and AI disclosure. Use when the user says "productize", "/game-productize", "get this game ready to ship/release/publish/launch", "what's missing before I launch", "prep f
Cleaning Data
5tilmon-engineering/claude-skills
Systematic data quality remediation - detect duplicates/outliers/inconsistencies, design cleaning strategy, execute transformations, verify results (component skill for DataPeeker analysis sessions)
Web Design Reviewer
9sandbaseai/workbuddy-skill
Use when visually reviewing an authorized website for layout, responsive, accessibility, consistency, and interaction issues, with optional source-level fixes.
Interpreting Results
5tilmon-engineering/claude-skills
Component skill for systematic result interpretation with intellectual honesty in DataPeeker analysis sessions
Browse the most popular Claude skills, all frontend & design skills, or write your own with the skills generator.