菜单
Use when building or rebuilding the French ROM of Pokémon Unbound end-to-end — from a translation_ready.json through make build-fr, the post-build patch chain, and validation.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | build-fr-rom |
| description | Use when building or rebuilding the French ROM of Pokémon Unbound end-to-end — from a translation_ready.json through make build-fr, the post-build patch chain, and validation. |
Procédure de bout en bout pour produire output/roms/GenedRom-fr.gba.
output/translation/*_translation_ready.json à jour (issu de la chaîne
combined_fr.txt → CSV trilingue → json). Si absent, le générer d'abord.input/roms/englishrom.gba et spanishrom.gba présentes (lecture
seule, vérifiées par make verify-roms).make build-fr — build générique puis enchaînement automatique des patchs :
patch_font_fr → patch_fixed_table_names → patch_time_format_fr →
apply_inline_overrides_fr → repair_stable_lz77_blocks →
repair_localized_lz77_blocks → repoint_stale_text_pointers → patch_pokedex_fr.translation-verifier
(orthographe, toponymes, glyphes, placeholders, synchro 3 sources).make test-playwright sur les specs touchées (boot,
gameplay, translation, visual-regression).input/roms/. Tout sort dans output/..sav et casse les goldens Playwright).Appliquer les règles de développement et la mémoire technique durable de gba_translator/Pokémon Unbound. Utiliser pour toute tâche dans ce dépôt, notamment avant de planifier, modifier, tester, déboguer ou relire le pipeline ROM, les traductions FR/IT/DE, l'encodage CFRU, les patchs binaires, l'émulateur mGBA ou le workflow Git.
Use when fixing any bug or patch script in gba_translator — before closing the ticket, verify the fix does not break (or silently already affects) the other registered languages (FR/IT/DE/Indie). Covers deciding whether a change is shared or per-language, which test paths and rebuild targets to run, and how to check a base-ROM quirk against every language.
Use before any new feature, pipeline change, or architectural decision — explores intent and design before implementation
Review a diff against project rules and acceptance criteria before merging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
Use when implementing any feature or bugfix, before writing implementation code