What problem does it solve? When designing reusable modules, integrating third-party systems, or wiring up configuration, teams often blur module boundaries, rely on implicit auto-registration, confuse reference documents with runtime sources of truth, and let fallbacks silently mask broken core logic. This Skill provides a structured set of engineering principles to keep module boundaries clean and configuration explicit. ## Core Features & Use Cases - Three-Layer Module Design: Classifies capabilities into core layer, preset layer, and project integration layer, with clear rules for what belongs in each. - Explicit Installation & Configuration: Enforces explicit bootstrap/registration over implicit side effects, and explicit Inspector/registry configuration over runtime guessing for stable structures. - Single Source of Truth & Controlled Degradation: Distinguishes reference material from runtime truth, and restricts fallback/no-op behavior to genuinely optional capabilities. - Use Case: When extracting a shared capability from a Unity project into a reusable module, use this Skill to decide which layer each piece belongs to, how it should be installed, which references must be explicitly configured, and how to verify the wiring. ## Quick Start Use the module-boundary-and-configuration skill to review whether my new module's layering, installation, and configuration follow clean boundary principles.
