eraser-diagrams

これはレビュー時に保存された抜粋です。完全で最新の内容は外部ソースを確認してください。

---
name: eraser-diagrams
description: 'Generates architecture diagrams from code, infrastructure, or descriptions. Use when user asks to visualize, diagram, or document system architecture.'
license: MIT
compatibility: Requires network access to call Eraser API
allowed-tools: Read Write Bash(curl:*)
metadata:
  version: "1.0.0"
  author: Eraser Labs
  tags: diagram, architecture, infrastructure, visualization, terraform, aws, azure, cloud
---

# Eraser Diagram Generator

Generates professional architecture diagrams directly from code, infrastructure files, or natural language descriptions using the Eraser API.

## When to Use

Activate this skill when:

- User asks to create, generate, or visualize a diagram
- User wants to document architecture from code
- User has Terraform, AWS, Azure, or infrastructure files
- User describes a system and wants it visualized
- User mentions "diagram", "architecture", "visualize", or "draw"

## How It Works

1. **Analyze the source**: Extract architecture information from code, files, or descriptions
2. **Generate Eraser DSL**: Create Eraser DSL code that describes the diagram
3. **Call the Eraser API**: Make an HTTP POST request to render the diagram
4. **Return the result**: Present the image URL and editor link to the user

## Diagram Types and Syntax

Eraser supports five types of diagrams, each optimized for different use cases. For detailed DSL syntax and examples, refer to the appropriate reference file:

### Flow Charts

Visualize process flows, user flows, and logic flows represented as nodes, groups, and relationships. Diagrams are created using simple syntax.

**Use for**: Process flows, user journeys, decision trees, business process documentation

**diagramType**: `"flowchart-diagram"`

**Reference**: [Flowchart Syntax](references/flowchart-syntax.md)

### Entity Relationship Diagrams (ERD)

Visualize data models represented as entities, attributes, and relationships. Diagrams are created using simple syntax.

**Use for**: Database schema design, data modeling, understanding entity relationships, documenting data structures

**diagramType**: `"entity-relationship-diagram"`

**Reference**: [ERD Syntax](references/erd-syntax.md)

### Cloud Architecture Diagrams

Visualize cloud infrastructure represented as nodes, groups, and connections. Diagrams are created using simple syntax.

**Use for**: Cloud infrastructure visualization, AWS/Azure/GCP architectures, system architecture documentation, data flow visualization

**diagramType**: `"cloud-architecture-diagram"`

**Reference**: [Architecture Syntax](references/architecture-syntax.md)

### Sequence Diagrams

Visualize system flows using sequence diagrams. Each vertical column represents an entity (e.g. user, server, DB) and arrows between the columns represent the flow of information or requests. Diagrams are created using simple syntax.

**Use for**: API request/response flows, system interactions, user workflows, message passing between services, process flows over time

**diagramType**: `"sequence-diagram"`

**Reference**: [Sequence Syntax](references/sequence-syntax.md)

### BPMN Diagrams (Swimlane Diagrams)

Visualize business processes represented as pools, lanes, and flow objects such as tasks, events, and gateways. Diagrams are created using simple syntax.

**Use for**: Business process documentation, workflow visualization, process improvement, cross-functional processes, swimlane diagrams showing roles/responsibilities

**diagramType**: `"bpmn-diagram"`

**Reference**: [BPMN Syntax](references/bpmn-syntax.md)

Each reference file contains complete syntax documentation, property references, and practical examples.

## API Integration

### Endpoint

```
POST https://app.eraser.io/api/render/elements
Content-Type: application/json
Authorization: Bearer ${ERASER_API_KEY}
X-Skill-Source: eraser-skill
```

**Note**: The `X-Skill-Source` header identifies the AI agent. You MUST replace `eraser-skill` with your actual agent nam