What problem does it solve?
Developing for Subspace Infinity requires adhering to strict module and package separation rules between the shared API, authoritative server, and client rendering layers, which can be confusing for new contributors or when adding new features. This Skill eliminates guesswork about where code belongs and how data moves between layers.
Core Features & Use Cases
- Exact code placement mapping: Provides a clear reference for which module and package every type of code (components, systems, events, configs, UI elements) belongs in.
- Data flow and boundary explanation: Details the authoritative server model, SimEthereal state sync, and RMI command boundaries between client and server.
- Use Case: A developer adding a new ship energy system can use this Skill to confirm the immutable energy component belongs in api/src/main/java/infinity/es/ship/, the writer system belongs in infinity-server/src/main/java/infinity/systems/ship/, and that client code cannot directly modify the component state.
Quick Start
Use the infinity-architecture skill to confirm the correct module and package for a new ship energy system component you are implementing.