Explicit module boundaries
Interfaces define what other modules and LLMs need to know; implementations stay hidden until needed.
DRG Framework Concept
Optional Unity architecture for better module composition and LLM context.
The framework is not the core product. DRG is module-first. The framework is the direction for composing modules like ads, consent, analytics, attribution, remote config, and saves, making boundaries explicit, increasing useful context for LLMs, and spending fewer tokens to explain how a Unity game works.
Problems developers search for
When the code works, but explaining it to an LLM costs too much context.
"How do I structure Unity modules so an LLM can understand the public contracts without reading every implementation?"
"How do I keep SDK flows, services, signals, lifecycle, and feature boundaries explicit enough for safe AI-assisted changes?"
"How do I reduce token usage when asking an LLM to modify a Unity game architecture?"
Concept
A structure for getting more useful LLM output from less context.
Predictable runtime flow
Lifecycle states, scoped services, and queued signals reduce hidden coupling and make behavior easier to explain.
Optional adoption
Use standalone modules first, then add framework structure when the project grows or LLM assistance becomes more valuable.
Platform growth
Upcoming attribution and remote config modules follow the same explicit contracts and replaceable provider adapter pattern.
Install
Add framework pieces only when composition helps.
https://github.com/yanmasharski/drg.core.git#1.0.0
https://github.com/yanmasharski/drg.framework.git#1.0.0Module-first