do I get a high-level overview of a module's architecture in a large codebase?", "answer": "To get a high-level overview of module architecture, you can analyze the codebase to return an abstract view of the module's usage, interactions, and functionality. This approach focuses on inter-module relationships rather than line-by-line analysis."}, {"question": "What is the best way to understand module dependencies and interaction points?", "answer": "Understanding module dependencies and interaction points is achieved by mapping the calling and called modules. This generates a high-level relationship map, clarifying how a specific module fits and interacts within the broader codebase context."}, {"question": "Can I generate an abstracted module overview for code with multiple responsibilities?", "answer": "Yes, you can generate an abstracted module overview specifically for complex code with multiple responsibilities. It extracts the higher-level functionality and relevant component interactions, helping you navigate confusing sections without getting lost in implementation details."}, {"question": "How do I visualize inter-module relationships without reading code line by line?", "answer": "Visualizing inter-module relationships without line-by-line reading involves abstracting the codebase section to show usage and interaction points. You request a relationship map for the target module to quickly see its broader architectural context and dependencies."}, {"question": "When do I need to use dependency mapping for code understanding?", "answer": "You need dependency mapping for code understanding when navigating a large codebase without a clear big picture. It is specifically useful when struggling with a large module's multiple responsibilities and you need insights into its place and interactions."}]2b:T5a5,## What problem does it solve? The Skill simplifies the process of creating and managing draw.io diagrams by enabling diagram generation through code, eliminating the need for manual creation or editing of draw.io files. ## Core Features & Use Cases - **Diagram Generation**: Automatically create diagrams in draw.io native format from code. - **File Export**: Export diagrams in various formats (PNG, SVG, PDF) with embedded diagram XML for easy editing. - **Use Case**: Ideal for documenting processes, software architecture, and flowcharts in code, reducing manual efforts and ensuring consistency across all documents. ### Quick Start Use the drawio skill to generate a diagram of a simple process, saved as 'process_flow.drawio', with the following XML: ``` 2c:T790,[{"question": "How do I generate draw.io diagrams automatically using code?", "answer": "You can generate draw.io diagrams automatically by writing native mxGraphModel XML code, which the Skill processes to create diagram files without manual editing. This ensures consistent diagram creation for software architecture and flowcharts."}, {"question": "Can I export draw.io diagrams to PNG, SVG, or PDF?", "answer": "Yes, you can export generated draw.io diagrams to PNG, SVG, and PDF formats. These exports embed the original diagram XML, allowing you to easily edit the visual output later without rebuilding the diagram from scratch."}, {"question": "Do I need to know mxGraphModel to create draw.io diagrams?", "answer": "Yes, familiarity with mxGraphModel and draw.io native XML is required to creat

botteryosuke

Agent Skills by botteryosuke

post-impl-skill-update

e2e-automated

pair-nav

improve-codebase-architecture

diagnose

to-issues

skill-creator

behavior-to-e2e

zoom-out

drawio

e2e-testing

parallel-agent-dev

pair-relay

nautilus-trader

grill-with-docs

bevy-engine

auto-pair-relay

tdd

to-prd

rust-testing

create-skill

brand-writer

humanizer