What problem does it solve?
Subspace Continuum, MOSS, and Subspace Infinity use overlapping terms like cell, tile, region, and arena to refer to completely different concepts, leading to miscommunication between contributors, bugs in cross-system code, and inconsistent documentation.
Core Features & Use Cases
- Cross-system term mapping: Quick reference cheat sheet that defines each common term as it is used in Subspace, MOSS, and Subspace Infinity.
- Common trap clarifications: Explicit breakdowns of high-risk confusion points, such as the difference between a Subspace tile and a MOSS TileId, and the three distinct meanings of "cell" in the codebase.
- Coordinate and axis guidance: Clear definitions of all coordinate spaces, axis conversion rules, and project-specific constant sources of truth to prevent positional bugs.
- Use case: When debugging a client-server position mismatch, use this skill to confirm which coordinate space the bug originates in, and avoid mixing up Subspace 2D axes with Infinity's 3D Y-up convention.
Quick Start
Use the subspace-moss-terminology skill to clarify the correct definition of "region" when reading code that references both eLVL map polygons and the runtime grid labeling system.