What problem does it solve? Building games in MapleStory Worlds (MSW) involves strict platform rules — TileMapMode and Body component mapping, .mlua/.codeblock pairing, SpriteRUID requirements, and builder-only file authoring — where mistakes cause silent failures like invisible entities or non-moving monsters. This Skill provides the foundation knowledge and mandatory preflight checks that prevent those failures. ## Core Features & Use Cases - Platform Rule Enforcement: Eight core rules plus symptom-to-cause troubleshooting references covering TileMapMode/Body mismatches, coordinate systems, SortingLayer, and spawn behavior. - Builder Protocol: A unified call protocol for MapBuilder, ModelBuilder, and UIBuilder so .map, .model, and .ui files are mutated safely without raw JSON edits. - Entity & Model Authoring: Template catalogs, modelId-vs-inline placement decisions, and animation state machine guidance (StateComponent, ActionSheet, IsLegacy) for monsters, NPCs, and players. - Use Case: When asked to add a chasing monster to a side-scrolling map, the Skill directs reading the TileMapMode first, authoring a .model from the MonsterCanonical template, placing it via MapBuilder.placeModel, and verifying animation states after refresh. ## Quick Start Ask the assistant to create a MapleStory Worlds monster or map entity and it will load this foundation skill first to apply the correct platform rules and builder workflow.