write-highrise-studio-lua
Write non-UI Lua scripts for Highrise Studio projects. You cannot write or edit them without this skill.
When & Why to Use This Skill
This Claude skill specializes in generating high-quality, non-UI Lua scripts specifically for Highrise Studio projects. It streamlines the development process by strictly adhering to platform-specific style guides and API constraints, ensuring that all generated code is optimized for the Highrise environment while avoiding incompatible Unity or Roblox syntax.
Use Cases
- Automating the creation of complex game logic and backend scripts for Highrise Studio experiences using standardized templates.
- Implementing platform-specific API calls accurately by cross-referencing with dedicated research tools to prevent runtime errors.
- Refactoring and debugging existing Lua scripts by identifying syntax errors through IDE diagnostic integration and ensuring style guide compliance.
| name | write-highrise-studio-lua |
|---|---|
| description | Write non-UI Lua scripts for Highrise Studio projects. You cannot write or edit them without this skill. |
Write Highrise Studio Lua code
This guide covers how to write Highrise Studio Lua code.
Instructions
Add the following steps to your todo list:
- Search for and read any relevant scripts in the project, if needed.
- Ask the user for any information that is needed to solve the request.
- If starting a new script, copy the code from the style guide as a starting template. Do not create a new script from scratch, as the style will be wrong.
- Use the
research-highrise-studio-lua-apiskill to understand the Highrise Studio API. Don't assume you know the API without it. - Write the code, following these imperatives:
- Do not use Unity C#, MonoBehaviour, or Roblox APIs unless specified in the Highrise Studio API docs. There is no such thing as
task. - Avoid browser or DOM references (
document,window,addEventListener, etc.).
- Do not use Unity C#, MonoBehaviour, or Roblox APIs unless specified in the Highrise Studio API docs. There is no such thing as
- If you have access to the
mcp__ide__getDiagnosticstool, use it to read syntax errors in the Lua scripts you work with. - Remove section headers that have no content.
- Remove guidance comments that were copied over from the template. Keep the section headers.
- If requested, add the script to the scene using the
use-unity-editorskill.