Menu
Design, implement, and validate Playwright end-to-end coverage for critical user workflows.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
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.
| name | playwright-e2e-tests |
| description | Design, implement, and validate Playwright end-to-end coverage for critical user workflows. |
Use this skill when a task requires browser-driven verification, UI regression protection, or release confidence for user-critical web flows.
Typical triggers:
Produce a concise QA package that includes:
AGENTS.md, ARCHITECTURE.md, and any active roles../commands/ when a deterministic workflow exists. For Playwright, prefer commands/playwright-test.sh, commands/playwright-install.sh, and commands/playwright-evidence-report.sh.../commands/comment-issue-test-results.sh to keep issue history completepost-pr-qa workflow so the PR receives a GitHub comment with pass/fail evidence and inline screenshot URLs when screenshots are part of the proof.When adding or changing Playwright coverage:
ARCHITECTURE.md first. If the host repository uses the PLAYWRIGHT template, follow it as the testing contract.commands/playwright-evidence-report.sh and cite the resulting Markdown report paths.