← ClaudeAtlas

visualizelisted

Create visualizations and interactive tools directly in conversation. Proactively use to show how something works; explore 'what happens when', 'what changes', or 'help me understand'; compare or inspect; create simulations, maps, charts, graphs, and mockups. Use standard tools for static scientific figures.
hyperdargo/ClaudeSkillAndPluginsWithMasterPrompt · ★ 0 · AI & Automation · score 62
Install: claude install-skill hyperdargo/ClaudeSkillAndPluginsWithMasterPrompt
# Visualize `<skill-dir>` is this SKILL.md’s directory; resolve relative file paths from it. - A request for a new standalone file, website, app page, component, or other project change is not an in-conversation visualization request, even when the deliverable contains charts or interactive content. - A request to preview, explain, or explore a proposed interface in the conversation is an in-conversation visualization request. - Create a visual only when the user needs to see or explore it in the conversation and it materially improves the explanation. Do not create an inline visual merely because the request involves data, charts, or an interactive page. - Use a normal Markdown table when the user asks for a table; return it directly and do not create a visualization file. - Use Mermaid when labeled nodes and edges fully explain a static structure; return a normal fenced Mermaid block and no visualization file. Use HTML for dynamics, spatial motion, adjustable inputs, and other visuals. - Work silently unless blocked or the user explicitly asks for progress. Never send commentary or progress updates while reading this skill or writing or updating the file; the final response must be your first user-facing message. - In user-facing prose, describe only what the visual helps the user see or decide. Keep it concise and do not repeat information already clear from the visual. Never announce this skill, a visualization surface, widgets, HTML, SVG, scripts, local files, inline d