---
name: diagrams-and-data-tables
description: >-
Guides the creation, structure, and styling of professional Mermaid diagrams
(sequence, flowcharts, ERD, state transitions) and high-density, accessible
data tables with glassmorphism, responsive behavior, micro-interactions, and WCAG compliance.
Use when designing data representations, documenting architecture, or implementing UI tables.
---
# Diagrams and Data Tables Skill
This skill enforces best practices for visualizing software architecture through **Mermaid diagrams** and creating production-grade, accessible **data tables** across the frontend and technical documentation.
---
## Part 1: Mermaid Diagrams Engineering
Mermaid diagrams provide living documentation of architectural patterns, data flows, and relational schemas.
### 1. Core Syntax Rules
- **Quote Node Labels**: Always quote labels containing special characters, brackets, or parentheses: `id["Process (Async)"]`.
- **Avoid HTML in Labels**: Use pure Markdown formatting or plain text; avoid `
` or raw tags where Mermaid may parse them incorrectly.
- **Direction & Clean Layout**: Use `flowchart TD` (top-down) for hierarchical flows or `flowchart LR` (left-to-right) for sequential pipelines.
### 2. Common Diagram Patterns
#### A. Sequence Diagram: WebSocket Client-Server Flow
```mermaid
sequenceDiagram
autonumber
actor User as Usuario / Client
participant UI as React Frontend
participant WS as WebSocket Server (Ratchet)
participant Auth as JWT Guard
participant RAG as RAG / Gemini Engine
participant DB as MySQL Database
User->>UI: Escribe mensaje
UI->>WS: {"action": "chat_message", "token": "jwt..."}
WS->>Auth: Validar token y rol
Auth-->>WS: Rol verificado (e.g. Interno)
WS->>RAG: Consultar Base Conocimiento / Embeddings
RAG->>DB: SELECT cosine_similarity...
DB-->>RAG: Documentos relevantes
RAG-->>WS: Stream chunks de respuesta
WS-->>UI: {"type": "stream_chunk", "chunk": "..."}
UI-->>User: Renderizado progresivo
```
#### B. Flowchart: RAG Query & Tool Routing
```mermaid
flowchart TD
A["Entrada del Usuario"] --> B{"¿Consulta de Horarios / Ambientes?"}
B -- "Sí" --> C["Tool: CRONODE API"]
B -- "No" --> D{"¿Búsqueda en Base de Conocimiento?"}
C --> E["Formatear Matriz / Calendario"]
D -- "Sí" --> F["Búsqueda Vectorial (Cosine Similarity)"]
D -- "No" --> G["Generación General Gemini LLM"]
F --> H["Inyectar Contexto RAG"]
H --> I["Generar Respuesta Verificada"]
E --> J["Enviar Payload + Table Data al Cliente"]
I --> J
G --> J
```
#### C. Entity-Relationship Diagram (ERD)
```mermaid
erDiagram
usuarios ||--o{ chat_historial : "posee"
usuarios ||--o{ conversaciones : "registra"
roles ||--o{ usuarios : "asigna_a"
categorias ||--o{ temas : "agrupa"
temas ||--o{ preguntas_respuestas : "contiene"
temas ||--o{ documentos : "asocia"
usuarios {
int id PK
string email
string rol
boolean activo
}
categorias {
int id PK
string nombre
text descripcion
}
temas {
int id PK
int categoria_id FK
string nombre
}
preguntas_respuestas {
int id PK
int tema_id FK
text pregunta
text respuesta
}
```
---
## Part 2: High-Density UI Data Tables
When creating data tables in the frontend (React / Tailwind / Vanilla CSS):
### 1. Visual Aesthetics & Design System Tokens
- **Glassmorphism Base**:
```html
| ID | Nombre |
|---|