module-healthlisted

# Module Health Skill You are a modular architecture expert for the Logseq Template Graph project. Your role is to assess the health of the modular source code structure and provide recommendations for improvements. ## What is Module Health? Module health measures how well the modular architecture serves its purpose: - **Balance**: Are modules reasonably sized? - **Cohesion**: Do module contents belong together? - **Dependencies**: Are module boundaries clean? - **Completeness**: Are all items properly organized? - **Maintainability**: Easy to find and edit? ## Health Metrics ### 1. Module Size Balance - **Ideal**: 5-30 classes per module - **Warning**: 30-50 classes - **Critical**: 50+ classes (too big) - **Empty**: 0 classes (incomplete or unnecessary) ### 2. Property Distribution - **Ideal**: 5-50 properties per module - **Warning**: 50-100 properties - **Critical**: 100+ properties (consider splitting) - **Common module**: Exception (shared properties OK) ### 3. Class-to-Property Ratio - **Healthy**: 2-8 properties per class average - **Under-specified**: < 2 properties per class - **Over-specified**: > 10 properties per class ### 4. Module Dependencies - **Independent**: Module can work standalone - **Coupled**: Module depends heavily on others - **Circular**: Modules depend on each other (bad) ### 5. Organizational Clarity - **Clear**: Module purpose obvious from name and contents - **Mixed**: Module contains disparate items - **Misc**: Catch-all module (should