AGENT SKILL

game-playtest

Run browser-game playtests and frontend QA. Use when the user asks for smoke tests, screenshot-based verification, browser automation, HUD or overlay review, or structured issue-finding in a browser game.

License 许可
MIT
最近更新
2026-07-19
Stars
★ 1
Forks
1

01 前言 Front Matter

name
game-playtest
description
Run browser-game playtests and frontend QA. Use when the user asks for smoke tests, screenshot-based verification, browser automation, HUD or overlay review, or structured issue-finding in a browser game.

02 资源文件 1

03 SKILL.md 正文

Game Playtest

Overview

Use this skill to test browser games the way players experience them: through boot, input, scene transitions, HUD readability, and visual state changes. Prefer browser automation and screenshot review when the project supports it.

Preferred Workflow

  1. Boot the game and confirm the first actionable screen.
  2. Exercise the main verbs.
  3. Capture screenshots from representative states.
  4. Check the UI layer independently from the render layer.
  5. Report findings in severity order with reproduction steps.

Tooling Guidance

  • Prefer Playwright or equivalent browser automation already available in the repo.
  • When the game is canvas or WebGL heavy, screenshots are mandatory because DOM assertions alone miss visual regressions.
  • Use screenshots to judge playfield obstruction and HUD weight, not just correctness of text or layout.
  • When deterministic automation is not practical, do a structured manual pass and capture evidence.
  • For 3D rendering bugs or unexplained frame cost, use SpectorJS and browser performance tooling rather than guessing from code alone.

Common Checks

2D checks

  • sprite alignment and baseline consistency
  • hit or hurt animation readability
  • HUD overlap with the playfield
  • command menu state changes
  • tile or platform readability
  • input-state feedback and turn-state clarity

3D checks

  • first-load playability versus dashboard-like chrome
  • persistent overlay weight versus playfield visibility
  • camera control and camera reset behavior
  • pointer-lock or drag-look transitions when menus and overlays open
  • depth readability and silhouette clarity
  • secondary panels collapsed or dismissible during normal play
  • resize behavior
  • WebGL context loss or renderer fallback behavior
  • material or lighting regressions
  • GLB or texture streaming stalls
  • collision proxy or physics mismatch
  • performance cliffs tied to post-processing or asset load

Responsive and Browser Checks

  • desktop and mobile viewport sanity
  • safe-area and notch issues where relevant
  • reduced-motion behavior for UI transitions
  • keyboard, pointer, and pause-state handling
  • React state and scene state synchronization when the project uses React Three Fiber

Reporting Standard

Lead with findings. Keep each finding concrete:

  • what the user sees
  • how to reproduce it
  • why it matters
  • what likely subsystem owns it

References

  • Shared architecture: ../web-game-foundations/SKILL.md
  • Frontend review cues: ../game-ui-frontend/SKILL.md
  • 3D debugging notes: ../../references/webgl-debugging-and-performance.md
  • Full checklist: ../../references/playtest-checklist.md

04 同仓库更多 Skills

zfifteen
zfifteen/skills-catalog

Zotero

Use Zotero Desktop from Codex to enable/probe the local API, search a local Zotero library, list items/collections/tags, export BibTeX, insert citation keys into LaTeX or Markdown drafts, read indexed full text when requested, and import BibTeX/RIS records into Zotero through the connector server. Use when the user mentions Zotero, citations, references.bib, BibTeX export, local Zotero API, localhost:23119, or adding citations from a Zotero library.

★ 1
zfifteen
zfifteen/skills-catalog

zoom-apps-sdk

Use when using Apps SDK.

★ 1
zfifteen
zfifteen/skills-catalog

youtube

Obtain accurate, timestamped YouTube video transcripts (preferring manual captions over auto-generated) as the primary deliverable, then derive summaries, key claims, or notes from that transcript. Use when the user provides a YouTube URL (or video ID) and wants the transcript, a faithful summary, key claims with attribution, timestamped notes, or "what does this video actually say". The skill is transcript-first: never substitute metadata, title, description, or search snippets for the spoken content. Triggers: "youtube transcript", "get the transcript of this video", "summarize this youtube video", "what did they say in https://youtube.com/...", "key claims from this talk".

★ 1
zfifteen
zfifteen/skills-catalog

yeet

Publish local changes to GitHub by confirming scope, committing intentionally, pushing the branch, and opening a draft PR through the GitHub app from this plugin, with `gh` used only as a fallback where connector coverage is insufficient.

★ 1
zfifteen
zfifteen/skills-catalog

x-post-creator

Create X-ready post threads and co-located story packages from the active conversation or referenced project material. Use when the user says turn this into an X-post, /x-post, make this into an X thread, or wants plain-language social posts with supporting images saved to docs/x-posts/[story-name]/.

★ 1
zfifteen
zfifteen/skills-catalog

x-api

Search, read, and write X posts through the local X API MCP server (the same backend used by the Codex x-api skill). Use for searching X/x.com, reading threads and replies, creating lists, staging/publishing posts for @alltheputs, finding high-visibility reply targets for research outreach, ingesting public context, or any request that mentions /x-api or "search X".

★ 1