What problem does it solve? Developers working in the GRYLibrary repository need to know where code belongs, which components consumers depend on, and how to verify changes before fixing defects or building features. ## Core Features & Use Cases - Repository Orientation: Explains the common project structure with code-units and their Other-folders for build, quality-check, and reference files. - Consumer Impact Awareness: Documents that the NuGet package declares no dependencies and that API renames reach every consuming product, so changes must be made with downstream repositories in mind. - Build and Test Guidance: Describes building with scbuildcodeunits or the task bb, and the runsettings.xml coverage configuration (XPlat Code Coverage with cobertura format) the pipeline expects. - Use Case: Before fixing a defect in the APIServer middlewares, consult this Skill to learn that services must inject IServerLog rather than IGRYLog, avoiding a startup failure from an unresolvable service. ## Quick Start Ask the AI to explain where a new middleware belongs in GRYLibrary and how to build and test the change before committing it.
