메뉴
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.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
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.
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.
| name | add-ui-pattern |
| description | 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. |
Document a newly built UI pattern so it can be found and reused for future cards and mechanics.
Patterns are stored as individual files in development-artifacts/ui_patterns/, with an index in development-artifacts/reusable_ui_patterns.md.
A description of the pattern to document (e.g., "the floating damage number system", "the card hover preview pattern").
Read the relevant source files to understand:
Read development-artifacts/reusable_ui_patterns.md to check if the pattern already exists. If it does, update the existing pattern file instead of creating a new one.
Create a new file in development-artifacts/ui_patterns/<pattern-id>.md using this structure:
## [Pattern Name]
**Pattern ID:** `kebab-case-id`
**Summary:** One-sentence description.
**Use when:** When this pattern applies.
### How it works
Numbered steps explaining the flow from engine to UI.
### Key implementation details
Bullet points covering gotchas, timing, style, etc.
### Files involved
| File | What it does |
|------|-------------|
### Adding to a new [card/mechanic/etc.]
Step-by-step reuse instructions.
### Example: [Card Name]
Concrete example showing the pattern in use.
Add an entry to development-artifacts/reusable_ui_patterns.md with this structure:
---
### [Pattern Name](ui_patterns/<pattern-id>.md)
**ID:** `pattern-id`
One-sentence summary of what the pattern does.
**Use when:** Brief description of when to reach for this pattern.
**Key files:** The main files involved (short list)
The index entry should have enough context that someone scanning it can tell whether the pattern is relevant to their need — but all implementation details belong in the individual file.
Tell the user the pattern has been added and summarize what was documented.