القائمة
Post QA and Playwright verification evidence to the linked task issue, including result summary and screenshot references.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
Plan original trading card game and card-battler visual direction for TCG/CCG card frames, card illustrations, board styling, tokens/minions, hand/deck/graveyard zones, VFX, and Hearthstone-like fantasy tabletop polish while keeping references IP-safe.
Plan and specify production-ready game art sheets, including environment tilesets, biome/terrain sets, autotile sets, prop atlases, and directional character animation sheets with 4, 6, 8, 16, or custom facing counts. Use when art roles need to create tilesets or sprite animation sets before implementation handoff.
Generate the host repository STYLE.md by composing one or more selected templates from ./.styles/.
Maintain, generate, or validate the host repository STYLE.md art contract from OpenCaw .styles templates. Use when visual work must preserve a project art direction, when a user asks to choose or change art styles, or when art roles need to verify that STYLE.md still references valid style templates.
Prepare game art assets for implementation handoff with style references, source/runtime file paths, atlas metadata, pivots, anchors, animation rows, collision assumptions, sorting layers, licensing, and validation checks. Use when art roles deliver assets to engineering, QA, game design, or documentation.
Review isometric and 2.5D game art for projection, tile metrics, anchors, elevation, depth sorting, occlusion, lighting, walkability, and gameplay readability. Use for isometric sprites, tiles, props, environments, VFX, maps, atlas handoffs, or style reviews.
استنادا إلى تصنيف SOC المهني
| name | comment-issue-test-results |
| description | Post QA and Playwright verification evidence to the linked task issue, including result summary and screenshot references. |
Use after running QA checks, especially Playwright/browser tests tied to a task issue.
post-pr-qa and comment-pr-qa-results.sh so the PR receives the primary GitHub comment.../commands/comment-issue-test-results.sh "<issue_url_or_number>" "<results_summary_file>" [screenshot_or_artifact ...]