メニュー
Renaming a C file or associated header (.h) file requires additional steps in decompilation projects or the build will fail. Use this skill when you want to rename a C file and/or a header file.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Use this skill if you need to decompile a function that uses F3DEX. The presence of the Gfx type or gRegionAllocPtr are strongly indicative of an F3DEX or S2DEX microcode function.
Decomp-Permuter is a tool that automatically permutes C files to better match a target binary. Use this skill when you are decompiling a function and it is almost matching except for some register differences (i.e. 95%+). Or if you are otherwise unable to make progress on a function decompilation. Do not use it when there are control flow or functional differences; it's often easy to resolve those by hand, and neither the scorer nor the randomizer tends to play well with them.
Match a given segment to a libultra ROM segment. Use this when converting unidentified asm libultra ranges such as osRecvMesg to matching C source.
Adding a new asset to snowboardkids.yaml requires following specific steps to ensure assets are in the correct order and properly declared. Use this skill when you need to add a new binary asset.
Convert arrays with hardcoded pointer addresses to use ROM_START/ROM_END symbols. This automates the process of adding USE_ASSET declarations, updating array initialization, and configuring YAML segments.
Match data file describes how to add dat asegments to a C file. Use the match data file skill when you need to match a data file.
| name | rename-a-c-file-or-header-file |
| description | Renaming a C file or associated header (.h) file requires additional steps in decompilation projects or the build will fail. Use this skill when you want to rename a C file and/or a header file. |
C files and their associated header files are mapped to specific ROM addresses via the Splat project configuration in snowboardkids.yaml.
A file will typically have a code segment, such as:
- [0x4A40, c]
It may also have data and/or rodata segments. Data segment(s) are mapped to the code via the third argument. The name specified in the third argument must match the name of the code segment. In this case the code segment has no name so it defaults to using its ROM address as a name (4A40). For example:
- [0x8CBA0, .data, 4A40]
To rename 4A40.c to credits.c, we would need to do the following:
- [0x4A40, c, credits]
...
- [0x8CBA0, .data, credits]
Naturally, the reverse is also true. To rename a segment that has already been named, you must change each instance of that name to the new name. In this case you would need to change 'credits' to your desired new file name.
In rare cases a C file will have a custom compiler flags. Be sure to check the project Makefile and update the C file's name there also.