跳到主内容
智客 ZICQ

技能库 智客分类:Agent 工作流 review-game

Review Game

审查现有的关于架构、业绩和最佳做法的游戏编码库。 当用户说"回顾我的游戏","代码回顾","检查我的游戏架构","是我的游戏结构良好",或"审计我的游戏代码"时使用. 不要用于修改——这是只读分析. 使用改进游戏执行修正.

844 安装量

官方网址:skills.sh

技能介绍

先看中文介绍;官方 description 原文单独保留,不改写 SKILL.md。

做什么

审查关于架构、性能和最佳做法的现有游戏代码库

何时用

用户说"审查我的游戏","代码审查","检查我的游戏架构","是我的游戏结构完善",或"审计我的游戏代码". 不要用于修改——这是只读分析. 使用改进游戏执行修正

代理如何加载

按 Agent Skills 渐进披露:启动时只加载 name 与 description(约 100 token);任务匹配后才读入整份 SKILL.md 正文;scripts/、references/、assets/ 仅在需要时再读。 本文件正文结构:Performance Notes、Review Game、Instructions、Step 1: Identify the game、Step 2: Architecture Review、Step 3: Performance Review。 其中含规范建议的小节:分步指令、输入输出示例。

文件分析

文件分析:除 SKILL.md 外,正文引用了 scripts/publish.sh,属于带资源的技能包,这些文件按需再读。

官方 description(原文)

Review an existing game codebase for architecture, performance, and best practices. Use when the user says "review my game", "code review", "check my game architecture", "is my game well structured", or "audit my game code". Do NOT use for making changes — this is read-only analysis. Use improve-game to implement fixes.

Performance NotesReview GameInstructionsStep 1: Identify the gameStep 2: Architecture ReviewStep 3: Performance ReviewStep 4: Code QualityStep 5: Monetization ReadinessOutput FormatExample UsageNext Step

· 许可:MIT

来源分类:skills.sh agent-skill

SKILL.md 与 Agent 调用

官方规范 ↗
name
review-game
description
Review an existing game codebase for architecture, performance, and best practices. Use when the user says "review my game", "code review", "check my game architecture", "is my game well structured", or "audit my game code". Do NOT use for making changes — this is read-only analysis. Use improve-game to implement fixes.
许可
MIT
  1. 发现技能客户端向 Agent 提供名称与描述目录。
  2. 匹配与调用用户指定或任务匹配后,载入 SKILL.md 指令。
  3. 按需加载按步骤读取参考文档、使用脚本与素材。
指令中引用的文件 · 1
  • scripts/publish.sh

以下路径提取自原文;文件是否齐全请以来源仓库中的完整目录为准。

具体调用语法与可用工具以目标 Agent 客户端为准。 查看调用机制说明 ↗

安装这个技能

Skills CLI ↗

先选择目标 Agent 和安装范围,保留技能包的附属文件,安装后检查客户端能否发现该技能。

该技能引用了附属文件,请从来源获取完整目录;仅复制 SKILL.md 可能缺少依赖。

交给 Agent 安装

复制安装指令给支持 Agent Skills 的代理,确认其中的目标目录与客户端匹配。

把 Agent Skill「review-game」安装到我的项目:SKILL.md 原文与官方 description 见 https://zicq.com/zh/skills/skl-f68ffc6e2fc29c9e-%E8%AF%84%E8%AE%BA%E6%B8%B8%E6%88%8F.html
请存为 .cursor/skills/review-game/SKILL.md 或 .claude/skills/review-game/SKILL.md,frontmatter 的 name 与 description 保持原样,不要改写。
该技能还带 scripts/、references/、assets/ 等文件,请从 https://github.com/playableintelligence/game-creator 取完整目录,不要只建一个 SKILL.md。

GitHub 完整包 ↗

终端安装 · Skills CLI

需要 Node.js 与 npx。先查看仓库技能列表,确认实际名称。

npx skills add 'https://github.com/playableintelligence/game-creator' --list

npx skills add 'https://github.com/playableintelligence/game-creator' --skill 'review-game'

CLI 会交互选择目标 Agent,默认安装到项目;用户级安装使用 -g。先通过查看命令核对仓库内容,再用 npx skills list 检查已安装技能。

阅读排版

name: review-game description: Review an existing game codebase for architecture, performance, and best practices. Use when the user says "review my game", "code review", "check my game architecture", "is my game well structured", or "audit my game code". Do NOT use for making changes — this is read-only analysis. Use improve-game to implement fixes. argument-hint: "[path-to-game]" license: MIT metadata: author: OpusGameLabs version: 1.3.0 tags: [game, review, architecture, best-practices, code-quality]

Performance Notes

  • Take your time to do this thoroughly
  • Quality is more important than speed
  • Do not skip validation steps

