메뉴
USE WHEN: visualizing algorithms, data structures, architecture, control flow with ASCII art, or when terminal-friendly diagrams are needed. DO NOT USE WHEN: Mermaid diagrams are better suited, rich graphics are available, or simple text explanation suffices.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
PROACTIVE skill - Claude invokes automatically when user messages exhibit anti-patterns. Detects recursive nesting, scope creep, buried asks, assumed context, stream dumps, imprecise descriptions. Disable with "coach off" or "raw mode".
USE WHEN: user wants to publish, port, or share a skill to a marketplace repo. DO NOT USE WHEN: creating new skills, installing skills, or general questions.
Explains code, algorithms, system design using ASCII diagrams. Trigger phrases - "explain visually", "I don't get it", "show me", "ascii diagram", "help me understand". Produces diagram-first explanations ending with TL;DR tables.
USE WHEN: user requests generative art, algorithmic art, procedural visuals, flow fields, particle systems, creative coding, or says "create art", "generative", "p5.js". DO NOT USE WHEN: static images, traditional graphics, or non-generative visual work is requested. Creates original algorithmic art—never copies existing artists' work.
USE WHEN: analyzing existing architectures, evaluating architectural decisions, identifying technical debt, planning refactoring, assessing whether patterns are justified, onboarding to complex codebases, reviewing PRs with architectural changes. DO NOT USE WHEN: simple code questions, bug fixes, feature implementation, or tasks not requiring architectural analysis. For complex architectural analysis, trigger deep thinking with "think harder" or "ultrathink" to enable thorough first-principles reasoning.
USE WHEN: needing real code examples from GitHub, finding API usage patterns, looking up framework setup, verifying library implementations, eliminating hallucinations with working code. DO NOT USE WHEN: working on proprietary code, questions about the current codebase, or when local context is sufficient. Requires Exa API key configured in environment.
| name | ascii-art-explainer |
| description | USE WHEN: visualizing algorithms, data structures, architecture, control flow with ASCII art, or when terminal-friendly diagrams are needed. DO NOT USE WHEN: Mermaid diagrams are better suited, rich graphics are available, or simple text explanation suffices. |
| license | Complete terms in LICENSE.txt |
This skill guides creation of performative ASCII art that transforms abstract code concepts into memorable visual explanations. Create art that makes the invisible visible—data flowing, structures forming, algorithms dancing.
The user provides a concept to visualize: an algorithm, data structure, system architecture, code flow, or abstract programming idea. They may include context about complexity level, specific aspects to emphasize, or the "aha moment" they want to capture.
Before drawing, understand the concept and commit to a BOLD visual strategy:
CRITICAL: ASCII art explains through COMPOSITION, not just labeling. If your diagram is just boxes with text labels, you've failed. The spatial arrangement itself must teach. Show WHY something works, not just WHAT it is. Every character placement is a design decision.
Focus on:
┌─┐│└┘├┤┬┴┼ for clean structures. Double-line ╔═╗║╚╝ for emphasis. Rounded ╭─╮│╰╯ for softer elements. Mix styles to create visual hierarchy.→←↑↓↗↘↙↖ for direction. ═══▶ for emphasis. ···> for dashed/optional. >>>>>> for streams. Show DATA MOVING, not static connections.[Step 1], [Step 2]. Time flows left-to-right or top-to-bottom.░▒▓█ for fill levels, heat maps, memory usage. Empty vs full. Active vs dormant. Use density to show intensity.★ ◆ ● ○ ◇ ▲ ▼ ⟦⟧ ⟨⟩ « » for emphasis, markers, boundaries. ╱╲ for diagonals. Make it MEMORABLE.NEVER create flat boxes-and-labels diagrams that could be bullet points, use only basic ASCII (+--+|) when Unicode box-drawing exists, show static structure without flow or transformation, produce cluttered noise without clear focal points, make everything the same visual weight, or forget to show the INSIGHT that makes the concept click.
Adapt complexity to concept scope. Simple concepts get elegant minimal diagrams. Complex systems get layered, annotated compositions. Algorithms get multi-frame animations. The art should match the teaching moment.
IMPORTANT: ASCII art is PERFORMATIVE—it should feel like watching the code come alive. Think theater, not textbook. The best diagrams make viewers say "NOW I get it!" after years of reading prose explanations. That's the bar.
Remember: Claude can create extraordinary visual compositions with just text characters. Don't settle for boring rectangles—create art that explains, delights, and illuminates.