analyze-screenshot
Analyze game screenshots for visual design issues, UI problems, and art consistency. Automatically triggers when a screenshot is attached.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Analyze game screenshots for visual design issues, UI problems, and art consistency. Automatically triggers when a screenshot is attached.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Merge feature branches back to their base branches across the main repo and submodules. Use when user says "merge feature", "finish feature", "merge back", or invokes /git-dev-merge.
Build the Blured Engine (OpenCode + Godot)
Guided game creation workflow — choose gameplay-first or visual-first path to build a complete playable game. Use when user wants to create a new game, says "create a platformer", "make a game", "new game project", or similar.
Replicate a UI layout from a cornerstone reference image into a pixel-perfect .tscn scene. Use when user says "replicate UI layout", "build layout from reference", "1:1 UI copy", or has a cornerstone UI image to turn into a scene.
Create polished player-facing UI from whitebox to final assets. 5-step workflow from UI mockup to deployed game UI. Do NOT use for whitebox/prototype UI.
Package the Blured Engine into a distributable directory
| name | analyze-screenshot |
| description | Analyze game screenshots for visual design issues, UI problems, and art consistency. Automatically triggers when a screenshot is attached. |
| auto_detect | analyze.*screenshot|check.*ui|review.*screenshot|what.*wrong.*screen|visual.*feedback |
| auto_detect_attachment | image |
Perform a systematic visual design review of the attached game screenshot using the checklist below. Cover every category — do not skip sections even if they seem fine. Call out both problems and things that work well.
45 Damage not 45damage)Structure the analysis as follows:
## Game Screenshot Analysis
### Summary
[1-2 sentences describing the overall state of the UI]
### Issues Found
#### Critical (breaks readability or usability)
- [Issue]: [Why it's a problem] → [Specific fix]
#### Minor (degrades polish or feel)
- [Issue]: [Why it's a problem] → [Specific fix]
#### Nitpicks (small improvements)
- [Issue] → [Fix]
### What Works Well
- [Element]: [Why it's effective]
### Top 3 Priority Fixes
1. [Highest impact fix]
2. [Second priority]
3. [Third priority]