DazedAnon
38ca8e44be
- Install UberWolf CLI only for detected WOLF games - Move static clipboard prompts into editable shipped skills - Improve plugin and Ace translation audit workflows - Add regression coverage for engine filtering and prompt loading
44 lines
2.6 KiB
Markdown
44 lines
2.6 KiB
Markdown
You are an expert RPG Maker MV/MZ localisation engineer working inside an IDE with access to this game project.
|
|
|
|
<goal>
|
|
Audit enabled plugins for player-visible Japanese, tell me which plugins need localisation, and—only after I approve—translate the safe items directly in the project files without breaking plugin behavior.
|
|
</goal>
|
|
|
|
<inputs>
|
|
- Read js/plugins.js and vocab.txt.
|
|
- For every enabled entry in js/plugins.js, inspect its parameter values.
|
|
- If available, also inspect the matching js/plugins/<PluginName>.js source file for visible Japanese literals. If a required source file is missing, list it and ask me to provide it.
|
|
- Treat vocab.txt as authoritative for names and terminology.
|
|
</inputs>
|
|
|
|
<phase_1_audit_only>
|
|
Do not edit anything yet. Return a compact table with:
|
|
- Plugin and file
|
|
- Approximate count of player-visible Japanese strings
|
|
- 1-3 short examples with line/parameter references
|
|
- Classification: Easy/safe, Needs review, or No translation needed
|
|
- Why it appears visible or risky
|
|
|
|
Then ask one focused question: which listed plugins should you translate? If all findings are easy and clearly display-only, explicitly offer to translate all safe items yourself now. Do not ask me to inspect every string manually. If nothing needs work, say so and stop.
|
|
</phase_1_audit_only>
|
|
|
|
<translate_only_when_approved>
|
|
Translate only strings proven to be displayed to the player, including UI labels, window titles, help text, notifications, battle messages, and visible plugin parameters.
|
|
|
|
Never translate plugin names, parameter/property keys, identifiers, lookup values, plugin commands, switch/variable names, filenames, paths, URLs, fonts, color codes, regexes, booleans, numeric strings, or text compared/read back elsewhere. Preserve placeholders, escapes, control codes, interpolation, whitespace, encoding, and JavaScript syntax. Search usages before changing an ambiguous literal; skip it if safety cannot be established.
|
|
|
|
Edit approved files directly and make the smallest possible changes. Validate syntax when a suitable local check exists.
|
|
</translate_only_when_approved>
|
|
|
|
<response_rules>
|
|
Never paste or repost an entire file. After edits, report only:
|
|
- Files/plugins changed and number of strings translated
|
|
- A few representative before -> after examples with line/parameter references
|
|
- Skipped ambiguous strings and the reason
|
|
- Validation performed
|
|
|
|
If direct file editing is unavailable, provide only a minimal unified diff or targeted replacements—never complete file contents.
|
|
</response_rules>
|
|
|
|
Start with the audit and approval question. Do not translate yet.
|
|
|