diagram

The Diagram skill is a specialized tool for developers and architects practicing Diagram Driven Development (DDD). It facilitates the creation, synchronization, and maintenance of 'Unified Impact Diagrams' stored in an ai/diagrams repository. Unlike standard technical documentation, DDD focuses on bridging the gap between Front-Stage user experiences and Back-Stage technical implementations. This skill ensures that every system diagram serves as a living, accurate reflection of the codebase, forcing explicit links between technical components and the user value they deliver.

• Automatically generates and updates sequence, architecture, and feature flow diagrams using Mermaid syntax.

• Performs comprehensive audits to detect outdated or missing diagrams by cross-referencing file history and repository structure.

• Manages an index of all visual documentation within README.md to maintain a single source of truth for system understanding.

• Validates technical diagrams against DDD principles, ensuring they include impact annotations, user-centric entry points, and error-path recovery documentation.

• Enforces strict naming conventions and organizational patterns (features, journeys, architecture, tests, refactoring) to keep the project documentation navigable.

• Incorporates Before/After refactoring documentation with visual highlighting for improved system transparency.

• Users must load relevant reference documentation (e.g., DDD_PRINCIPLES.md, CREATE.md, MERMAID_GUIDE.md) using the Read tool before executing operations to ensure adherence to quality standards.

• Input typically involves feature specifications or code diffs, while outputs are structured markdown files containing Mermaid diagrams, key insights, and clear change histories.

• Constraints include a prohibition on custom colors, except for specific refactoring impact indicators (#90EE90), and a requirement that every diagram maintains a balance between technical depth and user-facing impact.

• This tool is ideal for agile teams looking to reduce technical debt, improve architectural onboarding for new contributors, and ensure that feature development remains aligned with user journey requirements.