'diagram' 검색 결과

Choose, create, and review software diagrams that explain structure, interactions, workflows, states, or data relationships. Select suitable notation and rendering tools, then plan static exports or interactive views with readable layouts, accessible controls, and validation.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Explain login interactions with a sequence diagram
• Turn a database schema into an entity relationship diagram
• Document application architecture with C4

Convert suitable diagrams in Mastra documentation into Mermaid, a text format for diagrams, or create new ones. Assess which images to keep, follow diagram styling rules, and verify layout and readability in light and dark modes.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Replace box-and-arrow images with Mermaid diagrams
• Add a new diagram to Mastra documentation
• Fix diagram readability in light and dark modes

Create text diagrams with PlantUML for README files, emails, and terminal workflows. Convert diagram definitions into plain ASCII or Unicode box-drawing output to share interactions and relationships where image-based diagrams are unsuitable.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Add text diagrams to README files
• Share sequence diagrams in emails
• View diagrams in a terminal

Use when you need to generate Java project diagrams — including UML sequence diagrams, UML class diagrams, C4 model diagrams, UML state machine diagrams, UML Deployment Diagrams, ER (Entity Relationship) diagrams, and bounded-context diagrams — through a modular, step-based interactive process that adapts to your specific visualization needs. This should trigger for requests such as Generate UML diagram; Create sequence diagram; Create class diagram; Create state machine diagram; Create deployment diagram; Create C4 diagram; Create bounded-context diagram; Create context-map diagram. Part of Plinth Toolkit

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Create editable draw.io diagrams from descriptions, code, infrastructure settings, or database schemas. Update existing diagrams while preserving manual layout, check their structure and architecture rules, and export them to image or document formats for sharing.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Turn a written description into an editable diagram
• Generate architecture diagrams from code or infrastructure settings
• Update a diagram while preserving manual layout

Create editable FigJam diagrams for workflows, system architecture, data relationships, and schedules. The skill selects a suitable diagram type and guides Mermaid, a text format for diagrams, while accounting for rendering limits.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Visualizing a workflow or decision tree
• Mapping services and data stores
• Showing API interactions over time

Create editable FigJam diagrams for workflows, system architecture, data relationships, and schedules. The skill selects a suitable diagram type and guides Mermaid, a text format for diagrams, while accounting for rendering limits.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Visualizing a workflow or decision tree
• Mapping services and data stores
• Showing API interactions over time

Create Mermaid diagrams from text to explain software structure, API interactions, workflows, and database relationships. The skill guides diagram selection, syntax, styling, and export, helping keep visual documentation editable and stored alongside code.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Explaining system architecture with diagrams
• Mapping API requests and responses
• Documenting database table relationships

Understand a public GitHub repository through GitDiagram's architecture overview. Get an explanation of its main components, source paths, and connections, plus Mermaid diagram source and an interactive diagram for exploring the code.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Getting an overview of an unfamiliar public repository
• Finding source paths for major components
• Understanding connections and data flow

Turn notes, prose, code, schemas, or tables into editable diagrams, including flowcharts, architecture diagrams, and schedules. Choose Mermaid, Graphviz DOT, PlantUML, or SVG to suit the content, with image or PDF rendering when needed.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Turn business procedures into flowcharts
• Diagram system architecture and dependencies
• Visualize database relationships and interactions

Turn system structures, processes, and concepts into dark-themed diagrams. Create architecture diagrams, flowcharts, timelines, and other visual explanations as scalable SVG files, with PNG versions for use as images.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Explain system components and their connections
• Map process steps and decision branches
• Show interactions in chronological order

AWS の構成図を draw.io の XML（.drawio）で描く。公式の AWS4 アイコンを使い、タイトルや凡例や番号バッジのような装飾を足さず、どのサービスがどこにあって何とつながっているかだけで読める図にする。AWS 構成図、アーキテクチャ図、インフラ構成図、ネットワーク構成図、VPC の図を描いてほしいとき、draw.io で AWS の図を作りたいとき、既存の構成図を直したいときは必ずこの Skill を使う。Use this whenever the user asks for an AWS architecture diagram, cloud infrastructure diagram, VPC diagram, or a draw.io file of AWS resources, even if they don't say "draw.io". Mermaid、PlantUML、Python の diagrams ライブラリなど、ほかの形式を指定されたときは使わない。Do not use it when the user explicitly asks for Mermaid, PlantUML, or the Python diagrams library.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Turn descriptions or code analysis into Mermaid diagrams for workflows, system architecture, and database relationships. Check diagram syntax and export SVG, PNG, or text-based ASCII output, with themes and batch rendering options.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Visualizing system architecture
• Documenting API request sequences
• Drawing database relationships

Creates professional logical flow diagrams and logical system architecture diagrams using draw.io XML format (.drawio files). Use when creating: (1) logical flow diagrams showing data/process flow between system components, (2) logical architecture diagrams representing system structure without cloud provider specifics, (3) BPMN process diagrams, (4) UML diagrams (class, sequence, activity), (5) data flow diagrams (DFD), (6) decision flowcharts, or (7) system interaction diagrams. This skill focuses on generic/abstract representations, not AWS/Azure-specific architectures (use aws-drawio-architecture-diagrams for cloud diagrams).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

