'game-design' 검색 결과

The foundational theory of interactive experience design - loops, motivation, feel, and the art of meaningful playUse when "game design, core loop, game feel, player motivation, game mechanics, meaningful choice, progression system, game economy, game balance, playtesting, GDD, game document, fun factor, engagement, flow state, risk reward, player agency, juice, game polish, 8 kinds of fun, bartle types, MDA framework, game-design, player-experience, core-loop, motivation, game-feel, MDA, playtesting, GDD, systems-thinking, player-psychology, engagement, flow-state" mentioned.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Designing tabletop games - from core mechanics to manufacturing, from prototyping to KickstarterUse when "board game, tabletop, card game, worker placement, deck building, area control, playtesting, rulebook, kickstarter game, game balance, asymmetric factions, euro game, ameritrash, party game, dice game, prototype, game publisher, crowdfunding game, board-games, tabletop, game-design, mechanics, playtesting, kickstarter, manufacturing, rulebook, components, balance, player-interaction" mentioned.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use to structure a vague marketing request into a well-scoped brief before any real work begins. Triggers on "shape this campaign", "plan this launch", "scope this content", "marketing plan", "growth plan", "content strategy", "outbound plan", or when invoked as the /mshape slash command. Produces a filled brief (campaign, content, optimization, research, or pipeline) that downstream marketing skills can act on. Do not use for work already well-defined — go straight to execution. For engineering task shaping see prompt-shaper; for game-design intake see game-design-shaper.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Structures a vague engineering request into a well-scoped task brief before any implementation begins. Use when the user has an engineering goal but the ask is missing which repos are in scope, what "done" means, constraints, or open questions. Triggers on "shape this", "scope this out", "frame this work", "write a brief for", "I want to build" (with unclear scope), or the /shape slash command. Produces a filled task template (multi-repo feature, single-repo change, investigation, or bugfix). Not for already-scoped work — go straight to execution. If the domain is unclear, ask one qualifying question before routing — for marketing intake see marketing-shaper, game-design intake see game-design-shaper.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Meta-skill for complete Roblox game development with Rojo — the entry point that knows and unifies the three specialist skills `/rojo` (filesystem→Studio sync, project setup), `/rbx-studio` (editor, MCP, assets, malware scan) and `/game-design` (roles, workflows, GDD). Use this skill for ANY Roblox game-dev undertaking: planning/building/setting up a Roblox game, scaffolding a new project, defining code architecture (Main + manager modules, _G.ClientState + HUD, remotes in GameEnums), avoiding Luau/Roblox pitfalls, or when it is unclear which of the Roblox specialist skills fits — routing happens from here. Also trigger on "develop Roblox game", "build Roblox game", "new Roblox project", "Luau project structure", "how do I organize Roblox code", "Roblox dev setup".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

