Game UI Product Design
Writes and maintains game design docs (GDD), product requirements (PRD), and UI interaction logic before any page image generation. Use when users ask for 游戏策划方案、PRD、产品需求、UI交互逻辑、交互流程、状态机, or say to finish planning before generating UI visuals / 生图前先做策划.
Install
npx skills add guiguiyan930-source/game-ui-design-workflow --skill game-ui-product-designgit clone --depth 1 https://github.com/guiguiyan930-source/game-ui-design-workflow.git /tmp/game-ui-design-workflow
mkdir -p ~/.claude/skills
cp -r /tmp/game-ui-design-workflow/skills/game-ui-product-design ~/.claude/skills/game-ui-product-designPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# 游戏策划 · PRD · UI 交互(生成第一步) **本技能是完整 UI 生成流程的第一步。** 在调用页面生图、风格切换或批量延展之前,必须先完成本步并请用户批准三份文档。没有批准(且用户未明确跳过)时,不得开始后续视觉生成。 ## 输出文件 写入 `specs/<project-id>/`: | 文件 | 中文名 | 用途 | |---|---|---| | `gdd.md` | 游戏策划方案 | 定位、核心循环、系统清单、经济与养成(策划层) | | `prd.md` | 产品需求文档 | P0/P1 需求、信息架构、交付范围、验收 | | `interaction.md` | UI 交互逻辑 | 导航、主流程、控件行为、状态机、跨页链路 | 模板来源:仓库 `templates/spec-kit/gdd.md`、`prd.md`、`interaction.md`。项目已初始化则直接编辑现有文件,不要另起平行文档。 ## 何时使用 - 任何完整生成流程的**第一步**(默认入口) - 新建 UI 项目、只有概念尚无视觉 - 用户要求「生成之前加策划 / PRD / 交互」 - 延展或生图前发现三文档缺失、`draft` 或内容空洞 - 玩法或页面范围变更,需要回写需求与交互 ## 输入 优先读取: - `spec.md`、`research.md`、`plan.md` - 已有的 `gdd.md` / `prd.md` / `interaction.md` - 若已有:`contracts/screen-contract.yaml` 信息不足时:只询问题材、平台、核心玩法、首发页面范围等阻断问题;其余给可调整默认值并标注。 ## 工作流 复制并跟踪: ```text 进度: - [ ] 1. 确认或初始化项目目录 - [ ] 2. 撰写/更新 gdd.md - [ ] 3. 撰写/更新 prd.md - [ ] 4. 撰写/更新 interaction.md - [ ] 5. 交叉检查三文档一致 - [ ] 6. 停在人工批准门禁 ``` ### 1. 项目目录 若 `specs/<project-id>/` 不存在: ```bash python3 scripts/init_project.py <project-id> ``` ### 2. `gdd.md`(游戏策划方案) 必须覆盖: - 一句话定位、目标用户、卖点(≤3) - 核心循环表(回流 → 准备 → 玩法 → 成长 → 商业) - 系统清单与优先级(`must-have` / `genre-specific` / `optional`) - 资源与经济(策划层概述,禁止假装已有服务端公式) - 养成与进度轴、世界观最小集、风险约束 `文档状态.status` 先保持 `draft`,待用户批准后再改 `approved`。 ### 3. `prd.md`(产品需求) 必须覆盖: - 产品目标与可验证成功指标 - 非目标(明确不做) - P0 / P1 / P2 需求表(每条对应页面或系统) - 信息架构与本迭代页面交付范围 - 数据依赖、边界异常、验收清单 每条 P0 必须能被后续某个 `screen-id` 承接。 ### 4. `interaction.md`(UI 交互逻辑) 必须覆盖: - 全局交互原则、全局导航、全局状态 - 每个 must-have 页面:目的、进出、主流程、控件表、状态机
Details
- Skill name
game-ui-product-design- Repository
- guiguiyan930-source/game-ui-design-workflow
- Path
skills/game-ui-product-design/SKILL.md- License
- MIT
- Repo updated
- 5 August 2026
FAQ
What does the Game UI Product Design skill do?
Writes and maintains game design docs (GDD), product requirements (PRD), and UI interaction logic before any page image generation. Use when users ask for 游戏策划方案、PRD、产品需求、UI交互逻辑、交互流程、状态机, or say to finish planning before generating UI visuals / 生图前先做策划.
How do I install the Game UI Product Design skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add guiguiyan930-source/game-ui-design-workflow --skill game-ui-product-design. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Game UI Product Design popular?
It lives in guiguiyan930-source/game-ui-design-workflow, which has 455 GitHub stars and 66 forks.
Related skills
Game UI Asset Pipeline
455guiguiyan930-source/game-ui-design-workflow
Packs semantically named transparent game UI PNG files into an atlas, preserves component states and reviewed 9-slice metadata, and exports deterministic JSON handoff manifests for Godot, Unity, Cocos, or generic consumers. Use after sprite-sheet splitting when users ask for atlas packing, nine-patch metadata, engine delivery, Unity sprites, Godot regions, Cocos frames, or a Game UI Factory production handoff.
Game UI Component Breakdown
455guiguiyan930-source/game-ui-design-workflow
Breaks an approved game UI page or visual style into reusable, individually generated component assets with clean edges, transparent backgrounds where appropriate, stable naming, states, dimensions, prompts, and traceable manifest records. Use for UI slicing, transparent buttons, icons, cards, modals, navigation, characters, props, frames, labels, effects, or development handoff.
Game UI Extension
455guiguiyan930-source/game-ui-design-workflow
Extends a game concept or partial interface into a coherent screen system, player journey, feature flow, prioritized screen inventory, states, edge cases, and implementation-ready screen contracts. Use when users ask to expand an existing game UI, add related pages, audit missing screens, or plan a complete UI ecosystem.
Game UI Specification
455guiguiyan930-source/game-ui-design-workflow
Creates and maintains production-oriented game UI specifications and shared visual contracts covering color, typography, layout, geometry, components, interaction states, adaptation, and image-generation constraints. Use when users ask for a game UI design system, visual rules, standardization, or consistent downstream page and asset generation.
Game UI Page Generator
455guiguiyan930-source/game-ui-design-workflow
Designs and generates one complete game UI page at a time using an approved style and screen contract, producing a page brief, reproducible image prompt, negative constraints, an actual visual asset when image generation is available, and a manifest entry. Use for home, task, ranking, shop, inventory, character, event, reward, settlement, login, onboarding, HUD, or other game screens.
Game UI Sprite Sheet Splitter
455guiguiyan930-source/game-ui-design-workflow
Splits a generated game UI sprite sheet or component board into individual transparent PNG elements, writes crop metadata, validates dimensions and alpha channels, and packages all PNG files into a ZIP archive. Use after component breakdown when users ask to cut a combined sprite sheet, isolate every button/icon/card/effect, export single elements, remove a solid background, or deliver a downloadable PNG asset pack.
Browse the most popular Claude skills, all frontend & design skills, or write your own with the skills generator.