mermaid-diagram

分类: 文档与知识管理 | 上传者: drillan | 下载: 0 | 版本: v1.0（最新）
使用 sphinx-oceanid 在 Sphinx 文档中编写美人鱼图。支持 MyST Markdown (.md) 和 reStructuredText (.rst) 语法。防止常见错误，例如使用不受支持的图表类型。
更新日志: Source: GitHub https://github.com/drillan/sphinx-oceanid
目录结构

当前层级: tree/main/skills/mermaid-diagram/
📄 SKILL.md 9.5 KB
SKILL.md

---
name: mermaid-diagram
license: BSD-3-Clause
description: >
  Write Mermaid diagrams in Sphinx documentation using sphinx-oceanid.
  Supports both MyST Markdown (.md) and reStructuredText (.rst) syntax.
  Prevents common mistakes like using unsupported diagram types.

  MUST trigger when:
  - Editing .md/.rst files under docs/ where docs/conf.py contains sphinx_oceanid
  - User asks to add a diagram (flowchart, sequence, class, state, ER, chart)
  - User mentions 'mermaid'/'diagram' or wants to visualize architecture,
    workflows, data flows, hierarchies, or state machines

  SHOULD trigger proactively when documentation describes:
  - Processes/workflows (suggest flowchart)
  - Component interactions or API calls (suggest sequenceDiagram)
  - Class hierarchies or module relationships (suggest classDiagram)
  - State transitions or lifecycles (suggest stateDiagram)
  - Data models or entity relationships (suggest erDiagram)
  - Numeric data, comparisons, or trends (suggest xychart-beta)
---

# Mermaid Diagrams with sphinx-oceanid

