name	playwright-browser-discovery
description	Discover live web UI structure with Playwright or playwright-cli before authoring browser tests or page objects.

When to use

Use when the user needs to inspect a live web page, discover selectors, identify field types, record conditional UI behavior, capture screenshots, or confirm a browser workflow before writing Playwright tests.

Typical triggers:

creating a new page object
diagnosing a stale selector
enumerating dropdown/multiselect options
checking conditional fields after a radio, checkbox, or dropdown change
producing UI evidence for a test plan

Output

Produce a concise discovery record:

target environment and entry URL
navigation path used to reach the screen
stable selectors or IDs discovered
control type for each relevant field
conditional behavior and how it is triggered
screenshots, snapshots, traces, or eval output paths when available
implementation recommendations for page objects and test data

Notes

Prefer host-owned login helpers, fixtures, and existing specs over rebuilding authentication manually.
Use browser snapshots for orientation and page.evaluate/DOM enumeration for large or dynamic pages.
Record exact option labels for dropdowns and multiselects; tests should use visible labels only when the application contract supports that.
Treat snapshot element refs as temporary. Re-snapshot after navigation or dynamic UI changes.
On Windows, do not invent unsupported CLI flags. Use the locally installed playwright-cli or npx playwright-cli with the flags supported by that version.
Store generated discovery artifacts in host scratch locations such as .playwright-cli/; do not promote them into OpenCaw unless they are reusable templates or references.
Reference docs bundled with OpenCaw live under assets/playwright-cli/references/.
When the user needs a non-interactive handoff, run commands/playwright-discovery-report.sh to summarize snapshots, screenshots, traces, and videos into .ai/reports/.

Más de este repositorio

mismo repositorio

tcg-art-direction

TimothyMeadows/OpenCaw

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.

2026-06-234

create-game-art-sheets

TimothyMeadows/OpenCaw

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.

2026-06-064

generate-style

TimothyMeadows/OpenCaw

Generate the host repository STYLE.md by composing one or more selected templates from ./.styles/.

2026-06-064

maintain-art-style-contract

TimothyMeadows/OpenCaw

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.

2026-06-064

prepare-game-art-handoff

TimothyMeadows/OpenCaw

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.

2026-06-064

review-isometric-production

TimothyMeadows/OpenCaw

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.

2026-06-064

name	playwright-browser-discovery
description	Discover live web UI structure with Playwright or playwright-cli before authoring browser tests or page objects.

When to use

Typical triggers:

creating a new page object
diagnosing a stale selector
enumerating dropdown/multiselect options
checking conditional fields after a radio, checkbox, or dropdown change
producing UI evidence for a test plan

Output

Produce a concise discovery record:

target environment and entry URL
navigation path used to reach the screen
stable selectors or IDs discovered
control type for each relevant field
conditional behavior and how it is triggered
screenshots, snapshots, traces, or eval output paths when available
implementation recommendations for page objects and test data

Notes

Prefer host-owned login helpers, fixtures, and existing specs over rebuilding authentication manually.
Use browser snapshots for orientation and page.evaluate/DOM enumeration for large or dynamic pages.
Record exact option labels for dropdowns and multiselects; tests should use visible labels only when the application contract supports that.
Treat snapshot element refs as temporary. Re-snapshot after navigation or dynamic UI changes.
On Windows, do not invent unsupported CLI flags. Use the locally installed playwright-cli or npx playwright-cli with the flags supported by that version.
Store generated discovery artifacts in host scratch locations such as .playwright-cli/; do not promote them into OpenCaw unless they are reusable templates or references.
Reference docs bundled with OpenCaw live under assets/playwright-cli/references/.
When the user needs a non-interactive handoff, run commands/playwright-discovery-report.sh to summarize snapshots, screenshots, traces, and videos into .ai/reports/.