forked from Crown-Studio/roblox-ts-template
24 lines
2.3 KiB
Markdown
24 lines
2.3 KiB
Markdown
# Game content language
|
|
|
|
All AI assistants working in this repository must write all game content strictly in English, regardless of the language used in the user's request or conversation.
|
|
|
|
- Use English for all player-facing text: UI, menus, buttons, tooltips, notifications, errors, tutorials, dialogue, quests, item and ability names, descriptions, achievements, shops, and game publishing text.
|
|
- Use English for text embedded in generated images, textures, models, audio, and other game assets. Request English text and speech when using generation tools.
|
|
- Use English for new code identifiers, comments, logs, and developer commands associated with the game.
|
|
- When editing existing game content in another language, translate the affected content into natural English. Do not introduce French or other language variants unless the user explicitly requests localization.
|
|
- Before finishing a change, review the added or modified game content and asset-generation prompts for language consistency.
|
|
|
|
Conversation with the user and repository documentation may remain in the user's language. This does not change the English-only requirement for game content.
|
|
|
|
This policy applies to Codex, ChatGPT, Claude, Antigravity, Cursor, and any other AI assistant contributing to the project.
|
|
|
|
# Feature verification through Roblox Studio MCP
|
|
|
|
After implementing or modifying any feature, the agent must verify that it works in Roblox Studio through the Roblox Studio MCP before declaring it complete.
|
|
|
|
- Run the experience and exercise the affected feature through the MCP, checking its expected behavior and relevant client/server interactions.
|
|
- Inspect Roblox Studio Output and available runtime logs through the MCP for errors, warnings, and other signs of bugs during the test.
|
|
- Fix issues introduced by the change, then repeat the runtime test and Output inspection until the feature behaves as expected without related errors.
|
|
- Compilation, static checks, and automated tests complement this verification; they do not replace the MCP runtime check.
|
|
- In the completion report, briefly state what was tested and the result of the Output inspection. If the MCP is unavailable or verification cannot be completed, explicitly report the blocker and the unverified behavior instead of claiming the feature is verified.
|