This project uses [sphinx-oceanid](https://github.com/drillan/sphinx-oceanid/) to render Mermaid diagrams in Sphinx documentation. sphinx-oceanid uses the beautiful-mermaid rendering engine (ELK.js layout), which produces high-quality SVG output but only supports a specific set of diagram types.

## Activation Check

Before applying this skill, verify the project uses sphinx-oceanid:

1. Check if `docs/conf.py` (or `conf.py` at project root) exists
2. Verify it contains `sphinx_oceanid` in the `extensions` list

If these conditions are not met, this skill does not apply — do not suggest mermaid directives or proactive diagrams.

## Supported Diagram Types

Only these 6 types are supported. Using any other type causes a build warning or error:

| Type | Alias | Use Case |
|------|-------|----------|
| `flowchart` | `graph` | Workflows, decision trees, data pipelines |
| `sequenceDiagram` | — | API interactions, message flows between components |
| `classDiagram` | — | Class hierarchies, module relationships |
| `stateDiagram` | `stateDiagram-v2` | State machines, lifecycle transitions |
| `erDiagram` | — | Data models, entity relationships |
| `xychart-beta` | — | Bar charts, line charts with numeric axes |

**Not supported** (will produce errors): gantt, pie, gitGraph, journey, mindmap, timeline, sankey-beta, quadrantChart, block-beta, kanban, architecture-beta, and others. If a user needs one of these, explain the limitation and suggest an alternative from the supported types or a different approach (e.g., a table, an image).

## Syntax (MyST Markdown)

This project uses MyST (Markdown) for documentation. Use the `{mermaid}` directive:

````markdown
```{mermaid}
flowchart LR
  A[Input] --> B[Process] --> C[Output]
```
````

### With Options

````markdown
```{mermaid}
:caption: System Architecture
:alt: Architecture diagram showing data flow
:align: center
:zoom:

flowchart TD
  API[API Server] --> DB[(Database)]
  API --> Cache[Redis Cache]
```
````

### External .mmd File

````markdown
```{mermaid} diagrams/architecture.mmd
:caption: Full Architecture
:zoom:
```
````

The path is relative to the Sphinx source directory (`docs/`). The `.mmd` file contains only the Mermaid code (no directive syntax).

## Syntax (reStructuredText)

For `.rst` files, use the standard RST directive syntax:

```rst
.. mermaid::

   flowchart LR
     A[Input] --> B[Process] --> C[Output]
```

### With Options

```rst
.. mermaid::
   :caption: System Architecture
   :alt: Architecture diagram showing data flow
   :align: center
   :zoom:

   flowchart TD
     API[API Server] --> DB[(Database)]
     API --> Cache[Redis Cache]
```

### External .mmd File

```rst
.. mermaid:: diagrams/architecture.mmd
   :caption: Full Architecture
   :zoom:
```

### Auto Class Diagram (RST)

```rst
.. autoclasstree:: mypackage.MyClass
   :full:
   :namespace: mypackage
   :caption: MyClass class hierarchy
   :zoom:
```

### Syntax Selection Rule

- `.md` files → MyST syntax (`` ```{mermaid} ``)
- `.rst` files → RST syntax (`.. mermaid::`)
- Directive options are identical for both formats

## Directive Options

| Option | Type | Description |
|--------|------|-------------|
| `:caption:` | text | Rendered as `<figcaption>` below the diagram |
| `:alt:` | text | Accessibility text (`aria-label`) |
| `:align:` | `left` / `center` / `right` | Horizontal alignment |
| `:zoom:` | flag (no value) | Enable mouse wheel zoom and drag pan |
| `:name:` | text | Unique ID for cross-references |
| `:title:` | text | Mermaid-native title (inside diagram) |
| `:config:` | JSON | Per-diagram Mermaid config override |

## Diagram Examples

### Flowchart — Data Pipeline

````markdown
```{mermaid}
:caption: Market Data Pipeline
:align: center

flowchart LR
  Fetch[Fetch OHLCV] --> Clean[Clean & Validate]
  Clean --> Store[(Parquet Store)]
  Store --> Analyze[Analysis Engine]
  Analyze --> Report[Generate Report]
```
````

### Sequence Diagram — API Call

````markdown
```{mermaid}
:caption: Quote Retrieval Flow
:align: center

sequenceDiagram
  participant C as Client
  participant A as API
  participant D as Database
  C->>A: Request quotes
  A->>D: Query Parquet
  D-->>A: Return data
  A-->>C: JSON response
```
````

### State Diagram — Order Lifecycle

````markdown
```{mermaid}
:caption: Order State Machine

stateDiagram-v2
  [*] --> Pending
  Pending --> Submitted: Place order
  Submitted --> Filled: Execution
  Submitted --> Cancelled: Cancel
  Filled --> [*]
  Cancelled --> [*]
```
````

### ER Diagram — Data Model

````markdown
```{mermaid}
:caption: Market Data Schema

erDiagram
  COMMODITY ||--o{ QUOTE : has
  COMMODITY {
    string code PK
    string name
    string exchange
  }
  QUOTE {
    date date PK
    float open
    float high
    float low
    float close
    int volume
  }
```
````

### XY Chart — Performance

````markdown
```{mermaid}
:caption: Monthly Returns

xychart-beta
  title "Strategy Monthly Returns (%)"
  x-axis [Jan, Feb, Mar, Apr, May, Jun]
  y-axis "Return (%)" -5 --> 10
  bar [2.1, -1.3, 4.5, 3.2, -0.8, 5.1]
  line [1.0, 0.5, 2.0, 2.5, 1.5, 3.0]
```
````

### Class Diagram — Module Structure

````markdown
```{mermaid}
:caption: Analysis Module Hierarchy

classDiagram
  class BaseAnalyzer {
    +load_data()
    +validate()
    +analyze()*
  }
  class QuotesAnalyzer {
    +analyze()
    +calc_ohlcv()
  }
  class TicksAnalyzer {
    +analyze()
    +calc_vwap()
  }
  BaseAnalyzer <|-- QuotesAnalyzer
  BaseAnalyzer <|-- TicksAnalyzer
```
````

## Auto Class Diagrams

Generate class hierarchy diagrams automatically from Python code:

````markdown
```{autoclasstree} market_analysis.QuotesAnalyzer
:full:
:namespace: market_analysis
:caption: QuotesAnalyzer class hierarchy
:zoom:
```
````

| Option | Description |
|--------|-------------|
| `:full:` | Traverse full inheritance tree (up to `object`) |
| `:strict:` | Only classes defined in the specified module |
| `:namespace:` | Filter base classes by this namespace prefix |

## conf.py Configuration

The current project has `sphinx_oceanid` in extensions. Additional settings can be added to `docs/conf.py`:

```python
# Theme auto-detects dark/light from Shibuya theme (default: "auto")
oceanid_theme = "auto"

# Enable zoom on all diagrams globally (default: False)
oceanid_zoom = True

# Enable fullscreen modal button (default: False)
oceanid_fullscreen = True

# Action for unsupported diagram types: "warning" or "error" (default: "warning")
oceanid_unsupported_action = "warning"
```

## Proactive Diagram Suggestions

When editing `docs/*.md` or `docs/*.rst` files, analyze the text content and suggest diagrams where visualization would improve comprehension. **Never insert a diagram without explicit user approval.**

### Detection Patterns

| Text Pattern | Suggested Diagram | Example |
|---|---|---|
| Steps, flows, pipelines (A then B then C) | flowchart | "Fetch data, transform, then store" |
| Messages between components, request/response | sequenceDiagram | "Client sends a request to the API..." |
| Class inheritance, module dependencies | classDiagram | "Inherits from BaseHandler..." |
| State transitions, lifecycles | stateDiagram | "Order goes from Pending to Confirmed to Shipped..." |
| Entity relationships, data models | erDiagram | "A user has many orders" |
| Numeric data, comparisons, trends | xychart-beta | "Monthly revenue: Jan 100, Feb 150..." |

### How to Suggest

When a diagram opportunity is detected, suggest in this format:

1. **Where**: The location to insert the diagram (after which paragraph/section)
2. **Why**: One sentence explaining why this diagram type fits
3. **What**: The elements the diagram should contain

Example suggestion:

> This process description would be clearer as a **flowchart**.
> Elements: [Fetch] → [Transform] → [Store]
> Shall I add it after this paragraph?

Only write the Mermaid code after the user approves. If the user declines, continue without adding a diagram.

## Best Practices

- **Always verify the diagram type is supported** before writing. The 6 supported types cover most visualization needs.
- **Use `:caption:` and `:alt:`** for accessibility and context.
- **Use `:zoom:` for complex diagrams** — especially flowcharts with many nodes or detailed ER diagrams.
- **Prefer inline code over .mmd files** for small diagrams (under ~20 lines). Use external `.mmd` files for large, reusable diagrams.
- **Build and preview** after adding diagrams: `uv run make -C docs html` then serve with a local HTTP server (Mermaid requires HTTP, not `file://`).
- **Keep diagrams focused** — split large diagrams into smaller, focused ones rather than one monolithic diagram.
登录后下载/点赞/收藏 ❤ 8 | ★ 0
mermaid-diagram

目录结构

SKILL.md

举报内容

提示
