Menú
Generate the host repository STYLE.md by composing one or more selected templates from ./.styles/.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
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.
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.
Manage explicitly requested OpenCaw goals as automated multi-task delivery flows with automatic per-task PR creation and required post-PR QA.
| name | generate-style |
| description | Generate the host repository STYLE.md by composing one or more selected templates from ./.styles/. |
Use when ../STYLE.md is missing or when the user wants to regenerate it after changing the repository art style mix.
../STYLE.md is missing, ask the user which templates from ./.styles/ apply unless the user already named the desired style.../STYLE.md from the selected templates using concise read directives by default (for example Read .//.styles/ISOMETRIC_2_5D.md instructions) to avoid oversized files.../STYLE.md as the authoritative art style contract afterward../commands/generate-style.sh "<STYLE1>" ["STYLE2" ...]./commands/generate-style.sh --inline "<STYLE1>" ["STYLE2" ...]