ascii-visualizer
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.
What this skill does
# ASCII Visualizer Skill
**π― SKILL ACTIVATION PROTOCOL**
To use this skill, announce at the start of the response:
```
π― Using ascii-visualizer skill for visual diagram generation
```
## Purpose
Create clear ASCII visualizations for ANY concept. **USER EXPLICITLY LOVES ASCII ART** - use liberally!
## When to Use
- Architecture diagrams or system design
- Implementation plans and workflows
- Before/after comparisons or options
- Progress indicators and metrics
- File trees and hierarchies
## Pattern Library
### Box Diagrams
```
βββββββββββββββββββ
β Component A β
β (Description) β
ββββββββββ¬βββββββββ
β
βΌ
βββββββββββββββββββ
β Component B β
βββββββββββββββββββ
```
### File Trees
```
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)
```
### Flow Charts
```
User Answer
β
βΌ
tRPC Endpoint
β
βΌ
Claude AI β Evaluation
β
βΌ
Results Store β UI
```
### Comparison Tables
```
ββββββββββββββββββββββββββββββββββββββββββββ
β 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% β‘β
ββββββββββββββββββββββββββββββββββββββββββββ
```
### Progress Bars
```
DevPrep AI - Results Analytics
βββββββββββββββββββββββββββββββ
Tab 1: Overview ββββββββββββββββ 100% β
Tab 2: Questions ββββββββββββββββ 100% β
Tab 3: Hint Analyticsββββββββββββββββ 100% β
Tab 4: Insights ββββββββββββββββ 100% β
βββββββββββββββββββββββββββββββ
```
## Box-Drawing Characters
```
βββ¬ββ βββ¦ββ Basic boxes
βββΌββ€ β ββ¬ββ£ Heavy boxes
βββ΄ββ βββ©ββ Rounded corners
β β Vertical lines
β β Horizontal lines
β² βΌ Arrows
βΊ β Arrows horizontal
β
β Status indicators
π§ π Progress states
β π₯ Priorities
```
## Best Practices
1. **Clarity First** - ASCII should clarify, not confuse
2. **Consistent Styling** - Use box-drawing characters consistently
3. **Compact** - Fit within 80-100 columns when possible
4. **Status Indicators** - Use emojis for visual interest: β
π§ π β³ β β
5. **Always Visualize** - User loves seeing plans as ASCII art
## Usage Guidelines
Create ASCII visualizations for:
- "How does X work?"
- "Show me the plan"
- "What's the architecture?"
- "Compare A vs B"
- ANY explanation that benefits from visuals
## Example
See `examples/devprep-architecture.md` for a comprehensive example showing:
- DevPrep AI's 7-folder architecture
- Tab 4 Learning Insights implementation workflow
- Agent delegation with parallel execution
- Data flow visualization (store β hooks β components)
- Recent accomplishments and metrics
- Skills ecosystem integration
This example demonstrates how to create layered visualizations that progress from high-level architecture to detailed implementation flows.
Related in Writing & Docs
jax-development
IncludedUse this skill when the user is writing, debugging, profiling, refactoring, reviewing, benchmarking, parallelising, exporting, or explaining JAX code, or when they mention JAX, jax.numpy, jit, grad, value_and_grad, vmap, scan, lax, random keys, pytrees, jax.Array, sharding, Mesh, PartitionSpec, NamedSharding, pmap, shard_map, Pallas, XLA, StableHLO, checkify, profiler, or the JAX repo. It helps turn NumPy or PyTorch-style code into pure functional JAX, fix tracer/control-flow/shape/PRNG bugs, remove recompiles and host-device syncs, choose transforms and sharding strategies, inspect jaxpr/lowering/IR, and benchmark compiled code correctly.
nature-article-writer
IncludedDrafts, rewrites, diagnostically critiques, and style-calibrates primary research manuscripts for Nature and Nature Portfolio journals. Use when the user wants a Nature-style title, summary paragraph or abstract, introduction, results, discussion, methods, figure legends, presubmission enquiry, cover letter, reviewer response, or when a scientific draft sounds generic, jargon-heavy, structurally weak, or AI-ish and needs precise, broad-reader-friendly prose without inventing data, analyses, or references. Best for primary research articles and letters rather than reviews or press releases unless explicitly adapting one.
deckrd
IncludedDocument-driven framework that derives requirements, specifications, implementation plans, and executable tasks from goals through structured AI dialogue. Use when user says "write requirements", "create spec", "plan implementation", "derive tasks", "structure this feature", "break down into tasks", or "document this module". Also use for reverse engineering existing code into docs (/deckrd rev). Do NOT use for direct code writing β use /deckrd-coder after tasks are generated. Do NOT use when the user only wants to run or fix existing code without planning.
clinical-decision-support
IncludedGenerate professional clinical decision support (CDS) documents for pharmaceutical and clinical research settings, including patient cohort analyses (biomarker-stratified with outcomes) and treatment recommendation reports (evidence-based guidelines with decision algorithms). Supports GRADE evidence grading, statistical analysis (hazard ratios, survival curves, waterfall plots), biomarker integration, and regulatory compliance. Outputs publication-ready LaTeX/PDF format optimized for drug development, clinical research, and evidence synthesis.
handling-sf-data
IncludedSalesforce data operations with 130-point scoring. Use this skill to create, update, delete, bulk import/export, generate test data, and clean up org records using sf CLI and anonymous Apex. TRIGGER when: user creates test data, performs bulk import/export, uses sf data CLI commands, needs data factory patterns for Apex tests, or needs to seed/clean records in a Salesforce org. DO NOT TRIGGER when: SOQL query writing only (use querying-soql), Apex test execution (use running-apex-tests), or metadata deployment (use deploying-metadata).
accelint-ac-to-playwright
IncludedConvert and validate acceptance criteria for Playwright test automation. Use when user asks to (1) review/evaluate/check if AC are ready for automation, (2) assess if AC can be converted as-is, (3) validate AC quality for Playwright, (4) turn AC into tests, (5) generate tests from acceptance criteria, (6) convert .md bullets or .feature Gherkin files to Playwright specs, (7) create test automation from requirements. Handles both bullet-style markdown and Gherkin syntax with JSON test plan generation and validation.