art

multicam's avatarfrom multicam

Complete visual content system for PAI.Tron-meets-Excalidraw aesthetic - dark backgrounds, neon accents, hand-drawn sketch style.

⭐1stars🔀0forks📁View on GitHub🕐Updated Jan 10, 2026

When & Why to Use This Skill

This Claude skill provides a comprehensive visual content system featuring a unique 'Tron-meets-Excalidraw' aesthetic. It enables users to generate high-quality, hand-drawn style illustrations, technical diagrams, and social media assets characterized by dark backgrounds and neon accents, ensuring a consistent and modern brand identity across all visual communications.

Use Cases

  • Editorial Design: Creating professional blog headers and editorial illustrations with a tech-focused, digital-warmth aesthetic.
  • Technical Documentation: Generating architecture diagrams, Mermaid flowcharts, and sequence diagrams in a hand-drawn sketch style for better readability.
  • Data Visualization: Transforming complex information into structured visuals like 2x2 matrices, timelines, taxonomies, and comparison grids.
  • Social Media & Marketing: Producing high-impact visual assets such as quote cards, stat cards with big numbers, and multi-panel comics.
  • Instructional Content: Designing annotated screenshots and step-by-step recipe cards to simplify complex processes for users.
nameart
contextfork
description|
- USE WHEN user wants blog header or editorial illustrationworkflows/workflow.md
- USE WHEN user wants visualization or is unsure which formatworkflows/visualize.md
- USE WHEN user wants mermaid flowchart or sequence diagramworkflows/mermaid.md
- USE WHEN user wants technical or architecture diagramworkflows/technical-diagrams.md
- USE WHEN user wants taxonomy or classification gridworkflows/taxonomies.md
- USE WHEN user wants timeline or chronological progressionworkflows/timelines.md
- USE WHEN user wants framework or 2x2 matrixworkflows/frameworks.md
- USE WHEN user wants comparison or X vs Yworkflows/comparisons.md
- USE WHEN user wants annotated screenshotworkflows/annotated-screenshots.md
- USE WHEN user wants recipe card or step-by-stepworkflows/recipe-cards.md
- USE WHEN user wants aphorism or quote cardworkflows/aphorisms.md
- USE WHEN user wants conceptual map or territoryworkflows/maps.md
- USE WHEN user wants stat card or big number visualworkflows/stats.md
- USE WHEN user wants comic or sequential panelsworkflows/comics.md

Art Skill

Complete visual content system using the PAI Visual Aesthetic.


Core Aesthetic

Tron-meets-Excalidraw - Digital warmth combining:

  • Hand-drawn Excalidraw-style sketch lines (NOT clean vectors)
  • Dark slate backgrounds for modern contrast
  • Neon orange (warmth) + cyan (tech) accents
  • Subtle glows on key elements

Full aesthetic documentation: ${PAI_DIR}/skills/CORE/aesthetic.md

This is the SINGLE SOURCE OF TRUTH for all visual styling.


Workflow Routing

Content Type Workflow
Blog headers / Editorial workflows/workflow.md
Adaptive orchestrator workflows/visualize.md
Flowcharts / Sequences workflows/mermaid.md
Architecture diagrams workflows/technical-diagrams.md
Classification grids workflows/taxonomies.md
Chronological workflows/timelines.md
2x2 matrices workflows/frameworks.md
X vs Y workflows/comparisons.md
Screenshot markup workflows/annotated-screenshots.md
Step-by-step workflows/recipe-cards.md
Quote cards workflows/aphorisms.md
Idea territories workflows/maps.md
Big numbers workflows/stats.md
Sequential panels workflows/comics.md

Image Generation

Default model: nano-banana-pro (Gemini 3 Pro)

bun run ${PAI_DIR}/skills/art/tools/generate-ulart-image.ts \
  --model nano-banana-pro \
  --prompt "[PROMPT]" \
  --size 2K \
  --aspect-ratio 1:1 \
  --output /path/to/output.png

Alternative Models

Model When to Use
flux Maximum quality
gpt-image-1 Different interpretation

API keys in: ${PAI_DIR}/.env

  • REPLICATE_API_TOKEN - Flux and Nano Banana
  • OPENAI_API_KEY - GPT-image-1
  • GOOGLE_API_KEY - Nano Banana Pro
  • REMOVEBG_API_KEY - Background removal

Quick Decision Tree

What does user need?

├─ Unsure which approach? → VISUALIZE (analyzes & orchestrates)
├─ Flowchart/sequence/state diagram? → MERMAID
├─ Abstract metaphor for article? → Editorial (workflow.md)
├─ System/architecture with labels? → Technical Diagram
├─ Categories in grid? → Taxonomy
├─ Change over time? → Timeline
├─ 2x2 matrix or mental model? → Framework
├─ Side-by-side contrast? → Comparison
├─ Markup existing screenshot? → Annotated Screenshot
├─ Step-by-step process? → Recipe Card
├─ Quote as social visual? → Aphorism
├─ Idea territories as map? → Conceptual Map
├─ Single striking number? → Stat Card
└─ Multi-panel story? → Comic

For complete visual styling rules, ALWAYS read: ${PAI_DIR}/skills/CORE/aesthetic.md