Loading...
Loading...
Found 8 Skills
Create, edit, review, or export editable draw.io diagrams. Use when the user needs .drawio architecture, flow, sequence, network, or other technical diagrams; not data plots or artistic images.
Create a beautiful HTML explanation of a repo, spec, PR, architecture, or concept so a smart beginner can understand and retell it.
Automatically discover diagram and visualization skills when working with flowcharts, sequence diagrams, architecture diagrams, ER diagrams, Gantt charts, mindmaps, or any visual documentation using Mermaid.js. Activates for documentation and visualization tasks.
Generate self-contained HTML pages and slide decks (diagrams, comparison tables, architecture overviews, diff reviews, visual recaps) by emitting semantic component JSON. Use whenever a visual artifact communicates better than terminal prose — proactively trigger on 4+ row tables, ASCII flowcharts, multi-stage pipelines, or explicit "make a diagram / slides / recap" requests.
Design and review visual content for developer documentation, including screenshots, architecture diagrams, boxes-and-arrows diagrams, flowcharts, swimlanes, video decisions, accessibility, performance, annotations, and visual maintenance. Use when creating or auditing diagrams, screenshots, visual explanations, or media in technical docs.
プロダクトデモ動画を自動生成。百聞は一見にしかず、を体現。Use when user mentions '/generate-video', video generation, product demos, or visual documentation. Do NOT load for: embedding video players, live demos, video playback features. Requires Remotion setup.
Aggressively produce self-contained HTML artifacts instead of Markdown for substantial agent outputs. Use when the user asks for a doc, plan, spec, report, review, PR description, explainer, summary, comparison, research artifact, dashboard, diagram, flowchart, timeline, deck, slides, prototype, design reference, component sheet, editor, prompt tuner, config editor, triage board, or any human-facing deliverable that benefits from layout, visual hierarchy, navigation, diagrams, interactivity, or sharing. Default to this skill even when the user does not explicitly request HTML; stay in plain chat only for very short replies, code-only snippets, terminal commands, or explicit non-HTML requests.
Explains concepts, PRs, and designs for a specific reader as concise crash-course material without unnecessary verbosity, and verifies the diagrams and claims with tools. Build the reader persona—including what they already know, what they do not know, and how they read—from questions and public information, and write only the resulting delta. Create diagrams with vlmkit-anim against a fact sheet, re-run and cross-check code and output quoted in the body, and pass the HTML through vlmkit's validation gates. Use when the user says “explain this to me / to <person>”, “crash-course material”, “explanatory documentation”, “I want to understand this PR”, “explain it so I understand”, “I can't keep up with what the agent wrote”, or when a reviewer asks what a change does and the answer needs more than a paragraph. Also use it when the user wrote an explanation themselves and lost confidence in it.