dependency-sources

Configure local source paths for Moss and Simsilica Java dependencies.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the tedious step of extracting and unpacking compiled JAR files to access the source code of Moss and Simsilica library dependencies, saving development time when debugging or extending the Subspace Infinity game engine.

Core Features & Use Cases

  • Pre-located Moss Source Paths: Direct access to source code for all Moss modules (mblock, mphys, mworld, sio2-mblock, etc.) stored locally under ~/github/assofohdz/moss/.
  • Pre-located Simsilica Source Paths: Direct access to source code for core Simsilica libraries (Lemur, zay-es, SiO2, SimEthereal, SimMath) stored locally under ~/github/assofohdz/simsilica-deps/.
  • Use Case: When investigating a block rendering glitch in the Subspace Infinity client, use this Skill to directly read the mblock GeometryFactory.java implementation instead of extracting it from a compiled dependency JAR.

Quick Start

Use the dependency-sources skill to locate and read the source code for the Lemur InputMapper class to debug input handling issues.

Frequently Asked Questions about dependency-sources

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

FAQPage Schema
How do I read Moss and Simsilica library source code without extracting compiled JAR files?

You can read Moss and Simsilica source code directly using pre-configured local source tree paths, eliminating the tedious step of unpacking compiled JAR files for debugging or extending Java game engine dependencies.

Where can I find the Lemur InputMapper source code for debugging Java game UI input handling?

The Lemur InputMapper source code is accessible under the pre-located Simsilica local source tree at ~/github/assofohdz/simsilica-deps/, enabling immediate debugging of input handling issues without JAR extraction.

Can I use this to access physics and ECS internals for the Subspace Infinity game engine?

Yes, you can access physics, ECS, networking, and UI library internals for the Subspace Infinity project through pre-located local paths for all relevant Moss and Simsilica modules.

What's the best way to locate the mblock GeometryFactory implementation for a block rendering glitch?

The best way to locate the mblock GeometryFactory.java implementation is through the pre-configured local Moss source paths stored locally under ~/github/assofohdz/moss/, providing direct access to debug rendering glitches.

Does this approach cover all Moss modules like mphys and mworld for Java development?

Yes, this approach covers all Moss modules including mblock, mphys, mworld, and sio2-mblock, providing direct local source tree access to implementation details for Java game development workflows.

When do I need pre-configured source paths for Simsilica libraries like zay-es and SimEthereal?

You need pre-configured source paths for Simsilica libraries like zay-es and SimEthereal when debugging, extending, or auditing networking and ECS library internals during Java game development without extracting JARs.