deepwiki-ascii-diagrams

# ASCII Diagram Generation Skill

Professional ASCII-based diagram generation for technical documentation. This skill provides templates and guidelines for creating clean, maintainable architectural diagrams that integrate seamlessly into documentation systems.

## Diagram Standards

### ASCII Character Sets

**Standard Boxes (Components, Services)**
```
┌─────────────────┐
│   Component     │
│    or Service   │
└─────────────────┘
```

**Double-Line Boxes (External Systems, APIs)**
```
╔═════════════════╗
║   External      ║
║   System/API    ║
╚═════════════════╝
```

**Bold/Heavy Boxes (Databases, Storage)**
```
┏━━━━━━━━━━━━━━━━━┓
┃    Database     ┃
┃    or Storage   ┃
┗━━━━━━━━━━━━━━━━━┛
```

**Dashed Boxes (Optional, Conditional)**
```
┌┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┐
┆  Optional      ┆
┆  Component     ┆
└┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┘
```

### Connection Types

| Symbol | Meaning | Usage |
|--------|---------|-------|
| `────►` | Synchronous request | Direct API calls, HTTP requests |
| `◄────►` | Bidirectional | WebSocket, duplex connections |
| `- - - - ►` | Asynchronous/Event | Message queues, events, webhooks |
| `════════►` | Data flow | Large data transfers, streaming |
| `······►` | Optional/Conditional | Optional integrations |
| `~~~~►` | Real-time/WebSocket | WebSocket connections |

### Connection Labels

```
   "GET /api/users"
        ↓
    ┌────────┐
    │API     │
    │Gateway │
    └────────┘
        ↓
   "JSON response"
```

Connection labels should be placed:
- **Above arrows** for top-to-bottom flows
- **Beside arrows** for left-to-right flows
- **In brackets [like this]** for explanatory notes
- **With protocol names** for technical clarity

## Quality Guidelines

### Layout Principles

1. **Alignment**: Related components should align vertically or horizontally
2. **Spacing**: Minimum 2 characters between unconnected elements
3. **Consistency**: Use same box sizes for same-level components
4. **Hierarchy**: Position parent systems above children
5. **Flow Directio