Design polished, professional explanatory graphics as SVG or single-file HTML. Use when the user asks for an infographic, 資訊圖表, 懶人包, 圖解, a one-pager, a visual summary, or a timeline/comparison/process ("how it works") graphic — even without the word "infographic" — and to review an existing one ("幫我看這張圖表哪裡 可以改"). Use for a learning recap when a teaching dialogue ends ("學習總結成一張圖", "visual recap of what you taught me"); that route needs no further prompting. Also use when another skill needs a figure designed for a document it is producing. Do NOT invoke for a single standalone chart embedded in analysis output, for dashboards / BI tooling, for slide decks (use a pptx workflow), for explaining a term in plain language (use plain-speak), or for data-dense charts where the numbers are themselves the subject or precise scales matter (annual-results decks, survey findings, statistical graphics) — hand those to a data-visualization workflow. An explicit ask for an infographic / 資訊圖表 / 懶人包 / one-pager always qualifies even when the underlying data is precise; the data-density exclusion applies only when the user names a chart, plot, or dashboard instead. Quantities that serve as evidence inside an explanation (a funnel's drop-off, a cache hit-rate) stay in scope.
Install with
Claude CodeCodexCursorGitHub CopilotGemini CLI
Supported by the Atlas install prompt. Skill-specific requirements vary.
Skill stats
Skills1CategoryContent & writingStars0
About this skill
Design polished, professional explanatory graphics as SVG or single-file HTML. Use when the user asks for an infographic, 資訊圖表, 懶人包, 圖解, a one-pager, a visual summary, or a timeline/comparison/process ("how it works") graphic — even without the word "infographic" — and to review an existing one ("幫我看這張圖表哪裡 可以改"). Use for a learning recap when a teaching dialogue ends ("學習總結成一張圖", "visual recap of what you taught me"); that route needs no further prompting. Also use when another skill needs a figure designed for a document it is producing. Do NOT invoke for a single standalone chart embedded in analysis output, for dashboards / BI tooling, for slide decks (use a pptx workflow), for explaining a term in plain language (use plain-speak), or for data-dense charts where the numbers are themselves the subject or precise scales matter (annual-results decks, survey findings, statistical graphics) — hand those to a data-visualization workflow. An explicit ask for an infographic / 資訊圖表 / 懶人包 / one-pager always qualifies even when the underlying data is precise; the data-density exclusion applies only when the user names a chart, plot, or dashboard instead. Quantities that serve as evidence inside an explanation (a funnel's drop-off, a cache hit-rate) stay in scope.
Quick start
Copy the install prompt. Use the green button above this README.
Send it to your agent. Paste it into your coding agent’s chat and send.
Review the setup. Your agent checks the skill’s instructions, requirements, and installation scope.
Design polished, professional explanatory graphics as SVG or single-file HTML. Use when the user asks for an infographic, 資訊圖表, 懶人包, 圖解, a one-pager, a visual summary, or a timeline/comparison/process ("how it works") graphic — even without the word "infographic" — and to review an existing one ("幫我看這張圖表哪裡 可以改"). Use for a learning recap when a teaching dialogue ends ("學習總結成一張圖", "visual recap of what you taught me"); that route needs no further prompting. Also use when another skill needs a figure designed for a document it is producing. Do NOT invoke for a single standalone chart embedded in analysis output, for dashboards / BI tooling, for slide decks (use a pptx workflow), for explaining a term in plain language (use plain-speak), or for data-dense charts where the numbers are themselves the subject or precise scales matter (annual-results decks, survey findings, statistical graphics) — hand those to a data-visualization workflow. An explicit ask for an infographic / 資訊圖表 / 懶人包 / one-pager always qualifies even when the underlying data is precise; the data-density exclusion applies only when the user names a chart, plot, or dashboard instead. Quantities that serve as evidence inside an explanation (a funnel's drop-off, a cache hit-rate) stay in scope.
About this listing
Category
Content & writing
Reported license
MIT
Listing language (estimated)
English
Review status
Not individually reviewed
Agent compatibility
Atlas installation supports Claude Code, Codex, and Cursor. Skill-specific dependencies and features are checked during setup.
Claude Code
Codex
Cursor
GitHub Copilot
Gemini CLI