Game UI Component Breakdown
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.
Install
npx skills add guiguiyan930-source/game-ui-design-workflow --skill game-ui-component-breakdowngit 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-component-breakdown ~/.claude/skills/game-ui-component-breakdownPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# 游戏 UI 组件拆解 输出独立素材或待自动切割的组件雪碧图及其契约,不重新生成完整页面。 ## 前置门禁 必须读取: - `contracts/style-contract.yaml` - `contracts/screen-contract.yaml` - `contracts/component-contract.yaml` - `contracts/asset-manifest.yaml` - 已批准页面视觉稿 源页面对应 manifest 条目必须为 `approved: true`。若未批准,停止拆解并说明需要先完成页面验收。 ## 分类 - `background`:完整场景底图,无文字、按钮、导航或角色遮挡 - `control`:主按钮、次按钮、关闭、返回、领取、导航按钮 - `container`:卡片、文本框、弹窗底板、货币栏、进度条 - `icon`:资源、功能、状态和导航图标 - `character`:角色、NPC、宠物、头像 - `decoration`:边框、角标、光效、底座、丝带和粒子 ## 拆解步骤 1. 确定全套拆解或指定范围。 2. 建立组件 ID、分类、用途、复用性、尺寸、状态和源页面关系。 3. 区分页面专属组件与跨页面基础组件。 4. 为每个组件写一份可独立执行的提示文件。 5. 图片工具可用时逐个生成,不把多个组件排成素材板。 6. 检查边缘、透明通道、裁切、光向和比例。 7. 更新组件契约和资源清单。 ## 雪碧图模式 当用户后续需要“雪碧图拆分、单元素 PNG、ZIP 打包”时,可以先生成一张组件雪碧图作为中间产物: - 所有元素完整、互不接触并留有明显间距。 - 使用透明背景或单一纯色背景。 - 不要文字、编号、网格线、水印和说明箭头。 - 阴影与发光不能跨到相邻元素。 - 同一组件的不同状态保持固定顺序和一致轮廓。 雪碧图不是最终切图。生成后必须调用 `game-ui-sprite-sheet-splitter` 导出独立 PNG,并完成人工验收。 最终文件名遵循[组件语义命名规范](references/naming-conventions.md)。`element-001.png` 只允许作为检测中间结果,不能作为批准交付。 ## 默认规则 - 除背景外使用透明背景。 - 按钮、卡片、弹窗和标签默认不要文字,保留排版留白。 - 图标保持同一视角、光源、描边和小尺寸识别性。 - 角色完整无遮挡,姿态适合叠放到原布局。 - 装饰可叠加,不带不透明矩形底。 - 保持源页面的视觉权重;不要把次按钮生成得比主按钮更强。 - 按钮、面板、弹窗和进度条填写 `slice` 元数据;9-slice margins 需要人工预览确认。 ## 单组件提示文件 保存为 `prompts/components/<component-id>.md`: ```markdown # <组件名称> ## 来源与用途 ## 尺寸和状态 ## 必须继承的契约字段 ## 图像生成提示词 ## 反向限制 ## 验收记录 ``` 提示词必须明确: - “单独的游戏 UI 组件素材” - 组件类别、用途、目标尺寸与状态 - 色调、材质、光向、描边、厚度和圆角 - 是否透明、是否无文字、中心构图和安全边距 - 高清、完整轮廓、适合合成和开发 - 不生成完整页面、不粘连其他组件 ## 特殊规则 ### 背景 无 UI 控件、文字、按钮、导航和前景角色;需要延展时要求边缘自然连续。
Details
- Skill name
game-ui-component-breakdown- Repository
- guiguiyan930-source/game-ui-design-workflow
- Path
skills/game-ui-component-breakdown/SKILL.md- License
- MIT
- Repo updated
- 5 August 2026
FAQ
What does the Game UI Component Breakdown skill do?
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.
How do I install the Game UI Component Breakdown skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add guiguiyan930-source/game-ui-design-workflow --skill game-ui-component-breakdown. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Game UI Component Breakdown 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 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 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.
Qt UI Design
551TheQtCompanyRnD/agent-skills
Design or audit UI for Qt/QML, Qt projects, web, or embedded MPU or MCU targets. Use when creating screens, layouts, navigation, or auditing UX.
Game UI Product Design
455guiguiyan930-source/game-ui-design-workflow
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 / 生图前先做策划.
Qt Qml Profiler
551TheQtCompanyRnD/agent-skills
Use when the user is investigating QML / Qt Quick performance — both vague complaints ("the UI feels laggy", "this is slow", "frames are dropping", "the app stutters") and explicit asks to profile, find hotspots, or optimize bindings, signals, or rendering. Runs qmlprofiler on a 2D QML application, parses the .qtd trace, and analyzes hotspots against the source with frame-time, memory, and pixmap-cache summaries. Does NOT cover Qt Quick 3D.
Browse the most popular Claude skills, all frontend & design skills, or write your own with the skills generator.