Visual Card logo

Visual Card

Community
NatsuFox
visual-card

Generate professional visual note cards (视觉笔记卡片/信息图) from knowledge base content as single-page HTML infographics with PNG export. Use when users want to create visual summaries, knowledge cards, infographics, or poster-style visualizations of topics from the knowledge base.

Overview

PublisherNatsuFox
RepositoryTapestry
Skill namevisual-card
Stars
64
Forks
5
Bundled files
8
LicenseMIT
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.

  • 8 bundled files

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

  • Open source

    Published by NatsuFox on GitHub. Read the source before you install it.

Installation

Install the Visual Card 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.
  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/NatsuFox/Tapestry.git /tmp/Tapestry
mkdir -p .claude/skills
cp -r /tmp/Tapestry/skills/tapestry/visual-card .claude/skills/visual-card
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Visual Card 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 Visual Card 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 Visual Card 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.

Tapestry Visual Card

Generate professional visual note cards from knowledge base content: $ARGUMENTS

When to use this skill

Use this skill when:

  • A user wants to create a visual note card or infographic from KB content
  • The user asks to "visualize", "create a card", "make an infographic", or "generate a visual summary"
  • The user mentions 视觉笔记, 知识卡片, 信息图, or one-pager summary
  • You need to present knowledge base content in a shareable, poster-style format
  • The user wants to export KB content for social media or presentations

Purpose

This skill transforms structured knowledge base content into beautiful, information-dense visual cards following an editorial magazine aesthetic. It produces:

  1. A self-contained HTML file with embedded styles and export functionality
  2. A high-quality PNG image (via Playwright rendering)

The cards follow a fixed layout structure optimized for readability and social sharing.

Workflow

Architecture: Agent-Driven Content Synthesis

This skill uses an Agent-driven approach where the Agent reads the template specification and autonomously decides how to map source content to template blocks.

Key principle: The template structure is fixed (7 display blocks), but content mapping is intelligent and adaptive.

Step 1: Identify the Source Content

Resolve the target from the argument:

  • If a specific chapter path is provided (e.g., "ai-and-development-tools/ai-agent-architecture.md"), use that chapter
  • If a topic is provided (e.g., "ai-and-development-tools"), offer to generate cards for its chapters
  • If no argument, list available topics and ask the user to choose
