antv-infographic
Template-driven medical infographics using the AntV Infographic framework. Use when creating structured infographics from clinical data, trial results, or patient education content using pre-built templates for hero stats, comparison layouts, process flows, myth-busters, and checklists. Outputs publication-ready HTML/PNG infographics with JACC/NEJM-grade design tokens.
What this skill does
# AntV Infographic Integration
**Purpose:** Template-driven medical infographics using the AntV Infographic framework
---
## Quick Start & Workflow
### Step 1 — List Available Templates
```bash
cd skills/cardiology/visual-design-system/antv_infographic
python scripts/antv_cli.py list --verbose
```
**Available Templates** (full catalog: see `TEMPLATES.md`):
1. `trial_result_simple` — Clinical trial timeline (4 phases)
2. `mechanism_of_action` — Drug mechanism steps (5 steps)
3. `treatment_comparison` — Side-by-side treatment comparison
4. `patient_journey` — Patient care pathway (5 stages)
5. `guideline_recommendations` — Guideline strength classification
6. `dosing_schedule` — Medication dosing schedule (4 weeks)
7. `safety_profile` — Adverse events by frequency
8. `biomarker_progression` — Biomarker changes over time
9. `trial_endpoints` — Primary and secondary endpoints
10. `risk_stratification` — Risk level classification
11. `diagnostic_pathway` — Diagnostic workflow (5 steps)
### Step 2 — Render to HTML
```bash
python scripts/antv_cli.py render \
--template mechanism_of_action \
--output outputs/mechanism_of_action.html \
--width 1000 --height 800 \
--title "Drug Mechanism"
```
### Step 3 — Validate Output
Confirm the HTML file exists and is non-empty before proceeding.
```bash
ls -lh outputs/mechanism_of_action.html # Should be >10KB; if missing or tiny, re-run with --verbose
```
### Step 4 — Download Output
Open the HTML in your browser (path is printed in CLI output), then click **Download SVG** (vector, editable) or **Download PNG** (raster, 2× resolution, publication quality).
---
### Python API
```python
from scripts.antv_renderer import render_template, AntvRenderer
# Quick render
output = render_template('trial_result_simple', 'output.html')
assert output.exists() and output.stat().st_size > 1000, "Render failed"
# Advanced usage
renderer = AntvRenderer()
renderer.render_template_to_html(
'mechanism_of_action',
'mechanism.html',
width=1000,
height=800,
title='Drug Mechanism of Action'
)
```
**Programmatic batch rendering:**
```python
from scripts.antv_renderer import AntvRenderer
renderer = AntvRenderer()
templates = ['trial_result_simple', 'mechanism_of_action', 'patient_journey']
for template in templates:
output = renderer.render_template_to_html(
template,
f'outputs/{template}.html',
width=1200,
height=900
)
assert output.exists() and output.stat().st_size > 1000, f"Render failed: {template}"
print(f"Generated: {output}")
```
---
## Template Examples
### Mechanism of Action (`mechanism_of_action`)
**Use for:** Drug mechanisms, biological pathways
```
infographic list-row-simple-vertical
data
items:
- label: Oral Administration
desc: Drug taken orally, absorbed in GI tract
- label: Systemic Distribution
desc: Reaches target organs via bloodstream
- label: Receptor Binding
desc: Binds to specific receptors at cellular level
- label: Cellular Response
desc: Triggers cascade of intracellular signaling
- label: Clinical Effect
desc: Measurable improvement in symptoms/outcomes
```
---
## Custom Spec Syntax
```
infographic [TEMPLATE_TYPE]
data
items:
- label: [LABEL_TEXT]
desc: [DESCRIPTION_TEXT]
```
**Template types:**
- `list-row-simple-horizontal-arrow` — Horizontal timeline with arrows
- `list-row-simple-vertical` — Vertical list with connectors
- (200+ more — see AntV documentation)
**Render custom spec:**
```bash
python scripts/antv_cli.py render \
--spec "infographic list-row-simple-horizontal-arrow
data
items:
- label: Step 1
desc: First action
- label: Step 2
desc: Second action" \
--output custom.html
```
---
## Visual Router Integration
**Routing keywords:** "template infographic", "structured infographic", "step-by-step infographic", "trial timeline", "mechanism steps", "treatment pathway infographic"
```python
from cardiology_visual_system.scripts.visual_router import VisualRouter
router = VisualRouter()
router.route("Create a template infographic showing trial timeline") # → AntV
# Other tools: custom infographic → Gemini | forest plot → Plotly | flowchart → Mermaid
```
---
## CLI Reference
```bash
python scripts/antv_cli.py list # Simple list
python scripts/antv_cli.py list --verbose # With descriptions
python scripts/antv_cli.py render \
--template mechanism_of_action \
--output outputs/mechanism.html \
--width 1000 --height 800 \
--title "Drug Mechanism"
python scripts/antv_cli.py examples # Generate all 11 examples to outputs/examples/
python scripts/antv_cli.py info # Show integration info
```
---
## Troubleshooting
| Symptom | Fix |
|---------|-----|
| HTML doesn't open automatically | Open manually; path is printed in CLI output |
| SVG download button fails | Use a modern browser (Chrome, Firefox, Safari); check console for errors |
| Python import error | Run from `skills/cardiology/visual-design-system/antv_infographic/` |
| Template not found | Check spelling; use `list --verbose`; templates live in `templates/*.txt` |
---
## References
- [AntV Infographic GitHub](https://github.com/antvis/Infographic)
- [AntV Documentation](https://antv.vision/en)
- [Full Template Catalog](TEMPLATES.md)
- [Python API Reference](API.md)
- [Visual Design System](../SKILL.md)
- [Visual Router](../../cardiology-visual-system/scripts/visual_router.py)
Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.