Review Game

Analyze an existing game codebase and provide a structured review. This is the final step in the pipeline — it checks everything is wired up correctly and gives you a quality score.

Instructions

Analyze the game at $ARGUMENTS (or the current directory if no path given).

Step 1: Identify the game

  • Detect the engine (Three.js, Phaser, or other)
  • Read package.json for dependencies and scripts
  • Read the main entry point and index.html
  • Identify the game concept/genre

Step 2: Architecture Review

Check for these required patterns and report compliance:

  • [ ] EventBus: Is there a centralized event system? Are modules decoupled?
  • [ ] GameState: Is there a centralized state singleton?
  • [ ] Constants: Are config values centralized or scattered as magic numbers?
  • [ ] Orchestrator: Is there a main Game class that initializes everything?
  • [ ] Directory Structure: Is code organized into core/systems/gameplay/ui/level layers?
  • [ ] Event Constants: Are events defined as named constants or raw strings?

Step 3: Performance Review

Check for common issues:

  • [ ] Delta time capping: Is getDelta() capped to prevent death spirals?
  • [ ] Object pooling: Are temp objects reused in hot loops?
  • [ ] Resource disposal: Are Three.js geometries/materials/textures disposed?
  • [ ] Event cleanup: Are event listeners cleaned up on scene transitions?
  • [ ] Asset loading: Are assets preloaded with progress feedback?

Step 4: Code Quality

  • [ ] No circular dependencies: Modules flow one direction
  • [ ] Single responsibility: Each module has one clear job
  • [ ] Error handling: Event handlers wrapped in try/catch
  • [ ] Consistent naming: Events use domain:action, files use PascalCase

Step 5: Monetization Readiness

  • [ ] Points system: Is there a scoring/points mechanism?
  • [ ] Session tracking: Can game sessions be identified?
  • [ ] Anti-cheat potential: Is score validation server-side or at least structured for it?
  • [ ] Play.fun integration: Any existing SDK integration?

Output Format

Provide a structured report with:

  1. Game Overview - What the game is, tech stack, game loop
  2. Architecture Score (out of 6 checks)
  3. Performance Score (out of 5 checks)
  4. Code Quality Score (out of 4 checks)
  5. Monetization Readiness (out of 4 checks)
  6. Top Recommendations - Prioritized list of improvements with plain-English explanations
  7. What's Working Well - Positive findings

Example Usage

/review-game examples/flappy-bird

Result: Architecture 6/6, Performance 4/5, Code Quality 4/4, Monetization 2/4 → Top recommendations: add Play.fun SDK, add object pooling for pipes, add delta time capping. Positive findings: clean EventBus usage, proper GameState reset, well-organized directory structure.

Next Step

Tell the user:

Your game has been through the full pipeline! Here's what you have:

  • Scaffolded architecture (/viral-game)
  • Visual polish (/design-game)
  • Music and sound effects (/add-audio)
  • Automated tests (/qa-game)
  • Architecture review (/review-game)

(Reflects the /viral-game one-shot pipeline. If you're working through /make-game, the equivalent state is "post-scaffold-phase + first development milestone shipped".)

What's next?

  • Add new gameplay features with /game-creator:add-feature [description]
  • Deploy to the web — run npm run build && ~/.agents/skills/here-now/scripts/publish.sh dist/ for instant hosting, or use GitHub Pages, Vercel, Netlify, itch.io
  • Keep iterating! Run /design-game, /add-audio, or /review-game again anytime after making changes.

相关技能

Agent 工作流

Skill Creator

创造有效技能指南。 当用户想创造出新的技能(或更新现有的技能),以专业知识,工作流程,或工具集成来扩展克洛德的能力时,应该使用这种技能.

Agent 工作流

Clawdhub

使用ClawdHub CLI搜索,安装,更新并发布从taladhub.com的代理技能. 需要获取苍蝇上的新技能时使用,将安装的技能同步到最新版本或特定版本,或者发布 npm-instainddhub CLI 的新/更新的技能文件夹.

Agent 工作流

Agent Team Orchestration

管弦乐团多代理团队,任务设定周期,交接协议,审查工作流程. 使用时间: (1)建立2+特派员队伍,具有不同专业,(2)确定任务路线和生命周期(收录框_ spec_建设_审查_完成),(3)在特派员之间制定交接协议,(4)建立审查和质量关口,(5)管理特派员之间的交流和文物共享.

Agent 工作流

Superpowers

Spec-first,TDD,子代理驱动的软件开发工作流程. 当:(1)构建任何新功能或应用——触发脑暴_计划_子代理执行回路,(2)调试出一个bug或测试失败——触发系统性的根起过程,(3)用户说"让我们构建","帮助我计划","我想添加X",或"这个被打破",(4)完成一个功…