Msw Scripting

Teaches Claude to write MSW scripts in mlua, a Lua variant with annotations like @Component, @Logic, and @ExecSpace that control where code runs (client, server, multicast). The framework isn't intuitive if you're coming from Unity. UI components use different property names, physics colliders don't emit touch events the way you'd expect, and Logic scripts have no self.Entity. The skill drills file structure rules (no flat dumps, feature folders required), the verify-then-write API lookup workflow against 600+ engine definitions, and the build-refresh-playtest-logs cycle. It's strict about method comments going inside the body, not above, because the parser binds them wrong otherwise. Good for teams that need Claude to stop guessing and follow MSW's actual contracts.

skills.sh installs: 10.7K
GitHub stars: 38
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add msw-git/msw-ai-coding-plugins-official --skill msw-scripting --agent claude-code

Installs into .claude/skills of the current project.

Files

MSW Scripting (.mlua) — Framework + File Workflow + Playtest & Debugging

mlua is Lua-based, but it has MSW-specific annotations, a lifecycle, and an execution-space model. General Lua knowledge alone will not produce working code. All work is done by editing files in the workspace directly, and code is validated in the order build logs → runtime logs.

1. Core Principles (must follow)

1.1 Existing Script First

Before creating a new .mlua, glob/keyword-search under ./RootDesk/MyDesk/ for an existing script with the same purpose — extending an existing file is always the first choice. Duplicate implementations raise maintenance cost and conflict risk.

1.2 Folder Structure for New Scripts — Never Dump Files Flat

When a new .mlua is unavoidable, place it under a feature/category subfolder. Required path shape: ./RootDesk/MyDesk/<FeatureFolder>/<ScriptName>.mlua.

SKILL.md on GitHub