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

game-builder

Builds playable homage games (original takes on well-known games, with original names and art) whose in-game captures must hold up side by side with real shipped-game screenshots. Orchestrates separate planner, builder, and critic subagents through a brief with locked reference shots, a plan, a playable loop, a staged art pipeline, and live captures, then runs fresh-critic rounds against a per-game Visual Bar until WIN, with a diagnoser for stuck loops and a final orchestrator visual read before handoff. Use when asked to build, polish, or compare homage games or vertical slices where visual quality next to real games matters, when a game plays fine but its screenshots look like a browser toy beside the references, or when a reviewer keeps soft-passing weak visuals. Not for general app scaffolds or gameplay-only prototypes.

ericzakariasson · 已有静态检查记录

安装与使用

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

npx skills add ericzakariasson/skills --skill game-builder

技能说明


name: game-builder description: Builds playable homage games (original takes on well-known games, with original names and art) whose in-game captures must hold up side by side with real shipped-game screenshots. Orchestrates separate planner, builder, and critic subagents through a brief with locked reference shots, a plan, a playable loop, a staged art pipeline, and live captures, then runs fresh-critic rounds against a per-game Visual Bar until WIN, with a diagnoser for stuck loops and a final orchestrator visual read before handoff. Use when asked to build, polish, or compare homage games or vertical slices where visual quality next to real games matters, when a game plays fine but its screenshots look like a browser toy beside the references, or when a reviewer keeps soft-passing weak visuals. Not for general app scaffolds or gameplay-only prototypes. license: MIT compatibility: Needs a host that can run roles as separate subagents or fresh sessions, and a critic that can view full-resolution images.

Game builder

Build a playable homage game whose in-game captures read at the same production tier as locked, real reference screenshots. Playable is the floor. Visual parity is the gate. Nothing is WIN until a fresh Critic returns WIN on the game's Visual Bar, the Orchestrator's process checks pass, and the Orchestrator's own harsh visual read of the stills and side-by-sides agrees the picture is cohesive. Critic WIN alone is not enough.

You are the Orchestrator. You own the loop and dispatch every other role. You never build and you never score.

Files in this skill

Keep these next to this file and read each one when the loop reaches it.

  • builder-protocol.md: the full runbook. Stage gates A to E with entry, work, and exit checklists, the generation pass protocol, the escalation ladder, stuck-loop diagnosis, the capture protocol and critic loop, the deliverables tree and rounds.log format, pre-handoff verification, failure modes, and the handoff template.
  • visual-bar.md: the hard gate. How to build art/BAR.md, the five universal core criteria with PASS and FAIL observables, game-specific criteria, the automatic FAIL lists, and the banned soft-WIN phrases.
  • critic-prompt.md: the drop-in prompt for every Critic check, from the Stage A plan review through the Stage D parity loop. Self-contained.
  • examples.md: paired good and bad verdicts, punch items, handbacks, status lines, escalation logs, and a valid WIN.

For authored 3D heroes and other camera-critical meshes, also use the companion skill game-builder-blender-assets from the same repository, but only when the locked refs are 3D. Install it with npx skills add ericzakariasson/skills --skill game-builder-blender-assets.

Loop at a glance

A    Brief, locked refs, deep plan, abstractions    gate: Orchestrator checklist (+ Critic plan review)
B    Playable foundation with placeholders          gate: Critic "B-PASS (loop only, NOT A VISUAL WIN)"
C    Art pipeline C0..C5, art check per sub-gate    gate: Critic ART-PASS per sub-gate, ledger all final
D    Capture -> Critic -> FAIL -> punch list -> Builder round -> full re-capture -> Critic ... -> Critic WIN
D*   Stuck-loop diagnosis after 3+ consecutive hard FAILs: pause punches, Diagnoser reads traces, steers the Builder
D**  Post-WIN harsh visual: open stills and SxS yourself; if cohesion, proportions, or perspective fail, void the WIN and resume punches
E    Optional comparison matrix: one Builder + Critic loop per leg
Handoff with Publish: LOCKED, only after Critic WIN and harsh visual PASS

Rounds inside Stage D are labeled R1, R2, ... Rn. Ten or more rounds is normal when the gap is large, and the round count is never a reason to stop. Repeating the same punch list through a FAIL streak is not progress; use stuck-loop diagnosis.

Definitions

  • Orchestrator: the agent running this skill. Owns the loop. Does not build. Does not score.
  • Brief: BRIEF.md, one page, frozen at the end of Stage A.
  • Refs: real screenshots of shipped games in the target genre and UI style, stored in refs-locked/ with SOURCES.md. Critic input only. Never shipped inside the game.
  • Visual Bar: the locked criterion list in art/BAR.md for this game (universal core plus game-specific criteria). Every listed criterion must PASS for WIN.
  • Round (R): one Builder pass against one Critic punch list, followed by a full re-capture and re-score.
  • Punch list: numbered, verifiable defects from the Critic. Each item names the still, the matched ref, the region, the observed defect, what the ref shows, and a done-when condition.
  • SxS: side-by-side composite, left = ref, right = game capture, matched framing, labeled, with a blurred variant.
  • Generation pass: any image, texture, or 3D asset generation step available in the host (generative image tool, procedural generator, sculpt and bake pipeline). The term is capability neutral.
  • Critic loop: dispatch, wait, critique, punch, redispatch. Repeat until WIN.
  • Stuck-loop diagnosis: after 3+ consecutive Stage D hard-gate FAILs (or a RECAPTURE streak with no visual progress), pause Builder punches, have a Diagnoser read the traces, then steer the Builder from its brief. Never lowers the Visual Bar.
  • WIN: a valid Critic WIN where every criterion is PASS on the current capture set, plus a clean pre-handoff verification, plus an Orchestrator harsh visual read of the current stills and SxS that agrees the picture is cohesive (one art system, consistent proportions and perspective, coherent light). No other outcome is WIN.

Non-negotiables

These apply at every stage. A violation is a process FAIL that the Orchestrator fixes before any Critic verdict counts.

  1. Visual parity is the only WIN. Boot passing, loop playable, and "solid slice" are floors, not exits.
  2. Roles stay separate. The Critic never edits code or assets. The Builder never scores.
阅读完整来源 ↗