Skip to content

heymegabyte/agent-skills / 12-media-orchestration

media-orchestration

Verified

Section-by-section media planning and generation. Image generation (GPT Image 2 primary, built-in fallback), logo/icon generation (Ideogram v3 → favicon set), video generation (Veo 3.1), social preview images (OG 1200x630 + AI search optimization), stock photo curation (Pexels, Pixabay), critique/remix loops (max 3 rounds), asset compression pipeline, and media performance budgets.

FileKindSize
30-ideogram-methods.mdmarkdown16.0 KB
SKILL.mdskill md6.7 KB
build-breaking-rules.mdmarkdown48.2 KB
compression-pipeline.mdmarkdown3.8 KB
image-optimization.mdmarkdown6.6 KB
image-profiling.mdmarkdown3.2 KB
lightbox-classifier.mdmarkdown10.0 KB
media-prompts.mdmarkdown3.8 KB
notebooklm-pipeline.mdmarkdown22.1 KB
og-card-pipeline.mdmarkdown19.5 KB
og-image-generation.mdmarkdown8.5 KB
social-brand-hex.mdmarkdown3.8 KB
technical-diagramming.mdmarkdown4.4 KB
templates/PROMPTS.mdmarkdown10.0 KB

technical-diagramming.md

View on GitHub
---
name: Technical Diagramming
description: ASCII, Mermaid, SVG diagram generation for architecture docs, data flows, and system maps
version: "2.0.0"
updated: "2026-04-23"
---

# Technical Diagramming

## Format Selection

- **ASCII** — README/terminal/inline docs, zero dependencies, universal rendering
- **Mermaid** — GitHub/GitLab auto-render, versioned in markdown, CI-friendly
- **SVG** — high-fidelity exports, presentations, external docs
- **D2** — declarative alternative to Mermaid, auto-layout

### When to Use Which

- **README** — ASCII (renders everywhere, no extensions)
- **GitHub PR/wiki** — Mermaid (native rendering, diffable)
- **Architecture doc** — Mermaid + SVG export (version + present)
- **Terminal output** — ASCII (monospace guaranteed)
- **Slide deck** — SVG/PNG via `freeze` (high-fidelity)

## ASCII Diagrams

### Box-Drawing Characters

```
┌─────────┐    ┌──────────┐    ┌─────────┐
│  Client  │───▶│  Worker  │───▶│   D1    │
└─────────┘    └──────────┘    └─────────┘
                    │
                    ▼
              ┌──────────┐
              │    R2    │
              └──────────┘
```

Chars:

- `┌ ─ ┐ │ └ ┘ ├ ┤ ┬ ┴ ┼` for boxes
- `─→ ──▶ ◀── ←─` for arrows
- `···` for optional
- `═══` for emphasis

### Reusable Architecture Template

```
┌──────────────────────────────────────────┐
│              Cloudflare Edge             │
│  ┌────────┐  ┌────────┐  ┌────────┐     │
│  │ Worker │  │  KV    │  │  R2   │     │
│  └───┬────┘  └────────┘  └────────┘     │
│      │                                   │
│  ┌───▼────┐  ┌────────┐                 │
│  │   D1   │  │  DO    │                 │
│  └────────┘  └────────┘                 │
└──────────────────────────────────────────┘
```

## Mermaid.js

### Diagram Types

- `flowchart` — system arch
- `sequence` — API flows
- `classDiagram` — data models
- `erDiagram` — DB schema
- `stateDiagram` — state machines
- `gantt` — timelines
- `C4Context` — high-level arch

### Flowchart

```mermaid
flowchart LR
    A[Client] -->|HTTPS| B[CF Worker]
    B -->|Query| C[(D1)]
    B -->|Store| D[(R2)]
    B -->|Cache| E[KV]
    B -->|Auth| F[Clerk]
```

### Sequence

```mermaid
sequenceDiagram
    participant U as User
    participant W as Worker
    participant C as Clerk
    participant D as D1
    U->>W: POST /api/checkout
    W->>C: verifyToken()
    C-->>W: userId
    W->>D: INSERT order
    D-->>W: orderId
    W-->>U: {url: checkout}
```

### ER Diagram

```mermaid
erDiagram
    USER ||--o{ ORDER : places
    ORDER ||--|{ LINE_ITEM : contains
    PRODUCT ||--o{ LINE_ITEM : "ordered in"
```

## Tools

- **`freeze`** (charm.sh) — code/diagram → PNG, terminal-native
- **`mmdc`** (mermaid-cli) — `.mmd` → SVG/PNG/PDF, CI integration
- **`d2`** (terrastruct) — declarative diagrams, auto-layout, themes
- **Excalidraw** — hand-drawn aesthetic, collaborative, embeddable

### freeze Example

```bash
freeze --language mermaid -o arch.png diagram.mmd
```

### mermaid-cli

```bash
npx -p @mermaid-js/mermaid-cli mmdc -i diagram.mmd -o diagram.svg -t dark -b '#060610'
```

## Best Practices

- Left-to-right flow (LR) default, top-to-bottom (TB) for hierarchies
- Max 7±2 nodes per diagram — split complex systems into sub-diagrams
- Label ALL edges — unlabeled arrows are ambiguous
- Color for grouping not decoration — subgraphs with fills
- Consistent spacing — align nodes vertically/horizontally
- Dark theme: bg `#060610`, node fill `#1a1a2e`, text `#e0e0e0`, edge `#00E5FF`

## Ownership

- **Owns** — Diagram generation (ASCII + Mermaid + SVG + D2), architecture visualization, data flow diagrams, ER diagrams, deployment maps
- **Never owns** — Image generation (→ image-gen), brand design (→ 09), UI mockups (→ 10)
writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deploymentStars: 322kUpdated Claude CodeCodexVerifiedInstall
xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.Stars: 119kUpdated Claude CodeCodexVerifiedInstall
childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release.Stars: 118kUpdated Claude CodeCodexVerifiedInstall