bash
# List available topics
ls -d data/books/*/

Step 2: Run the Context Preparation Script

bash
python visual-card/_scripts/generate_card.py --chapter "<topic>/<chapter.md>"

This prints a JSON object with three keys:

  • source.content: the raw chapter markdown
  • source.frontmatter: parsed metadata (title, author, date, etc.)
  • template_specification: full natural language spec of the 7 template blocks
  • instructions: task description

Step 3: Read the Template Specification

Read visual-card/_templates/card_template_spec.md to understand:

  • What each of the 7 blocks is for
  • Quality criteria for content selection
  • Expected JSON output format with examples

Step 4: Synthesize the Content Mapping (Agent Task)

Analyze the source content against the template spec and produce a synthesis JSON. Write it to a temp file:

bash
# Write synthesis to temp file
cat > /tmp/card_synthesis.json << 'EOF'
{
  "metadata": {
    "chapter": "<chapter-name>",
    "title_en": "<English title, 3-8 words>",
    "title_cn": "<Chinese title>",
    "topic_label": "<TOPIC LABEL IN CAPS>",
    "source_label": "<SOURCE IN CAPS>",
    "thesis": "<one sentence with <strong>keyword</strong> embedded>"
  },
  "framework": {
    "formula": "<A × B × C format>",
    "formula_subtext": "<what the formula means>",
    "label": "<FRAMEWORK NAME>",
    "components": [
      {"letter": "A", "name": "Component Name", "description": "One-line description"}
    ]
  },
  "insights": [
    {"number": "01", "title": "Insight Title", "description": "2-3 sentence insight description"}
  ],
  "dark_panel": {
    "icon": "⚡",
    "section_title": "<Section Title>",
    "block1": {"title": "<Block 1 Title>", "items": ["item 1", "item 2", "item 3"]},
    "block2": {"title": "<Block 2 Title>", "items": ["item 1", "item 2", "item 3", "item 4"]},
    "conclusion": {"label": "核心洞察", "text": "<conclusion text>", "highlight": "<highlighted phrase>"}
  },
  "closing_thought": {
    "text": "<memorable closing insight>",
    "attribution": "<author or source>"
  }
}
EOF

Content decisions to make:

  • Framework: Identify 2-6 core concepts that structure the topic (acronym or logical grouping)
  • Insights: Select 3-5 most surprising, actionable, or paradigm-shifting points
  • Dark panel: Narrative flow — overview → key mechanics → conclusion
  • Thesis: A single provocative claim that captures the article's core argument
  • Closing thought: A memorable synthesis that gives the reader something to carry away

Step 5: Generate HTML/PNG from Synthesis

bash
python visual-card/_scripts/generate_card_from_synthesis.py \
  --synthesis /tmp/card_synthesis.json \
  --chapter "<topic>/<chapter.md>"

This renders the synthesis into the HTML template and exports PNG via Playwright.

Step 6: Present the Results

Report back with:

  • The generated PNG path (primary deliverable)
  • The HTML path (for browser-based editing/export)
  • A brief summary of the content mapping decisions made

Card Design System

The visual cards follow a fixed editorial layout:

┌──────────────────────────────────────────┐
│ TOPIC LABEL              SOURCE LABEL    │  ← Top Bar
├────────────────────┬─────────────────────┤
│ English Title      │ Thesis statement    │  ← Title Area
│ 中文标题            │ with key insight    │
├─────┬─────┬─────┬──┴──────────────────────┤
│  M  │  P  │  D  │  G  │                  │  ← Framework Row (2-6 cards)
├─────┴─────┴─────┴─────┴──────────────────┤
│ ⚡ Dark Panel      │ ★ Light Panel        │  ← Two-Column Content
│ (narrative/story)  │ (numbered insights)  │
├──────────────────────────────────────────┤
│ Formula = M × P × D × G    Closing note  │  ← Highlight Bar
├──────────────────────────────────────────┤
│ FRAMEWORK LABEL              BRAND NAME   │  ← Footer
└──────────────────────────────────────────┘

Color Palette

Default theme (customizable):

  • Primary: Deep teal #1a7a6d
  • Accent: Orange #e8713a
  • Background: Warm gray #f0ebe4
  • Dark panel: #1a1a1a

Typography

  • English display: Playfair Display (serif)
  • Chinese body: Noto Sans SC
  • Monospace/labels: JetBrains Mono

Content Strategy

When generating cards from KB content:

  1. Extract or synthesize a framework - Identify the core structural model (2-6 components)
  2. Create a memorable acronym - Make the framework easy to remember
  3. Write a provocative thesis - Strong, opinionated claim in the title area
  4. Dark panel = narrative - Problems, transitions, paradigm shifts
  5. Light panel = insights - Actionable numbered takeaways (3-4 items)
  6. Bottom formula - Distill into one equation-style summary

Output Format

By default, generate both HTML and PNG:

  1. HTML file: Self-contained with embedded CSS, Google Fonts, and html2canvas for browser export
  2. PNG file: High-quality render at 1.5× scale (1800px wide), optimized for social media

Output location: data/cards/YYYY-MM-DD-{topic-slug}/

Language Handling

CRITICAL: The card content language should match the source KB content language:

  • If the KB chapter is in Chinese, generate Chinese card content
  • If the KB chapter is in English, generate English card content
  • Always include bilingual titles (English + Chinese) regardless of content language
  • Technical terms and framework acronyms remain in their original language

Dependencies

The skill requires:

  • Python 3.8+
  • Playwright (for PNG rendering): pip install playwright && playwright install chromium

Dependencies are checked and installed automatically on first run.

Resources

  • visual-card/_scripts/generate_card.py: Main orchestrator for Agent-driven workflow
  • visual-card/_scripts/prepare_card_context.py: Prepares context (source + template spec) for Agent
  • visual-card/_scripts/generate_card_from_synthesis.py: Generates HTML/PNG from Agent synthesis
  • visual-card/_scripts/html2png.py: Playwright-based HTML to PNG renderer
  • visual-card/_scripts/generate_card_legacy.py: Legacy hardcoded extraction (fallback)
  • visual-card/_templates/card_template.html: Canonical HTML/CSS template
  • visual-card/_templates/card_template_spec.md: Natural language specification for Agent (describes 7 blocks, quality criteria, examples)
  • _assets/: Additional assets (if needed)

Example Usage

bash
# Generate a card for a specific chapter
python visual-card/_scripts/generate_card.py \
  --chapter "data/books/markets-and-trading/market-structure-and-signals"

# Generate with custom color scheme
python visual-card/_scripts/generate_card.py \
  --chapter "data/books/ai-and-research/model-training-and-optimization" \
  --primary-color "#2d5a8c" \
  --accent-color "#d4af37"

# Generate HTML only (skip PNG)
python visual-card/_scripts/generate_card.py \
  --chapter "data/books/community-qa-and-discussion/platform-discussions" \
  --html-only

Integration with Other Skills

This skill works best after:

  • Synthesis: Content is already organized in the knowledge base
  • Display: User has browsed the KB and identified interesting chapters

It can be chained with:

  • Display: Generate cards for all chapters in a topic
  • Feed: Create visual cards from feed items

Notes

  • Cards are 1200px wide by default (poster format)
  • PNG export uses device-scale-factor for high-DPI rendering
  • The floating action button (FAB) in HTML allows browser-based export at multiple resolutions
  • All cards include a copyright attribution to the original visual-note-card-skills project

Bundled files

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

Frequently asked questions

What does the Visual Card AI skill do?

Generate professional visual note cards (视觉笔记卡片/信息图) from knowledge base content as single-page HTML infographics with PNG export. Use when users want to create visual summaries, knowledge cards, infographics, or poster-style visualizations of topics from the knowledge base.

Why use Visual Card on TypingMind?

Because you install it once and use it with any model. Visual Card 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 Visual Card in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/NatsuFox/Tapestry/tree/main/skills/tapestry/visual-card. 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 Visual Card?

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 Visual Card?

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

Is the Visual Card AI skill free?

Yes. It is published on GitHub by NatsuFox under the MIT 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 👇