「game」の検索結果

Agent fallback for CCSGameRules_vtable (auto-generated, category: func). Locate CCSGameRules_vtable in the CS2 server module via IDA Pro MCP and emit a fresh, minimal-unique artifact. The deterministic preprocessor could not resolve this symbol on the current gamever - your job is the re-sign. Trigger: CCSGameRules_vtable, CCSGameRules_vtable

日本語の概要は準備中です。原文の説明を表示しています。

Agent fallback for CCSGameRules_PlayerSpawn (auto-generated, category: vfunc). Locate CCSGameRules::PlayerSpawn in the CS2 server module via IDA Pro MCP and emit a fresh, minimal-unique artifact. The deterministic preprocessor could not resolve this symbol on the current gamever - your job is the re-sign. Trigger: CCSGameRules_PlayerSpawn, CCSGameRules::PlayerSpawn

日本語の概要は準備中です。原文の説明を表示しています。

Agent fallback for CCSGameRules_GoToIntermission (auto-generated, category: vfunc). Locate CCSGameRules::GoToIntermission in the CS2 server module via IDA Pro MCP and emit a fresh, minimal-unique artifact. The deterministic preprocessor could not resolve this symbol on the current gamever - your job is the re-sign. Trigger: CCSGameRules_GoToIntermission, CCSGameRules::GoToIntermission

日本語の概要は準備中です。原文の説明を表示しています。

Agent fallback for CCSGameRules_BeginRound (auto-generated, category: func). Locate CCSGameRules::BeginRound in the CS2 server module via IDA Pro MCP and emit a fresh, minimal-unique artifact. The deterministic preprocessor could not resolve this symbol on the current gamever - your job is the re-sign. Trigger: CCSGameRules_BeginRound, CCSGameRules::BeginRound

日本語の概要は準備中です。原文の説明を表示しています。

Agent fallback for CCSGameRules_FindPickerEntity (auto-generated, category: vfunc). Locate CCSGameRules::FindPickerEntity in the CS2 server module via IDA Pro MCP and emit a fresh, minimal-unique artifact. The deterministic preprocessor could not resolve this symbol on the current gamever - your job is the re-sign. Trigger: CCSGameRules_FindPickerEntity, CCSGameRules::FindPickerEntity

日本語の概要は準備中です。原文の説明を表示しています。

Agent fallback for C_GameRules_vtable (auto-generated, category: func). Locate C_GameRules_vtable in the CS2 client module via IDA Pro MCP and emit a fresh, minimal-unique artifact. The deterministic preprocessor could not resolve this symbol on the current gamever - your job is the re-sign. Trigger: C_GameRules_vtable, C_GameRules_vtable

日本語の概要は準備中です。原文の説明を表示しています。

Launch, see and drive a real game so an agent can test its own mods. Covers launching via Steam or the exe, windowed mode at a fixed size, screenshots of the game window (GPU-safe capture), clicking and typing into menus, holding keys, relative mouse, crash-reporter cleanup, killing by PID, reading logs, scripted test scenes, and an in-game JSON bridge that lets an agent observe and act. Windows-first (also from WSL), with notes for Linux and macOS. Use when a mod must be verified in game, when navigating menus automatically, or when building a repeatable test or demo scene.

日本語の概要は準備中です。原文の説明を表示しています。

Figure out how a specific installed game can be modded, before writing any mod code. Covers where it's installed, the engine and version, managed vs native code, anti-cheat, loaders already present, save and config folders, and the community's modding route. Use when the user asks "can I mod <game>?", "what engine is <game>", "how do people mod <game>", or at the start of any modding task. Produces MODDING_PLAN.md.

日本語の概要は準備中です。原文の説明を表示しています。

Add one or more Components to a GameObject in the opened Prefab or active Scene. Component types are looked up by full name (with namespace) or by class-name fallback. Use 'gameobject-find' to locate the host GameObject and 'gameobject-component-list-all' to discover valid component type names.

日本語の概要は準備中です。原文の説明を表示しています。

Entrypoint for building, upgrading, and finishing Three.js browser games. Routes work across the sibling threejs-* skills for gameplay, graphics, UI, 3D/image/audio asset generation, debugging, and release. Use for any request to build, upgrade, polish, or ship a Three.js game as a whole, at any scope from a small arcade prototype to a premium release.

日本語の概要は準備中です。原文の説明を表示しています。

Add "juice" and game feel that makes actions satisfying — screen shake, hit-stop/freeze frames, tweened/eased motion, squash & stretch, knockback, and layered audio-visual feedback — as engine-neutral techniques that pair with the detected engine's tween, particle, and camera APIs. Use when the user mentions game feel, juice, "make it feel good/punchy", screen shake, hit stop, screen freeze, easing, squash and stretch, impact frames, or feedback/polish on hits, jumps, pickups, and deaths.

日本語の概要は準備中です。原文の説明を表示しています。

Architect game input — action mapping (abstracting keys into named actions), rebinding with conflict detection and persistence, multi-device support (keyboard, gamepad, touch), analog deadzones, and feel features like input buffering and coyote time, plus accessibility. Engine-neutral. Use when the user mentions input mapping, rebind controls, gamepad support, deadzone, input buffering, coyote time, or accessible controls.

