Run any Skill in Manus with one click

diagram-generation

Generate self-contained HTML architecture diagrams. Use when creating visual diagrams for PRs, task plans, or architectural explanations.

Run Skill in Manus

Overview

Generate self-contained HTML architecture diagrams. Use when creating visual diagrams for PRs, task plans, or architectural explanations.

Install command

npx skills add https://github.com/abudhahir/projects-pkm --skill diagram-generation

Copy and paste this command into Claude Code to install the skill

Source

abudhahir/projects-pkm

Stars0

Forks0

UpdatedApril 22, 2026 at 19:51

File Explorer

3 files

SKILL.md

readonly

name	diagram-generation
description	Generate self-contained HTML architecture diagrams. Use when creating visual diagrams for PRs, task plans, or architectural explanations.

Diagram Generation

Generate self-contained HTML diagrams that visualize code changes, data flows, and architecture decisions.

When to Use

Visualizing PR changes for code review
Explaining architectural decisions
Documenting data/request flows
Illustrating before/after comparisons

Output

Self-contained HTML file at diagrams/opik-{TICKET_NUMBER}-diagram.html
Includes "Copy as image" button for sharing in Slack, Jira, PR descriptions
Dark GitHub theme, semantic color coding, responsive layout

How to Generate

Follow the style guide in style-guide.md and use the HTML template in template.md.

Required Sections (pick what applies)

Request / Data Flow — how data moves through layers
Why This Approach — problem vs solution comparison
Files Changed by Layer — grid of affected files grouped by component
Key Design Decisions — numbered guards, trade-offs, or constraints

Section Selection

Bug fix: Focus on before/after flow, root cause, safety guards
New feature: Focus on data flow, architecture, files changed
Refactor: Focus on before/after architecture, files changed
Cross-component: Show all layers with connecting flows

Reference Files

style-guide.md — Semantic colors, box themes, section labels, flow patterns, architecture trees
template.md — Base HTML structure, copy-as-image script, section recipes

Common Gotchas

SRI hash on CDN scripts: The html2canvas <script> tag must include integrity and crossorigin attributes — see template.md for the current hash
Absolute paths for Playwright screenshots: Playwright saves relative to its own CWD, not the repo root — always use absolute paths when calling browser_take_screenshot
Max 4 sections: More than 4 sections makes diagrams too tall for screenshots and hard to scan visually
No raw diff content: Diagrams show high-level summaries (component names, file names, flow descriptions) — never embed verbatim diff hunks or Jira comments
toBlob can return null: The Canvas toBlob call in the copy-as-image script needs a null check — see template.md

More from this repository

same repository

backend-patterns

abudhahir/projects-pkm

Backend architecture patterns, API design, database optimization, and server-side best practices for Node.js, Express, and Next.js API routes.

2026-05-210

agent-identifier

abudhahir/projects-pkm

This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development best practices for Claude Code plugins.

2026-04-220

skill-development

abudhahir/projects-pkm

This skill should be used when the user wants to "create a skill", "add a skill to plugin", "write a new skill", "improve skill description", "organize skill content", or needs guidance on skill structure, progressive disclosure, or skill development best practices for Claude Code plugins.

2026-04-220

visual-explainer

abudhahir/projects-pkm

Generate beautiful, self-contained HTML pages that visually explain systems, code changes, plans, and data. Use when the user asks for a diagram, architecture overview, diff review, plan review, project recap, comparison table, or any visual explanation of technical concepts. Also use proactively when you are about to render a complex ASCII table (4+ rows or 3+ columns) — present it as a styled HTML page instead.

2026-04-220

azure-architecture-diagram

abudhahir/projects-pkm

This skill should be used when a user wants to generate a visual architecture diagram of an Azure subscription's infrastructure. It discovers all resources via Azure CLI (or Azure MCP if available), maps them to mingrammer/diagrams Python nodes, generates executable Python code, and renders a PNG architecture diagram grouped by resource group. Trigger phrases include "generate azure diagram", "visualize azure subscription", "draw my azure infrastructure", "create azure architecture diagram", "diagram my azure resources", "map my azure environment".

2026-04-220

azure-resource-visualizer

abudhahir/projects-pkm

Analyze Azure resource groups and generate detailed Mermaid architecture diagrams showing the relationships between individual resources. USE FOR: create architecture diagram, visualize Azure resources, show resource relationships, generate Mermaid diagram, analyze resource group, diagram my resources, architecture visualization, resource topology, map Azure infrastructure DO NOT USE FOR: creating/modifying resources (use azure-deploy), security scanning (use azure-security), performance troubleshooting (use azure-diagnostics), code generation (use relevant service skill)

2026-04-220

Source

abudhahir

abudhahir/projects-pkm

View GitHub Repository View Creator Repositories

Install command

Download

Run Skill in Manus

Useful forSOC

Software DevelopersComputer and Mathematical Occupations15-1252L4

name	diagram-generation
description	Generate self-contained HTML architecture diagrams. Use when creating visual diagrams for PRs, task plans, or architectural explanations.

Diagram Generation

Generate self-contained HTML diagrams that visualize code changes, data flows, and architecture decisions.

When to Use

Visualizing PR changes for code review
Explaining architectural decisions
Documenting data/request flows
Illustrating before/after comparisons

Output

Self-contained HTML file at diagrams/opik-{TICKET_NUMBER}-diagram.html
Includes "Copy as image" button for sharing in Slack, Jira, PR descriptions
Dark GitHub theme, semantic color coding, responsive layout

How to Generate

Follow the style guide in style-guide.md and use the HTML template in template.md.

Required Sections (pick what applies)

Request / Data Flow — how data moves through layers
Why This Approach — problem vs solution comparison
Files Changed by Layer — grid of affected files grouped by component
Key Design Decisions — numbered guards, trade-offs, or constraints

Section Selection

Bug fix: Focus on before/after flow, root cause, safety guards
New feature: Focus on data flow, architecture, files changed
Refactor: Focus on before/after architecture, files changed
Cross-component: Show all layers with connecting flows

Reference Files

style-guide.md — Semantic colors, box themes, section labels, flow patterns, architecture trees
template.md — Base HTML structure, copy-as-image script, section recipes

Common Gotchas

SRI hash on CDN scripts: The html2canvas <script> tag must include integrity and crossorigin attributes — see template.md for the current hash
Absolute paths for Playwright screenshots: Playwright saves relative to its own CWD, not the repo root — always use absolute paths when calling browser_take_screenshot
Max 4 sections: More than 4 sections makes diagrams too tall for screenshots and hard to scan visually
No raw diff content: Diagrams show high-level summaries (component names, file names, flow descriptions) — never embed verbatim diff hunks or Jira comments
toBlob can return null: The Canvas toBlob call in the copy-as-image script needs a null check — see template.md