Documd Visuals logo

Documd Visuals

OrganizationPopular
markdown-viewer
documd-visuals

Create text-driven visuals in Markdown: charts, diagrams, cards, architecture and page layouts. Charts and analytical views (bar, line, pie, heatmap, correlation, regression); reliability and operations (latency, incident, throughput, cycle time, OKR, standup, on-call); product and finance (funnel, retention, revenue, budget); process and workflow (approval, BPMN); software design and behaviour (class, state machine, sequence, C4); dependencies and impact (dependency graph, ER, causality); system architecture as HTML (layer stack, wings, zones, topology, service catalogue, request paths); infrastructure (cloud, Kubernetes, ETL, network, security, IAM, compliance); governance and people (ArchiMate, org chart, hiring); knowledge and planning (mind map, roadmap, Gantt, migration); documents (comparison, SWOT, memo, policy, catalogue, case study). Use when a document needs a diagram, chart or card. Figures render live. Not for slide decks or math notation. Not recommended: mermaid / canvas / drawio / dot.

Overview

Publishermarkdown-viewer
Repositoryskills
Skill namedocumd-visuals
Stars
3.4K
Forks
191
Bundled files
353
LicenseCC-BY-4.0
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 353 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by markdown-viewer on GitHub. Read the source before you install it.

Installation

Install the Documd Visuals AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/markdown-viewer/skills/tree/main/documd-visuals
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/markdown-viewer/skills.git /tmp/skills
mkdir -p .claude/skills
cp -r /tmp/skills/documd-visuals .claude/skills/documd-visuals
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Documd Visuals in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Documd Visuals on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Documd Visuals is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

documd visuals

Routing for every diagram, chart, card and layout this document pipeline can render.

Figures are text, in place. A fence (plantuml · vega · echarts · infographic) or bare HTML written into the Markdown is the figure: the viewer draws it live, the block stays editable, and nothing is pre-rendered, built or exported first. documd is optional — export and verification only.

