mo-architecture

What problem does it solve?

Provides a single-source-of-truth architecture for Monica modules to eliminate inconsistency, unclear boundaries, and ad-hoc folder layouts that cause maintenance pain and coupling between layers.

Core Features & Use Cases

• Standardized Layering: Defines public vs internal layers (Abstractions, Models, Facades, Services, Providers, Modules, Annotations) and the Internal/ sub-folder convention to make visibility explicit.
• Folder & Grouping Rules: Prescribes folder depth limits, prefix-naming over subfolders, when to introduce feature folders, and localization placement exceptions.
• Facade/Service/Provider Patterns: Clarifies Facade responsibilities, Service naming and scope, Provider separation, and Module registration conventions including ModuleBase vs WebModuleBase guidance.
• UI & Page Patterns: Describes Mixed/Standalone/Composite UI layouts, page decomposition rules, state patterns, and red flags for refactoring.

Quick Start

Ask the skill to design or refactor a Monica module (infrastructure, UI, or mixed) and produce a folder layout, naming conventions, public/internal boundaries, Facade placement, and provider separation recommendations.