日本語の概要は準備中です。原文の説明を表示しています。

Integrate Game Center features using GameKit. Use when authenticating GKLocalPlayer, checking player restrictions, submitting leaderboard scores, reporting achievements, implementing real-time or turn-based matchmaking, handling GKMatch data, showing the Game Center dashboard or access point, adding challenges and friend invitations, saving game data, or verifying player identity on a server.

日本語の概要は準備中です。原文の説明を表示しています。

Lightweight WebGL/WebGPU game engine with entity-component architecture and visual editor integration. Use this skill when building browser-based games, interactive 3D applications, or performance-critical web experiences. Triggers on tasks involving PlayCanvas, entity-component systems, game engine development, WebGL games, 3D browser applications, editor-first workflows, or real-time 3D rendering. Alternative to Three.js with game-specific features and integrated development environment.

日本語の概要は準備中です。原文の説明を表示しています。

Expert blueprint for digital card games (CCG/Deckbuilders) including card data structures (Resource-based), deck management (draw/discard/reshuffle), turn logic, hand layout (arcing), drag-and-drop UI, effect resolution (Command pattern), and visual polish (godot-tweening, shaders). Use for CCG, deckbuilders, or tactical card games. Trigger keywords: card_game, deck_manager, card_data, hand_layout, drag_drop_cards, effect_resolution, command_pattern, draw_pile, discard_pile.

日本語の概要は準備中です。原文の説明を表示しています。

Expert blueprint for idle/clicker games including big number handling (mantissa + exponent system), exponential growth curves (cost_growth_factor 1.15x), generator systems (auto-producers), offline progress calculation, prestige systems (reset for permanent multipliers), number formatting (K/M/B suffixes, scientific notation). Use for incremental games, idle games, or cookie clicker derivatives. Trigger keywords: idle_game, big_number, exponential_growth, generator_system, offline_progress, prestige_system, number_formatting.

日本語の概要は準備中です。原文の説明を表示しています。

Design a Seedance 2.0 two-player co-op game menu or opening animation with stable character bindings, approved visual direction, readable UI copy, coordinated palette, explicit interaction events, and a clean final menu state. Use for game concepts and character-led social intros; not for playable game development or copying commercial game branding.

日本語の概要は準備中です。原文の説明を表示しています。

Build, extend, and verify playable browser games, optionally using SandBase for generated concept art and game assets. Use for substantial 2D or 3D web-game work; use a general frontend workflow for non-game interactive sites.

日本語の概要は準備中です。原文の説明を表示しています。

Provider-independent production workflow for AI agents creating game trailers and promos, including announcement, gameplay, launch, DLC/update, store-page videos, social cutdowns, and generated/engine-capture hybrid trailers. Use when planning, scripting, capturing, generating, editing, localizing, reviewing, or QAing game marketing videos where gameplay truthfulness, platform/store constraints, ratings, accessibility, claims, CTA metadata, and rights provenance matter.

日本語の概要は準備中です。原文の説明を表示しています。

Expertise in real-time multiplayer networking, lag compensation, and authoritative server architectureUse when "multiplayer game, netcode, client-server game, P2P networking, lag compensation, rollback networking, game server, matchmaking, lobby system, player synchronization, state replication, dedicated server, authoritative server, tick rate, network prediction, interpolation, extrapolation, GGPO, lockstep, real-time multiplayer, networking, multiplayer, gamedev, realtime, client-server, p2p, netcode, synchronization, lag-compensation, matchmaking" mentioned.

日本語の概要は準備中です。原文の説明を表示しています。

Expert in designing and implementing intelligent game AI systems including behavior trees, finite state machines, GOAP, utility AI, pathfinding, steering behaviors, and perception systems. Specializes in creating believable, performant NPC behaviors that enhance player experience. Use when "game AI, NPC behavior, behavior tree, state machine for game, enemy AI, pathfinding, A* algorithm, navmesh, steering behavior, GOAP, utility AI, AI perception, combat AI, companion AI, boss AI, crowd simulation, flocking, game-ai, behavior-trees, pathfinding, npc, state-machines, goap, utility-ai, steering, perception" mentioned.

日本語の概要は準備中です。原文の説明を表示しています。

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.

日本語の概要は準備中です。原文の説明を表示しています。

Navigator and help guide for the UniKit framework — use when the user is unsure what to do next, where to start, or which unikit skill fits their situation. It diagnoses intent and points to the right skill or pipeline: starting a project, writing code, testing, planning, the spec-driven code workflow, authoring or detailing game design, finding a new mechanic, or deciding what game to build. Trigger on questions like "what do I do next", "where do I start", "how do I start coding", "how do I test my code", "how do I create the game design", "how do I detail a system", "how do I find a new mechanic", "which unikit skill should I use", "how does the code pipeline relate to game design", "I'm lost in unikit", "help me with unikit". Read-only — it explains and points to the right command, it never edits project files. For technical code research use /unikit-explore; for game-design research use /unikit-gd-explore; to initialize the framework use /unikit.

日本語の概要は準備中です。原文の説明を表示しています。