MANDATORY prerequisite — load this skill BEFORE every `generate_diagram` tool call. NEVER call `generate_diagram` directly without loading this skill first. Trigger whenever the user asks to create, generate, draw, render, sketch, or build a diagram — flowchart, architecture diagram, sequence diagram, ERD or entity-relationship diagram, state diagram or state machine, gantt chart, or timeline. Also trigger when the user mentions Mermaid syntax or wants a system architecture, decision tree, dependency graph, API call flow, auth handshake, schema, or pipeline visualized in FigJam. Routes to type-specific guidance, sets universal Mermaid constraints, and tells you when to use a different diagram type or skip the tool entirely (mindmaps, pie charts, class diagrams, etc.).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Generate database relationship diagrams from Entity Framework Core models, mappings, and migrations. Produce D2 diagram source showing tables, keys, relationships, and constraints, with display options for columns and grouping. The d2 CLI can render SVG or PNG images.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Document an EF Core project's database structure
• Review primary keys and foreign key relationships
• Visualize owned types and many-to-many join tables

Turn a codebase into architecture documentation with Mermaid diagrams. Using the C4 model, a way to describe systems at different levels of detail, the skill explains external relationships, applications, internal components, deployment, and request flows.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Explaining a system overview to stakeholders
• Documenting relationships between apps and databases
• Mapping internal components of a feature

Explore how a public GitHub repository is organized using GitDiagram. Get explanations tied to component names and source paths, an interactive architecture diagram, and a narrated explainer video when one is available.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Preparing to work in an unfamiliar public codebase
• Understanding major components and their source paths
• Exploring component connections in an interactive diagram

Add Mermaid diagrams to generated wiki pages to explain request flows, state changes, data relationships, and branching logic. Keep diagrams aligned with inspected source code and repair syntax problems in diagrams degraded during earlier runs.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Illustrate requests passing between components
• Show job lifecycles and state transitions
• Document relationships between data entities

Turn written descriptions into editable Excalidraw diagrams, including flowcharts, mind maps, system architecture, and database relationships. Generate a .excalidraw JSON file with connected shapes, labels, and a consistent sketch or clean visual style.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Turning business procedures into flowcharts
• Organizing ideas into mind maps
• Drawing cloud architecture with service icons

Comprehensive guide for creating software diagrams using Mermaid syntax. Use when users need to create, visualize, or document software through diagrams including class diagrams (domain modeling, object-oriented design), sequence diagrams (application flows, API interactions, code execution), flowcharts (processes, algorithms, user journeys), entity relationship diagrams (database schemas), C4 architecture diagrams (system context, containers, components), state diagrams, git graphs, pie charts, gantt charts, or any other diagram type. Triggers include requests to "diagram", "visualize", "model", "map out", "show the flow", or when explaining system architecture, database design, code structure, or user/application flows.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when creating editable technical diagrams with draw.io / diagrams.net sources, including architecture diagrams, ERD, UML, sequence diagrams, flowcharts, ML model diagrams, official shape lookup, brand symbols, Graphviz auto-layout, codebase structure maps, .drawio validation, or draw.io CLI export fallback. Do not use for ordinary raster image generation, freehand sketches, interactive canvas/Three.js scenes, or decorative SVG animation. Chinese triggers include draw.io, diagrams.net, editable architecture diagrams, .drawio, ER diagrams, UML, sequence diagrams, auto layout, shape retrieval, code structure diagrams.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Comprehensive guide for creating software diagrams using Mermaid syntax. Use when users need to create, visualize, or document software through diagrams including class diagrams (domain modeling, object-oriented design), sequence diagrams (application flows, API interactions, code execution), flowcharts (processes, algorithms, user journeys), entity relationship diagrams (database schemas), C4 architecture diagrams (system context, containers, components), state diagrams, git graphs, pie charts, gantt charts, or any other diagram type. Triggers include requests to "diagram", "visualize", "model", "map out", "show the flow", or when explaining system architecture, database design, code structure, or user/application flows.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Guia completo para criar diagramas de software usando sintaxe Mermaid. Use quando usuários precisarem criar, visualizar ou documentar software por meio de diagramas, incluindo diagramas de classe (modelagem de domínio, design orientado a objetos), diagramas de sequência (fluxos de aplicação, interações de API, execução de código), fluxogramas (processos, algoritmos, jornadas do usuário), diagramas de relacionamento de entidades (esquemas de banco de dados), diagramas de arquitetura C4 (contexto do sistema, containers, componentes), diagramas de estado, git graphs, gráficos de pizza, gráficos de Gantt ou qualquer outro tipo de diagrama. Acionadores incluem solicitações para "diagram", "visualize", "model", "map out", "show the flow" ou ao explicar arquitetura de sistema, design de banco de dados, estrutura de código ou fluxos de usuário/aplicação.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.