What problem does it solve?
This skill codifies Gosling2's architectural rules to prevent architectural drift and enforce maintainable, modular design across the codebase.
Core Features & Use Cases
- Layered Hierarchy enforcement: UI (src/presentation/), Business (src/business/), Data (src/data/), and Core (src/core/) with explicit import permissions to avoid cross-layer coupling.
- Governance & modularization: God Object ban (no file > 600 lines) and splitting guidance to keep components focused and maintainable.
- Service Bus discipline: Sibling widgets communicate via a central LibraryService or EventBus to decouple UI and business logic.
- Resource discipline: Centralized constants, logging, utilities, and config practices with no inline UI logic in data layer.
- Use Case: When adding a new feature, teams map code to the four layers and document dependencies to prevent leakage.
Quick Start
Review the existing architecture rules in rules/architecture.md and ensure new modules conform to the four-layer model, service-bus communication, and god-object guidelines; update governance documentation as needed.
