跳至正文
OpenAgentSkill
浏览已开放 · 目录记录日期 2026-11-21 · 自动更新和账户服务暂时关闭。
设计与 UI

game-architect

READ this skill when designing or planning any game system architecture — including combat, skills, AI, UI, multiplayer, narrative, or scene systems. Contains paradigm selection guides (DDD / Data-Driven / Prototype), system-specific design references, and mixing strategies. Works as a domain knowledge plugin alongside workflow skills (OpenSpec, SpecKit) or plan mode of an agent.

Yuki001 · 已有 AI 审核记录

安装与使用

运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。

npx skills add Yuki001/game-dev-skills --skill game-architect

技能说明


name: game-architect description: READ this skill when designing or planning any game system architecture — including combat, skills, AI, UI, multiplayer, narrative, or scene systems. Contains paradigm selection guides (DDD / Data-Driven / Prototype), system-specific design references, and mixing strategies. Works as a domain knowledge plugin alongside workflow skills (OpenSpec, SpecKit) or plan mode of an agent.

Game Architect Skill

Game architecture domain knowledge reference. Provides paradigm selection, system design references for game project architecture.

[!NOTE] This skill contains domain knowledge only, not a workflow. Pair it with a workflow skill (e.g., OpenSpec, SpecKit) or an agent's plan mode for structured design flow.

Usage Modes

With Workflow Skill (Recommended)

When used with a workflow skill (e.g., OpenSpec, SpecKit) or in the plan mode of an agent, this skill serves as a domain knowledge plugin:

  • During requirements/spec phases: Consult the Paradigm Selection Guide and System-Specific References to inform architectural decisions
  • During design/planning phases: Use the Reference Lookup Guide below to read relevant references/ documents

Knowledge Mode (Query)

When user requests to query knowledge for game architecture, this skill provides a reference lookup guide to relevant references/ documents based on the task.


Reference Lookup Guide

When designing game architecture, read the relevant references/ documents based on the task:

Architecture References

WhenRead
Always (high-level structure)references/macro-design.md
Always (core principles)references/principles.md
Requirement analysisreferences/requirements-analysis.md
Choosing DDD paradigmreferences/domain-driven-design.md
Choosing Data-Driven paradigmreferences/data-driven-design.md
Choosing Prototype paradigmreferences/prototype-design.md
Evolution & extensibility reviewreferences/evolution.md
Changing requirements in an existing implementationreferences/requirement-change-strategy.md
Performance optimization neededreferences/performance-optimization.md
Multiplayer support neededreferences/multiplayer-overview.md
  • For physical architecture design, see the Physical Architecture References table below.
  • For system-specific design, see the System-Specific References table below.
  • For multiplayer system design, see the Multiplayer References table below.

Note : Only read the multiplayer references when multiplayer is needed.

Physical Architecture References

WhenRead
Project structure & file organizationreferences/project-structure.md
Data formats, processing, custom formats, bundles, metadatareferences/data-files.md
Gameplay content editor applications and authoring pipelinesreferences/content-editor.md
Asset conventions & pipelinereferences/asset-conventions.md
Distribution, packaging, hot update, CDN, deploymentreferences/distribution.md

System-Specific References

System CategoryReference
Foundation & Core (Logs, Timers, Modules, Events, Resources, Audio, Input)references/system-foundation.md
Time & Logic Flow (Update Loops, Async, FSM, Command Queues, Controllers)references/system-time.md
Combat & Scene (Scene Graphs, Spatial Partitioning, ECS/EC, Loading)references/system-scene.md
UI & Modules (Modules Management, MVC/MVP/MVVM, UI Management, Data Binding, Reactive)references/system-ui.md
Skill System (Attribute, Skill, Buff)references/system-skill.md
Action Combat System (HitBox, Damage, Melee, Projectiles)references/system-action-combat.md
Camera, Character & Controller 3C (PlayerController, Physics, Camera, Actor States)references/system-3c.md
Effect & Feedback System (Screen Shake, VFX, Hit-Stop, Haptics, SFX, Floating Text, UI Feedback, Orchestration)references/system-effect-feedback.md
Narrative System (Dialogue, Cutscenes, Story Flow)references/system-narrative.md
Game AI System (Movement, Pathfinding, Decision Making, Tactical)references/system-game-ai.md
Mod & DLC System (Plugin Architecture, Config Database, Scripting, Hooks, Extensibility)references/system-mod.md
Procedural Content Generation (PCG) (World/Level Generation, Roguelike, Noise, Simulation)references/system-pcg.md
Algorithm & Data Structures (Pathfinding, Search, Physics, Generic Solver)references/algorithm.md
Puzzle Game System (Match-3, Jigsaw, Water Sort, Blocks, Physics Puzzles, Board Games, Content & Presentation Boundaries)references/system-puzzle.md

Multiplayer References

FocusReferenceUse When
Multiplayer overviewreferences/multiplayer-overview.mdDecide client/server responsibility, authority split, and gameplay sync style
Multiplayer protocol and connectionreferences/multiplayer-protocol.mdDesign messages, serialization, Req/Resp/Notify, heartbeat, reconnect
Multiplayer server architecturereferences/multiplayer-server-architecture.mdDesign ownership boundaries, process roles, deployment, persistence, recovery
Common server components and servicesreferences/multiplayer-implementation-common.mdBuild shared infrastructure such as auth, gateway, connector, db, cache, discovery, queue, observability
Room server build playbookreferences/multiplayer-implementation-room.mdBuild a concrete small-to-medium room-based realtime server with join flow, room ownership, settlement, reconnect
Encounter server build playbookreferences/multiplayer-implementation-encounter.mdBuild a concrete turn-based or combat-workflow server with checkpointing, idempotent actions, settlement
Persistent world server build playbook`r
阅读完整来源 ↗