Menu
Use when adding a new TCGEngine root application to the docker-compose environment (e.g. a new game). Walks through duplicating the web/mysql/phpmyadmin/redis services, assigning unique ports and env vars, and validating the new app comes up.
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
Use when debugging a specific SWUSim in-game bug or unexpected behavior tied to a real game (e.g. "game 2619 auto-resolves this leader ability wrong", "why did this prompt appear", "this ability should have auto-passed", "the shield popped when it shouldn't"). For reproducing and root-cause-fixing a live-game defect from its saved gamestate.
Use when starting a NEW SWU set to generate its consolidated SWUSim/docs/<set>-implement.md plan (for swusim-implement-set-plan to drive). Scans the generated card dictionaries, classifies every card, surveys for unbuilt core mechanics (hard-stops if found), then batches needs-work cards autonomy-first. Generate-only; one set abbreviation as input.
Use when implementing SWU card abilities — looks up card text, writes all DSL tests first, then self peer-reviews against the CR + game logic + card data and implements; only stops for the user on a card it can't verify to 98% alone. Supports single cards and batches.
Use when the user wants to drive a whole multi-batch SWUSim implementation plan doc (e.g. docs/<set>-complex-plan.md) to completion in one session — "run/execute the <set> plan", "work through the remaining phases". For many card batches across phases at once; for a single batch use swusim-implement-card.
Use when asked to verify a SWU set is "card complete" / review a set for implementation gaps (e.g. "is JTL card complete?", "validate the SOR set", "what's left in LOF?"). Runs two independent completeness checks — a dictionary-vs-Done-list diff AND an inverse-stub sweep that proves every trigger stub has a real handler — classifies each finding as a real gap or a false positive, and reports. Read-only validation; hand real gaps to swusim-implement-card.
Use at the end of a SWUDeck (NOT overall TCGEngine work) working session to run a short retro, capture durable lessons, and hand off cleanly. Invoke when the user says they're wrapping up, asks to "close the session", "run the retro", or asks "what were the lessons learned this session".
| name | new-docker-app |
| description | Use when adding a new TCGEngine root application to the docker-compose environment (e.g. a new game). Walks through duplicating the web/mysql/phpmyadmin/redis services, assigning unique ports and env vars, and validating the new app comes up. |
This skill provides instructions on how to add a new TCGEngine root application to the docker-compose environment.
NewGame)Update docker-compose.yml:
web-server, mysql-server, phpmyadmin, and redis services.<rootname>-<service-name> (e.g., newgame-web-server).3300:80 for web, 5103:80 for phpmyadmin, 6484:6379 for redis).MYSQL_SERVER_NAME: Set to <rootname>-mysql-server.REDIS_HOST: Set to <rootname>-app_redis.MYSQL_DATABASE: Set to the desired database name for the new app.<rootname>-redis and <rootname>-mysql-server.container_name to <rootname>_app_redis.<rootname>-mysql-data.Update docker-compose.override.yml:
web-server debug configuration for the new <rootname>-web-server.Validation:
docker compose up -d.