thatrebeccarae/claude-marketing / skills/tech-diagram
tech-diagram
VerifiedGenerate technical architecture diagrams, pipeline flows, layer/stack diagrams, and system illustrations as standalone HTML files. Uses a dark-mode design system with embedded CSS and inline SVG. Use when the user needs architecture diagrams, system illustrations, flow charts, or technical visualizations.
| File | Kind | Size |
|---|---|---|
| EXAMPLES.md | markdown | 2.5 KB |
| LICENSE | other | 1.0 KB |
| REFERENCE.md | markdown | 7.7 KB |
| SKILL.md | skill md | 4.3 KB |
EXAMPLES.md
View on GitHub# Tech Diagram — Examples
## Example 1: Data Pipeline Architecture
**Prompt:**
> Create a diagram showing our ETL pipeline: S3 ingestion → Spark transform → Snowflake warehouse → dbt models → Looker dashboards
**Expected output:** A standalone HTML file with a 5-stage horizontal pipeline flow, each stage colored with a different accent, connecting arrows between stages, and a brief description under each stage label.
---
## Example 2: Tech Stack Layers
**Prompt:**
> Show our tech stack as a layer diagram: Infrastructure (AWS), Platform (Kubernetes), Services (Go microservices), API Gateway (Kong), Frontend (Next.js)
**Expected output:** A vertical stack diagram with 5 layers, bottom to top from infrastructure to frontend. Each layer has a distinct background tint and lists the key technologies.
---
## Example 3: Microservices Component Map
**Prompt:**
> Map out our microservices: Auth Service (Go), User Service (Go), Payment Service (Java), Notification Service (Python), API Gateway (Kong). Auth talks to User and Payment. Gateway routes to all.
**Expected output:** A grid of 5 component boxes with the service name, language tag, and status indicator. Connection lines or arrows showing the communication paths described.
---
## Example 4: Migration Timeline
**Prompt:**
> Create a timeline for our database migration: Phase 1 (Jan) — Schema design, Phase 2 (Feb) — Dual-write setup, Phase 3 (Mar) — Shadow reads, Phase 4 (Apr) — Cutover, Phase 5 (May) — Decommission legacy
**Expected output:** A vertical timeline with 5 milestones, each showing the phase name, month, and a one-line description. Completed phases in green, current in blue, future in muted gray.
---
## Example 5: Before/After Architecture
**Prompt:**
> Show before/after: Before — monolith Rails app with MySQL, single server. After — microservices with API gateway, Redis cache, PostgreSQL, deployed on Kubernetes.
**Expected output:** A side-by-side split diagram. Left side shows a single box (monolith) connected to MySQL. Right side shows multiple service boxes connected through an API gateway, with Redis and PostgreSQL as separate data stores.
---
## Example 6: KPI Dashboard Header
**Prompt:**
> Create a metrics row showing: Uptime 99.97%, P95 Latency 142ms (down 12%), Error Rate 0.03%, Deployments 47/month (up 8%)
**Expected output:** A horizontal row of 4 metric cards with large monospace numbers, labels, and trend indicators (green up arrows, red down arrows as appropriate).
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| 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: 198k | Updated | Claude CodeCodex | Verified | Install |
| 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: 119k | Updated | Claude CodeCodex | Verified | Install |
| 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: 118k | Updated | Claude CodeCodex | Verified | Install |