class-module-diagramming

What problem does it solve?

This skill helps engineers visualize and communicate code structure by generating Mermaid class diagrams that reflect classes, interfaces, enums, and modules with proper visibility and relationships, enabling clearer design reviews and documentation.

Core Features & Use Cases

• One purpose per diagram — focus diagrams on a single objective like domain model, module layout, or architecture layering.
• Show what matters — omit trivial members; emphasize visibility modifiers and key relationships (inheritance, composition, association, dependency).
• Explicit visibility & relationships — display + public, - private, # protected, ~ package visibility and distinct relations (inheritance, implementation, composition, aggregation, association, dependency).
• Phase-driven approach — guide from Subject/Scope/Audience/Sources through element types (Class, Interface, Enum, Abstract, Packages) to members and domain/module diagrams.
• Quick-startable workflows — provide a concise, practical sequence to generate diagrams from real code, with examples and caveats.

Quick Start

Describe the subject and scope to generate a Mermaid class diagram of the code structure.