Iron rules

  1. Allowed fences — plantuml / puml · vega · vega-lite · echarts · infographic, plus bare HTML — which is how system architecture diagrams, cards and page layouts are drawn.
  2. Nothing outside that list. A fence the list does not name is a bug, not a lesser option — there is no second-tier engine.
  3. One diagram per fence. Do not put two engines in one block, and never nest fences.
  4. HTML is bare, never ```html — a fenced block becomes an image. Start from a real file rather than inventing one: layered-with-wings.md for a system, executive-brief-summary.md for a card.
  5. Inline the data. vega / vega-lite / echarts must carry their own values / series data; external URLs are unreliable on the export path.
  6. State the reading in the copy. Every figure answers one question — put it in the prose or the block's title.
  7. Pick a theme, then colour from it. Colours come from one of the themes indexed in styles/palette.md; copy that theme's block for your engine and take every value from it — a hex picked by hand, or two themes in one figure, is a bug. Charts pass the categorical ramp in order; cards use one accent plus neutrals.

Route by goal

Find the reader's goal, open the goal guide, pick an example. Engines are suggestions; the guide and examples are authoritative.

A — data & metrics

GoalTrigger keywordsEnginesRead
service-reliabilitylatency · p95/p99 · SLO · SLA · error budget · burn rate · availability · uptime · reliabilityecharts vega infographicgoals/service-reliability.md
ops-monitoringincident load · alert volume · outliers · anomalies · service scorecard · support volumeecharts vega infographicgoals/ops-monitoring.md
delivery-throughputthroughput · cycle time · lead time · velocity · capacity · staffing · backlog · WIP · rank movementecharts vega infographicgoals/delivery-throughput.md
goal-and-status-reportingOKR · KPI · target vs actual · goal attainment · status board · dashboard · scorecardecharts vega infographic html-cssgoals/goal-and-status-reporting.md
product-metricsconversion · funnel · adoption · retention · churn · activation · signup · cohorts · experimentecharts infographicgoals/product-metrics.md
business-reportingquarterly results · revenue · ARR · revenue mix · margin · periodic results · forecastinfographic vega echartsgoals/business-reporting.md
go-to-marketpipeline · channel · partner · partner tiers · market entry · sales funnel · SWOT · campaignsecharts infographicgoals/go-to-market.md
cost-and-budgetcost · spend · budget · cloud bill · savings · cost reduction · capex · unit economicsecharts infographic vegagoals/cost-and-budget.md
data-explorationcorrelation · distribution · regression · outlier detection · missing data · small multiples · densityvega echartsgoals/data-exploration.md

B — process & systems

GoalTrigger keywordsEnginesRead
engineering-operationsstandup · sprint ritual · team rhythm · on-call · coverage · shift handover · deploy cadence · checklistinfographic vega echartsgoals/engineering-operations.md
incident-managementincident · postmortem · escalation · triage · runbook · change request · launch readiness · reviewinfographic echarts html-cssgoals/incident-management.md
process-and-workflowapproval · workflow · swimlane · SOP · process map · BPMN · gate · procurementplantuml infographicgoals/process-and-workflow.md
software-designclass · domain model · component · package · layering · use case · object · C4 container · SysMLplantumlgoals/software-design.md
software-behaviourstate machine · lifecycle · sequence · interaction · messaging · event flow · EIP · deploymentplantumlgoals/software-behaviour.md
dependencies-and-relationsdependency · call graph · impact analysis · coupling · ownership · causality · fishboneplantuml vega echarts infographicgoals/dependencies-and-relations.md
system-architecturesystem architecture · layer stack · zones · pipeline stages · service catalog · request path · connectorshtml-cssgoals/system-architecture.md

C — infrastructure & governance

GoalTrigger keywordsEnginesRead
cloud-architectureAWS · Azure · Kubernetes · container · serverless · IoT · edge · VPC · observabilityplantuml infographicgoals/cloud-architecture.md
data-platformETL · lakehouse · warehouse · CDC · streaming · ingestion · catalog · ML pipeline · ER modelplantumlgoals/data-platform.md
network-topologynetwork · topology · DMZ · wireless · firewall · switch · packet · route · trafficplantuml echartsgoals/network-topology.md
security-and-compliancezero trust · IAM · encryption · threat model · trust boundary · controls · evidence · audit · compliance · riskplantuml infographic html-cssgoals/security-and-compliance.md
enterprise-architectureArchiMate · capability map · value stream · stakeholder map · business architectureplantuml infographicgoals/enterprise-architecture.md
organization-and-rolesorg chart · reporting line · workforce · capability coverage · capability maturity · handoffs · responsibilitiesinfographic vega echarts html-cssgoals/organization-and-roles.md
people-and-hiringhiring · headcount plan · interview loop · onboarding · career ladder · certifications · progressioninfographicgoals/people-and-hiring.md

D — knowledge & expression

GoalTrigger keywordsEnginesRead
knowledge-and-outlinemind map · outline · knowledge map · concept map · topics · word cloudplantuml infographic vega echartsgoals/knowledge-and-outline.md
planning-and-roadmaproadmap · milestone · timeline · Gantt · quarterly plan · release schedule · strategy focusinfographic vega plantuml html-cssgoals/planning-and-roadmap.md
migration-and-rolloutmigration · cutover · rollout waves · phased delivery · programme · work breakdownplantuml infographicgoals/migration-and-rollout.md
comparison-and-selectioncompare · versus · build or buy · decision record · quadrant · vendor selection · trade-off · priorityinfographic html-cssgoals/comparison-and-selection.md
internal-documentsmemo · brief · charter · abstract · policy · quote · principleshtml-css infographicgoals/internal-documents.md
catalogues-and-inventoriescatalogue · inventory · entitlements · offerings · standard tools · support tiersinfographicgoals/catalogues-and-inventories.md
customer-and-partner-commscustomer story · case study · sales brief · bulletin · announcement · partner brief · education modulehtml-cssgoals/customer-and-partner-comms.md
theme-and-toneprint · photocopy · handout · low vision · large print · colour-blind · slide · projected · long-forminfographic echarts plantumlgoals/theme-and-tone.md

Engine cheat sheet

EngineReach for it whenLook elsewhere when
plantumlUML/ArchiMate/BPMN semantics, brand and device icons (9,514 stencils), or a relationship graph that should lay itself outIt is a chart
vega / vega-liteThe data needs work first — join, window, fold, regression, density, facets, small multiplesOne polished chart with heavy styling (echarts)
echartsReport-grade chart or KPI dashboard: axes, series, thresholds, annotations, gaugesThe data must be transformed first
infographicA designed-looking board: roadmap, timeline, checklist, comparison, quadrant, knowledge mapAxes, several series or statistical shapes (echarts)
HTML/CSSCards, memos, overviews, page-level layoutsAnother engine already renders that diagram

Details, limits and pitfalls: plantuml · echarts · vega · infographic · html-css.

Capability boundaries

These are not possible; pick the fallback instead of retrying.

WantFallback
3D / globe / WebGL charts (no echarts-gl)2D echarts; scatter/graph for shape
Geographic maps (no bundled map data, no GeoJSON offline)schematic rectangle layout, or an HTML/CSS region diagram
dataset.transform in ECharts (throws RangeError in 6.1.0)sort and derive upstream, then dataset.source
Functions in an echarts option (parsed as JSON)template strings ("{c}%"), per-item label objects
External data or images (data.url, remote URLs)inline values, data URLs
PlantUML WBS / Salt / Timing / ditaa / JSON / YAML / EBNF / nwdiag / SDL / math (parse, draw nothing useful)@startmindmap, a boxed rectangle tree, HTML/CSS mockups, or a code fence
Interactive charts (tooltip, zoom, brush)annotate directly: labels, thresholds, callouts
Icons in vega / echartsplantuml stencils
Free-form positioning in infographicHTML/CSS for pixel control

Reading a document

To read a document in the browser or in VS Code, install docu.md Markdown Viewer: https://docu.md.

Exporting & verifying — optional

Authoring never needs this. The documd CLI converts a document or a diagram source to a file, extracts figures as images, and verifies that blocks render — for when the output is a file. Nothing to install: npx @markdown-viewer/documd in.md out.docx. Flags, formats and the npm-scope warning: converting.md.

When a block does not render

  1. Fence in the allowed list? Exactly one block per figure?
  2. Is it a listed anti-pattern in that engine's reference (see Engine cheat sheet) — or strict syntax (JSON for echarts/vega, no empty lines in bare HTML)?
  3. Then switch to the alternative engine the goal guide names; most scenarios have two.
  4. Or verify by rendering: npx @markdown-viewer/documd file.md --assets /tmp/figs.

Where everything lives

catalog/scenarios.md indexes every scenario with its domain, engines, tier and example path — start there; then goals/<domain>.md, engines/<engine>.md, examples/<domain>/<file>.md.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

and 140 more files.

Frequently asked questions

What does the Documd Visuals AI skill do?

Create text-driven visuals in Markdown: charts, diagrams, cards, architecture and page layouts. Charts and analytical views (bar, line, pie, heatmap, correlation, regression); reliability and operations (latency, incident, throughput, cycle time, OKR, standup, on-call); product and finance (funnel, retention, revenue, budget); process and workflow (approval, BPMN); software design and behaviour (class, state machine, sequence, C4); dependencies and impact (dependency graph, ER, causality); system architecture as HTML (layer stack, wings, zones, topology, service catalogue, request paths); i...

Why use Documd Visuals on TypingMind?

Because you install it once and use it with any model. Documd Visuals is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Documd Visuals in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/markdown-viewer/skills/tree/main/documd-visuals. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Documd Visuals?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Documd Visuals?

As many as you like. As long as a model supports skills, you can use Documd Visuals with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Documd Visuals AI skill free?

Yes. It is published on GitHub by markdown-viewer under the CC-BY-4.0 license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