1.8천건 · 관련도순
Measure and improve Three.js or WebGL game performance through repeatable gameplay checks. Identify CPU or GPU bottlenecks, reduce unnecessary rendering and processing, and verify that controls, collisions, visuals, and memory remain stable.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Build in-game changelogs that connect release notes and displayed versions to successful production deployments. Reconstruct supported history, integrate menu navigation and accessible controls, and verify version consistency and behavior on desktop and mobile.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Build or audit browser map editors for Three.js and isometric games. Reuse production world definitions, edit placements in isolated drafts, inspect enemy behavior overlays, and validate exports before reviewed integration into the game.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Develop game theory papers from topics, model ideas, or drafts. The skill guides research questions, model design, equilibrium analysis, writing, and revision, with checks for mathematical rigor, citation gaps, and responses to reviewer comments.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Generate 2D game characters, props, icons and effects, or prepare existing artwork for use in a game. The skill removes backgrounds, separates frames, adjusts size and palettes, checks results, and exports assets for game engines.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Set up and debug a Phaser 4 game: the Game config, the Scene lifecycle (init/preload/create/update), the asset loader, cameras, and cross-scene communication. Use when building or debugging a Phaser game — when the user mentions Phaser, Phaser.Game, Phaser.Scene, preload/create/update, this.load, this.add, or scene transitions. For Arcade Physics movement/collisions use phaser-arcade-physics.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Plan and ship a game under a jam deadline: lock scope to the clock, schedule the hours, cut features, and submit on time. Use for a game jam (Ludum Dare, GMTK Jam, Global Game Jam), a 48-hour or weekend build, or scoping and submitting a jam entry.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Design and build game UI/UX — HUDs, menus, and overlays — that survive every screen: anchor- based responsive layout, resolution/aspect scaling and safe areas, keyboard/gamepad focus navigation, a screen/menu state stack, and event-driven (not polled) HUD updates. Engine- neutral patterns that pair with the detected engine's UI skill. Use when the user mentions HUD, health bar, main menu, pause menu, settings screen, UI layout, anchors, UI scaling, aspect ratio, safe area, controller/keyboard menu navigation, or wiring UI to game state.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Take a board game idea from 'wouldn't it be cool if' to a playtestable prototype — core loop, tension source, components you can make tonight, balance starting-points, and a real playtest protocol with kill criteria. Use when someone says 'I have a board game idea', 'design a game about X', 'my game drags in the midgame', or 'how do I playtest this'. Produces a design one-pager, a print-and-play prototype spec, and a 3-session playtest plan.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Deconstruct a novel for game adaptation. Compress a raw novel, deconstruction library, or writing project into a SOURCE_BIBLE with cited textual evidence, extracting world rules, player verbs, spaces, character will, systems, and visual anchors — without inventing a genre yet. Use for gameable book analysis, analyze a novel for game adaptation, extract game systems from a book. 游戏化拆书。把原始小说、拆文库或写作工程压缩成有必要原文证据的 SOURCE_BIBLE，提取世界规则、玩家动词、空间、角色意志、系统和视觉锚点，不提前发明游戏类型。用于游戏化拆书、分析小说的游戏改编基础等需求。
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Verify a game with evidence on its selected target runtime. Launch the actual build and prove real rendering, input, the core loop, at least one designed outcome, restart, and explicit limitations without dressing subjective fun up as a certain verdict. Use for test a generated game, QA a game build, check whether the game is fully playable, or verify the build. 游戏证据化质量验证。在选定的目标运行环境中启动实际构建，证明真实渲染、输入、核心循环、至少一个设计结果、重开和明确限制，不把主观趣味包装成确定性结论。用于测试生成游戏、检查游戏能否完整游玩或验证构建。
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Design game concepts from a novel. From SOURCE_BIBLE and PRODUCT_BRIEF, compare meaningful alternatives on the dimensions still unlocked, then select a playable direction using hard vetoes and explicit trade-offs. Use for what game should this novel become, compare game concepts, choose a game direction for this book, decide whether this novel should become an interactive story. 小说游戏概念设计。根据 SOURCE_BIBLE 与 PRODUCT_BRIEF 比较未锁定维度上的有效替代方案，用硬否决和关键取舍选择可玩方向。用于判断小说适合做成什么游戏、该不该做成互动叙事、比较游戏方案等需求。
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Expert architectural standards for building scalable Godot GAMES (RPGs, Platformers, Shooters) using the Composition pattern (Entity-Component). Use when designing player controllers, NPCs, enemies, weapons, or complex gameplay systems. Enforces "Has-A" relationships for game entities. Trigger keywords: Entity-Component, ECS, Gameplay, Actors, NPCs, Enemies, Weapons, Hitboxes, Game Loop, Level Design.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Expert architectural standards for building scalable Godot GAMES (RPGs, Platformers, Shooters) using the Composition pattern (Entity-Component). Use when designing player controllers, NPCs, enemies, weapons, or complex gameplay systems. Enforces "Has-A" relationships for game entities. Trigger keywords: Entity-Component, ECS, Gameplay, Actors, NPCs, Enemies, Weapons, Hitboxes, Game Loop, Level Design.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Facilitate game brainstorming sessions with game-specific techniques. Use when the user says "brainstorm game" or "game ideas"
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Consolidated game developer for story execution, code implementation, code review, QA/test authorship, and sprint orchestration. Use when the user asks to talk to Link Freeman, the Game Developer, the Game QA, or the Game Scrum Master.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
The craft of weaving story into interactive systems where the player is both audience and author. This skill covers the unique challenges of game narrative: branching structures that respect player agency, environmental storytelling that rewards exploration, dialogue systems that feel alive, and the delicate balance between authored experience and emergent narrative. Unlike linear media, games don't tell stories TO players - they create the conditions for stories to emerge WITH players. The narrative designer's job is to build the scaffolding that supports infinite player-authored moments while maintaining coherent themes and emotional arcs. This skill synthesizes lessons from Disco Elysium's internal monologue as gameplay, Hades' death-as-narrative-engine, interactive fiction's branching mastery (Inkle, Twine), and procedural narrative pioneers like Dwarf Fortress. It addresses ludonarrative harmony, bark systems, cinematics that respect agency, and the "and therefore" test that separates plot from story. Use when "narrative design, game story, game writing, dialogue system, branching narrative, player choice, environmental storytelling, bark system, quest design, lore delivery, ludonarrative, interactive fiction, inkle, twine, dialogue tree, player agency, cinematic design, voice direction, localization, procedural narrative, narrative, game-writing, dialogue, branching, player-agency, environmental-storytelling, quest-design, voice-acting, localization, interactive-fiction, procedural-narrative, ludonarrative" mentioned.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
World-class expertise in TCG/CCG design, resource systems, and metagame balanceUse when "card game design, TCG design, CCG design, trading card game, collectible card game, mana curve, deck building, card templating, keyword mechanic, set design, draft format, limited format, card rarity, color pie, faction design, card balance, magic the gathering style, hearthstone style, deckbuilder, card text, rules text, card-game, tcg, ccg, trading-card, collectible-card, deck-building, mana-curve, draft, limited, constructed, set-design, card-templating, mechanics, keywords, rarity, balance" mentioned.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
德州扑克策略 (德州扑克策略 (Texas Hold'em) — solver/GTO 时代的无限注德州扑克竞技打法，牌手/职业视角。覆盖: (a) 理论两极 — GTO 博弈论均衡 (不可剥削的基线策略) vs Exploitative 剥削打法 (针对对手漏洞偏离均衡最大化 EV)，以及二者的实战取舍; (b) solver 时代工作流 — PioSOLVER/GTO Wizard 跑解、范围构建、节点锁定 (node-locking) 做剥削、用 HUD+数据库 (Hold'em Manager/PokerTracker/Hand2Note) 复盘找漏洞 (leak finding); (c) 牌型分层 — 现金局 (cash game) vs 锦标赛 (MTT) 的根本差异，后者叠加 ICM (独立筹码模型) 与跳台/泡沫期博弈; (d) 核心概念栈 — 范围 (range)/权益 (equity)/EV/位置 (position)/翻前开池与 3-bet/4-bet/翻后下注理论 (c-bet、极化 vs 浓缩范围、MDF 最小防守频率、阻断牌 blockers、超池下注 overbet)、SPR、底池赔率; (e) 元层 — 资金管理 (bankroll management)、桌位选择 (table selection)、方差与心态 (mental game/tilt 控制)、抽水 (rake) 与场次选择对长期赢率 (winrate, bb/100) 的影响; (f) 智识演进 — 从 Sklansky 古典手牌价值 → Janda/Tipton 博弈论 → solver 普及 → GTO Wizard 民主化求解 → AI 超人 (Libratus/Pluribus) 对人类策略的反哺。学派分歧: GTO 派 vs 剥削派、现金局 vs 锦标赛、理论自上而下 vs 牌局自下而上、solver 纯学院派 vs 实战感觉派。不含: 线下牌场运营/发牌荷官、博彩合规与赌场管理、扑克之外的牌类 (桥牌/斗地主)、纯概率赌博 (老虎机/轮盘)。) Master OS — automated mastery of 德州扑克策略 (Texas Hold'em) — solver/GTO 时代的无限注德州扑克竞技打法，牌手/职业视角。覆盖: (a) 理论两极 — GTO 博弈论均衡 (不可剥削的基线策略) vs Exploitative 剥削打法 (针对对手漏洞偏离均衡最大化 EV)，以及二者的实战取舍; (b) solver 时代工作流 — PioSOLVER/GTO Wizard 跑解、范围构建、节点锁定 (node-locking) 做剥削、用 HUD+数据库 (Hold'em Manager/PokerTracker/Hand2Note) 复盘找漏洞 (leak finding); (c) 牌型分层 — 现金局 (cash game) vs 锦标赛 (MTT) 的根本差异，后者叠加 ICM (独立筹码模型) 与跳台/泡沫期博弈; (d) 核心概念栈 — 范围 (range)/权益 (equity)/EV/位置 (position)/翻前开池与 3-bet/4-bet/翻后下注理论 (c-bet、极化 vs 浓缩范围、MDF 最小防守频率、阻断牌 blockers、超池下注 overbet)、SPR、底池赔率; (e) 元层 — 资金管理 (bankroll management)、桌位选择 (table selection)、方差与心态 (mental game/tilt 控制)、抽水 (rake) 与场次选择对长期赢率 (winrate, bb/100) 的影响; (f) 智识演进 — 从 Sklansky 古典手牌价值 → Janda/Tipton 博弈论 → solver 普及 → GTO Wizard 民主化求解 → AI 超人 (Libratus/Pluribus) 对人类策略的反哺。学派分歧: GTO 派 vs 剥削派、现金局 vs 锦标赛、理论自上而下 vs 牌局自下而上、solver 纯学院派 vs 实战感觉派。不含: 线下牌场运营/发牌荷官、博彩合规与赌场管理、扑克之外的牌类 (桥牌/斗地主)、纯概率赌博 (老虎机/轮盘)。: top builders' mental models, tool stack, current workflows, jargon, and where to keep up. Trigger this skill when the user works on 德州扑克策略 (Texas Hold'em) — solver/GTO 时代的无限注德州扑克竞技打法，牌手/职业视角。覆盖: (a) 理论两极 — GTO 博弈论均衡 (不可剥削的基线策略) vs Exploitative 剥削打法 (针对对手漏洞偏离均衡最大化 EV)，以及二者的实战取舍; (b) solver 时代工作流 — PioSOLVER/GTO Wizard 跑解、范围构建、节点锁定 (node-locking) 做剥削、用 HUD+数据库 (Hold'em Manager/PokerTracker/Hand2Note) 复盘找漏洞 (leak finding); (c) 牌型分层 — 现金局 (cash game) vs 锦标赛 (MTT) 的根本差异，后者叠加 ICM (独立筹码模型) 与跳台/泡沫期博弈; (d) 核心概念栈 — 范围 (range)/权益 (equity)/EV/位置 (position)/翻前开池与 3-bet/4-bet/翻后下注理论 (c-bet、极化 vs 浓缩范围、MDF 最小防守频率、阻断牌 blockers、超池下注 overbet)、SPR、底池赔率; (e) 元层 — 资金管理 (bankroll management)、桌位选择 (table selection)、方差与心态 (mental game/tilt 控制)、抽水 (rake) 与场次选择对长期赢率 (winrate, bb/100) 的影响; (f) 智识演进 — 从 Sklansky 古典手牌价值 → Janda/Tipton 博弈论 → solver 普及 → GTO Wizard 民主化求解 → AI 超人 (Libratus/Pluribus) 对人类策略的反哺。学派分歧: GTO 派 vs 剥削派、现金局 vs 锦标赛、理论自上而下 vs 牌局自下而上、solver 纯学院派 vs 实战感觉派。不含: 线下牌场运营/发牌荷官、博彩合规与赌场管理、扑克之外的牌类 (桥牌/斗地主)、纯概率赌博 (老虎机/轮盘)。 problems and wants industry-grade thinking, tool selection, or workflow guidance. 触发词：「德州扑克」「德扑」「Texas Hold'em」「poker strategy」「扑克策略」
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
3D Game Development workflow skill. Use this skill when the user needs 3D game development principles. Rendering, shaders, physics, cameras and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
2D Game Development workflow skill. Use this skill when the user needs 2D game development principles. Sprites, tilemaps, physics, camera and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
2D Game Development workflow skill. Use this skill when the user needs 2D game development principles. Sprites, tilemaps, physics, camera and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
3D Game Development workflow skill. Use this skill when the user needs 3D game development principles. Rendering, shaders, physics, cameras and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Reviews game audio code for Wwise/FMOD integration safety, custom DSP plugin correctness, and audio middleware usage. Use when the user asks to review a Wwise plugin, check an FMOD DSP effect, audit game audio middleware integration, or asks "is my game audio code safe?". Trigger on phrases like "review my Wwise plugin", "check FMOD DSP effect", "is my game audio code safe", "review my audio middleware integration", or when you see AkPluginInfo, FMOD_DSP_DESCRIPTION, IMetaSoundSource, or Execute/process callbacks in game audio code.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.