メニュー
Mermaid diagram syntax for flowcharts, sequence, class, state, module, ER, GitFlow. Use when generating Mermaid diagrams in documentation, technical designs, or architecture.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | mermaid-diagrams |
| description | Mermaid diagram syntax for flowcharts, sequence, class, state, module, ER, GitFlow. Use when generating Mermaid diagrams in documentation, technical designs, or architecture. |
flowchart (not deprecated graph); 2 spaces indentA["Text with → arrow"]#8594; for →; line breaks: <br>subgraph, loop, alt, opt, par — with endflowchart TD (top-down) or flowchart LR (left-right)[rect], (rounded), {diamond}, ((circle)), ([stadium])--> solid, -.-> dotted, ==> thick; labels: -->|Yes|flowchart TD
A[Start] --> B{Decision}
B -->|Yes| C[Action 1]
B -->|No| D[Action 2]
C --> E([End])
D --> E
participant Name as Label->> async, -> sync, -->> responseloop, alt, opt, par — close with endNote right of B: textsequenceDiagram
participant A as Client
participant B as Server
A->>B: Request
B-->>A: Response
loop Retry
B->>B: Validate
end
+ public, - private, # protected<|-- inheritance, *-- composition, o-- aggregation"1" --> "0..*"stateDiagram-v2; start/end: [*]State1 --> State2 : Eventstate StateName { ... }stateDiagram-v2
[*] --> State1
State1 --> State2 : Event
state State1 {
[*] --> SubState1
SubState1 --> SubState2
}
State2 --> [*]
flowchart TB + subgraph "Group Name" for architecture layer groupingflowchart LR for component interaction; label protocols: -->|HTTP/REST|(()); service nodes: []erDiagram||--o{ one-to-many, ||--|| one-to-one, }o--o{ many-to-many{}; mark PK/FK/UKgitGraphbranch name, checkout name, merge namecommit id: "label"graph)endstateDiagram-v2flowchart TB + subgraphsequenceDiagramflowchartstateDiagramMCP server usage for Dart MCP, Firecrawl, Hugging Face. Tool priorities, commands, workflows.
Development process rules. Use when planning complex tasks, implementing incrementally, managing packages, or following communication guidelines.
Dart 3 patterns including switch/if-case, pattern matching, sealed classes, and records. Use when writing exhaustive switches, destructuring, pattern matching on types, or returning multiple values with records.
Core code quality rules for Dart/Flutter. Use when formatting, handling async/null safety, organizing classes, or following Dart best practices.
Code review checklist for PRs/MRs. Use when reviewing pull requests, examining code changes, or when the user asks for a code review.
Data handling patterns for Dart/Flutter. Use when implementing serialization, caching, layer separation, DTOs, repositories, offline-first, or data validation.