subspace-moss-terminology

Resolve overlapping terminology across Subspace Continuum, MOSS, and Subspace Infinity.

25|5|Updated Apr 22, 2017
One-click install
npx skills add https://github.com/assofohdz/subspace-infinity --skill subspace-moss-terminology
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: subspace-moss-terminology
Source: https://github.com/assofohdz/subspace-infinity/tree/main/.claude/skills/subspace-moss-terminology
Command: npx skills add https://github.com/assofohdz/subspace-infinity --skill subspace-moss-terminology

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about subspace-moss-terminology

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
Why do coordinate spaces mismatch between Subspace Continuum and Subspace Infinity?

Coordinate space mismatches occur because Subspace Continuum uses a 2D axis system while Subspace Infinity uses a 3D Y-up convention. This skill provides axis conversion rules and coordinate space definitions to prevent positional bugs when developing across both systems.

How do I resolve terminology confusion between Subspace, MOSS, and Subspace Infinity?

Resolving terminology confusion requires cross-system reference mappings for overlapping terms like cell, tile, region, and arena. This skill provides a cheat sheet clarifying each term's specific definition across Subspace, MOSS, and Subspace Infinity.

What is the difference between a Subspace tile and a MOSS TileId?

A Subspace tile and a MOSS TileId refer to completely different concepts despite sharing similar names. This skill provides common trap clarifications that explicitly break down high-risk confusion points like this to prevent cross-system coding bugs.

How do I fix client-server position mismatch bugs in Subspace game development?

Fixing client-server position mismatch bugs requires confirming which coordinate space the error originates in. This skill offers coordinate space definitions and axis conversion rules to prevent mixing up Subspace 2D axes with Infinity's 3D Y-up convention.

When do I need terminology disambiguation for Subspace and MOSS development?

Terminology disambiguation is needed during software development, debugging, and documentation tasks involving shared terms like region, arena, and grid. This skill ensures consistent term usage when reading code that references both eLVL map polygons and runtime grid labeling systems.