visualize-code
Analyze source code and generate architectural diagrams. Use when visualizing code structure, relationships, or workflows. Supports class, ER, sequence, and dependency diagrams.
What this skill does
# Visualize Code Command
Analyze source code files and automatically generate appropriate diagrams.
## Usage
```bash
/visualization:visualize-code <path> [diagram-type]
```
## Arguments
- `<path>` - File or directory to analyze (required)
- `[diagram-type]` - Optional: `class`, `er`, `sequence`, `dependency` (auto-detected if omitted)
## Examples
```bash
/visualization:visualize-code src/models
/visualization:visualize-code src/services/user.service.ts class
/visualization:visualize-code prisma/schema.prisma er
/visualization:visualize-code src/routes sequence
/visualization:visualize-code src dependency
```
## Supported Analysis Types
| Type | Trigger | Input |
| --- | --- | --- |
| `class` | TypeScript/Python/Java classes | `.ts`, `.py`, `.java`, `.cs` files |
| `er` | ORM/database schemas | `schema.prisma`, `models.py`, `*.entity.ts` |
| `sequence` | API route handlers | Route files with HTTP handlers |
| `dependency` | Import statements | Any source files |
## Execution
Delegate to the `visualization:code-visualizer` agent with the following prompt:
---
**Task:** Analyze source code and generate an appropriate diagram.
**Target:** $1 (path to analyze)
**Diagram Type:** $2 (optional - auto-detect if not specified)
**Instructions:**
1. **Discover files** at the specified path using Glob
2. **Determine analysis type** based on:
- Explicit diagram type argument (if provided)
- File patterns and content
3. **Read and analyze** the relevant source files
4. **Extract structure**:
- For class diagrams: classes, properties, methods, relationships
- For ER diagrams: entities, fields, keys, relationships
- For sequence diagrams: handlers, service calls, responses
- For dependency diagrams: imports, module relationships
5. **Generate diagram** using Mermaid syntax (preferred for GitHub rendering)
6. **Return results** with diagram and analysis notes
**Auto-Detection Rules:**
| File Pattern | Default Type |
| --- | --- |
| `schema.prisma` | ER |
| `models.py` (Django/SQLAlchemy) | ER |
| `*.entity.ts` | ER |
| `**/routes/**`, `*_controller.*` | Sequence |
| Generic `.ts`, `.py`, `.java` | Class |
**Output Format:**
Return:
1. Brief summary of what was analyzed (files, classes, entities, etc.)
2. The generated diagram in a ```mermaid code block
3. Any limitations or incomplete analysis notes
4. Suggestions for refinement
**Example Output for Class Diagram:**
Analyzed 5 files in `src/models/`:
- User.ts (1 class, 4 methods)
- Post.ts (1 class, 3 methods)
- Comment.ts (1 class, 2 methods)
```mermaid
classDiagram
class User {
+String id
+String email
+createPost()
+addComment()
}
...
```
Note: Some private utility methods were omitted for clarity.
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.