skills/ariegoldkin/ascii-visualizer/SKILL.md
Creates beautiful ASCII art visualizations for plans, architectures, workflows, and data. This skill should be used when explaining system architecture, creating implementation plans, showing workflows, visualizing comparisons, or documenting file structures. NOT for code syntax highlighting or markdown tables. User explicitly loves ASCII art - use liberally for visual communication.
npx skillsauth add aiskillstore/marketplace ascii-visualizerInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
🎯 SKILL ACTIVATION PROTOCOL To use this skill, announce at the start of the response:
🎯 Using ascii-visualizer skill for visual diagram generation
Create clear ASCII visualizations for ANY concept. USER EXPLICITLY LOVES ASCII ART - use liberally!
┌─────────────────┐
│ Component A │
│ (Description) │
└────────┬────────┘
│
▼
┌─────────────────┐
│ Component B │
└─────────────────┘
test-orchestration-demo/
├── .claude/
│ ├── skills/ ⭐ This skill!
│ └── instructions/
├── Docs/
│ └── results-implementation/
└── frontend/ ✨ 7-folder architecture
├── app/ (Next.js routes)
├── modules/ (Feature modules)
├── shared/ (UI components)
├── lib/ (Integrations)
├── store/ (Global state)
├── styles/ (Design system)
└── types/ (TypeScript)
User Answer
│
▼
tRPC Endpoint
│
▼
Claude AI → Evaluation
│
▼
Results Store → UI
┌──────────────────────────────────────────┐
│ BEFORE (17 folders) AFTER (7 folders)│
├──────────────────────────────────────────┤
│ Complexity: High Simple -60% ⬇️│
│ Type Safety: 70% 100% +30% ✅│
│ Code Lines: 3,455 2,500 -955 🧹│
│ Build Time: 8.5s 7.2s -15% ⚡│
└──────────────────────────────────────────┘
DevPrep AI - Results Analytics
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Tab 1: Overview ████████████████ 100% ✅
Tab 2: Questions ████████████████ 100% ✅
Tab 3: Hint Analytics████████████████ 100% ✅
Tab 4: Insights ████████████████ 100% ✅
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
┌─┬─┐ ╔═╦═╗ Basic boxes
├─┼─┤ ╠═╬═╣ Heavy boxes
└─┴─┘ ╚═╩═╝ Rounded corners
│ ║ Vertical lines
─ ═ Horizontal lines
▲ ▼ Arrows
► ◄ Arrows horizontal
✅ ❌ Status indicators
🚧 📋 Progress states
⭐ 🔥 Priorities
Create ASCII visualizations for:
See examples/devprep-architecture.md for a comprehensive example showing:
This example demonstrates how to create layered visualizations that progress from high-level architecture to detailed implementation flows.
development
Apple Human Interface Guidelines for content display components. Use this skill when the user asks about charts component, collection view, image view, web view, color well, image well, activity view, lockup, data visualization, content display, displaying images, rendering web content, color pickers, or presenting collections of items in Apple apps. Also use when the user says how should I display charts, what's the best way to show images, should I use a web view, how do I build a grid of items, what component shows media, or how do I present a share sheet. Cross-references: hig-foundations for color/typography/accessibility, hig-patterns for data visualization patterns, hig-components-layout for structural containers, hig-platforms for platform-specific component behavior.
tools
Automate HelpDesk tasks via Rube MCP (Composio): list tickets, manage views, use canned responses, and configure custom fields. Always search tools first for current schemas.
testing
Expert Haskell engineer specializing in advanced type systems, pure functional design, and high-reliability software. Use PROACTIVELY for type-level programming, concurrency, and architecture guidance.
tools
GraphQL gives clients exactly the data they need - no more, no less. One endpoint, typed schema, introspection. But the flexibility that makes it powerful also makes it dangerous. Without proper controls, clients can craft queries that bring down your server. This skill covers schema design, resolvers, DataLoader for N+1 prevention, federation for microservices, and client integration with Apollo/urql. Key insight: GraphQL is a contract. The schema is the API documentation. Design it carefully.