elder-scrolls-legends

Debug a bug using the user's description and the match log file from the most recent game.

Audit cards for data accuracy and engine correctness. Supports single-card audit (compare against UESP wiki, verify engine ops/targets/families, report PASS or NEEDS_FIX) or full-catalog batch audit with progress tracking.

Investigate and fix a card whose in-game effect is not working as described.

Add a reusable UI pattern to the catalog. Use when a new UI feature has been built and should be documented for future reuse — e.g. "add this animation pattern", "catalog this UI flow". Takes a description of the pattern and the relevant files.

Find a reusable UI pattern from the catalog given a description of what you need. Use when implementing a new card or mechanic and you want to check if an existing UI pattern applies — e.g. "I need an arrow from one creature to another", "show damage after an animation", "defer an effect until a visual plays".

Configure a test match scenario for manual gameplay testing. Use when user wants to test a card, mechanic, keyword, or interaction in-game — e.g. "test veteran", "set up a match with treasure hunt cards", "I want to try Consume". Creates a JSON config in data/test_match_configs/ so the user can press ? on the Match button to pick and launch it.

Process all error reports from res://reports/bug-reports/ — analyze each bug, fix it, run tests, commit, and delete the report file. Ask for guidance on unclear reports.

Fix a card by comparing its local data and effects against the UESP wiki. Takes a card name, fetches wiki details, audits data fields and gameplay functionality, and fixes any discrepancies.

After fixing bugs in a session, generalize the fixes into abstract pattern classes and scan the codebase for unresolved siblings. Use when you've made several fixes and want to find other instances of the same class of bug. Triggers on phrases like "scan for similar bugs", "find related issues", "pattern scan", "extrapolate fixes", "any other bugs like these".

Fetch a card's artwork from the UESP wiki and save it to the codebase. Use when user wants to download, fetch, or add card art/image for a specific card. Takes a card name as argument.

Configure a new special lane type for Elder Scrolls Legends. Implements the lane effect in the registry, engine, and tests. Use when user wants to add, set up, configure, or implement a lane — e.g. "configure the mania lane", "set up armory lane", "implement the water lane effect". Takes a lane name as argument.

Run the headless AI-vs-AI match auditor to find gameplay bugs. Use when user wants to stress-test the engine, find card bugs automatically, run the auditor, or simulate matches — e.g. "run the auditor", "simulate some matches", "stress test the engine", "find bugs automatically".

Check the latest game log for evidence of a specific issue described by the user.

Research Elder Scrolls lore for a region and propose adventure themes with matching card catalog decks. Use when planning new adventures for a region — e.g. "research Morrowind adventures", "what adventures could we do in Cyrodiil". Takes a region name as argument.

Download missing card art for all cards in the catalog. Finds cards without art, creates a tracking document, then fetches art for each one using the fetch-card-art skill.

Analyze the most recent game log to identify card effect issues, gameplay bugs, and missing implementations.