How game development works as a process — roles, subtasks, workflows and role descriptions, especially (but not only) for Roblox. Use this skill when it's about the ORGANIZATION of game dev rather than concrete code: Which roles exist (Creative Director, Engineer, Artist, Polish/Audio, Business, QA-Tester, Game Critic)? Who does which subtask? What does a development chain (concept → backend → frontend → polish → test) look like? How do you write a Game Design Document / KONZEPT.md? How do several (AI) agents divide up a game? Also trigger on "plan a new game", "create Game Design Document", "which roles do I need for my game", "development workflow for a game", "who tests the game", "structure a game idea", "Roblox genre/monetization".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Coordinate role-based agents to design, implement, integrate, and test a game combat feature. The workflow covers gameplay rules, enemy behavior, visual effects, and audio planning, with a final report on completion, test results, and unresolved issues.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Design and implement a parry mechanic
• Coordinate enemy reactions, effects, and audio events
• Review combat architecture for the configured engine

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Expert blueprint for save/load systems using JSON/binary serialization, PERSIST group pattern, versioning, and migration. Covers player progress, settings, game state persistence, and error recovery. Use when implementing save systems OR data persistence. Keywords save, load, JSON, FileAccess, user://, serialization, version migration, PERSIST group.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Expert blueprint for TileMapLayer and TileSet systems for efficient 2D level design. Covers terrain autotiling, physics layers, custom data, navigation integration, and runtime manipulation. Use when building grid-based levels OR implementing destructible tiles. Keywords TileMapLayer, TileSet, terrain, autotiling, atlas, physics layer, custom data.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Expert blueprint for scene loading, transitions, async (background) loading, instance management, and caching. Covers fade transitions, loading screens, dynamic spawning, and scene persistence. Use when implementing level changes OR dynamic content loading. Keywords scene, loading, transition, async, ResourceLoader, change_scene, preload, PackedScene, fade.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Expert testing decision trees for GdUnit4: unit vs scene vs CI gates, headless runners, snapshots, and mock networks. Use when choosing test layers, wiring CI, or validating signals/physics without beginner assert catalogs. Keywords: GdUnit4, GdUnitTestSuite, headless CI, snapshot test, mock network, scene integration test, TDD.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Expert blueprint for Godot 4 project organization (feature-based folders, naming conventions, version control). Enforces snake_case files, PascalCase nodes, %SceneUniqueNames, and .gitignore best practices. Use when starting new projects or refactoring structure. Keywords project organization, naming conventions, snake_case, PascalCase, feature-based, .gitignore, .gdignore.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Expert blueprint for performance profiling and optimization (frame drops, memory leaks, draw calls) using Godot Profiler, object pooling, visibility culling, and bottleneck identification. Use when diagnosing lag, optimizing for target FPS, or reducing memory usage. Keywords profiling, Godot Profiler, bottleneck, object pooling, VisibleOnScreenNotifier, draw calls, MultiMesh.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Expert blueprint for RPG stat systems (attributes, leveling, modifiers, damage formulas) using Resource-based stats, stackable modifiers, and derived stat calculations. Use when implementing character progression OR equipment/buff systems. Keywords stats, attributes, leveling, modifiers, CharacterStats, derived stats, damage calculation, XP.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Expert blueprint for HTML5/web export on Compatibility (WebGL 2.0): JavaScriptBridge, localStorage wrapper, custom loading shells, COOP/COEP hosts, relative paths, beforeunload, visibility pause, and size optimization. WebGPU is out of scope. Keywords: web, HTML5, WebGL, Compatibility, JavaScriptBridge, localStorage, COOP, COEP, canvas, browser API.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Expert blueprint for procedural content generation (dungeons, terrain, loot, levels) using FastNoiseLite, random walks, BSP trees, Wave Function Collapse, and seeded randomization. Use when creating roguelikes, sandbox games, or dynamic content. Keywords procedural, generation, FastNoiseLite, Perlin noise, BSP, drunkard walk, Wave Function Collapse, seeding.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Expert blueprint for RichTextLabel with BBCode formatting (bold, italic, colors, images, clickable links) and custom effects. Covers meta tags, RichTextEffect shaders, and dynamic content. Use when implementing dialogue systems OR formatted text. Keywords RichTextLabel, BBCode, [b], [color], [url], meta_clicked, RichTextEffect, dialogue.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Expert blueprint for VR platforms (Meta Quest, PSVR, SteamVR, Pico) covering XR toolkit (OpenXR), comfort settings (vignetting, snap turning, teleport), motion controls, hand tracking, and 90+ FPS requirements. Use when targeting VR headsets or implementing immersive 3D experiences. Keywords VR, XR, OpenXR, Meta Quest, motion sickness, comfort, locomotion, XRController3D, foveated rendering.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Expert blueprint for console platforms (PlayStation, Xbox, Nintendo Switch) covering controller-first UI, certification requirements (TRCs/TCRs), platform services (achievements, cloud saves), and performance compliance. Use when targeting console releases or implementing gamepad-only interfaces. Keywords console, PlayStation, Xbox, Switch, TRC, TCR, certification, controller, gamepad, achievements.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Expert blueprint for hierarchical finite state machines (HSM) and pushdown automata for complex AI/character behaviors. Covers state stacks, sub-states, transition validation, and state context passing. Use when basic FSMs are insufficient OR implementing layered AI. Keywords state machine, HSM, hierarchical, pushdown automata, state stack, FSM, AI behavior.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Expert blueprint for AI pathfinding (tower defense, RTS, stealth) using NavigationAgent2D/3D, NavigationServer, avoidance, and dynamic navigation mesh generation. Use when implementing enemy AI, NPC movement, or obstacle avoidance. Keywords NavigationAgent2D, NavigationRegion2D, pathfinding, NavigationServer, avoidance, baking, NavigationObstacle.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Expert blueprint for turn-based combat with turn order, action points, phase management, and timeline systems for strategy/RPG games. Covers speed-based initiative, interrupts, and simultaneous turns. Use when implementing turn-based combat OR tactical systems. Keywords turn-based, initiative, action points, phase, round, turn order, combat.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Expert blueprint for dedicated / headless multiplayer hosts: ENet/DTLS, authority validation, safe packet decode, matchmaker handoff, and health telemetry. Use when building authoritative servers, --headless hosts, or hardening host networking. Keywords: dedicated server, headless, ENet, DTLS, authority, safe_packet_decoder, multiplayer host, WebSocketMultiplayerPeer.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.