ascii-canvas
Compose high-quality ASCII/Unicode text-based visual artifacts. "Canva for ASCII."
When to fire
Fire on:
- Explicit format requests: "make a flowchart", "draw the architecture", "ASCII slideshow", "infographic on X", "comparison table", "timeline of", "cheat sheet for", "make a comic", "comic strip", "comic-style", "as a skit", "as a scenario", "with characters", "dialogue between X and Y", "anthropomorphize X", "make flashcards", "flashcard deck", "vocab cards", "study cards", "Anki-style cards", "drill me on X", "quiz me on X", "test me on X", "help me memorize X"
- Visual framing: "visualize X", "show me how X works", "diagram this", "illustrate"
- Structured breakdown of non-trivial topics: "break down X", "walk me through X step by step", "explain X as a playbook", "learning ladder for X", "content map for X"
Do NOT fire on:
- Simple factual questions ("what year did X happen?")
- Short answers (less than ~3 steps or one paragraph)
- Conversational replies, opinions, hot takes
- When trigger is weak AND structure won't improve clarity over prose
Routing flow
1. DETECT TRIGGER
├── Explicit format keyword? → load that format file
├── Visual framing? → infer format from topic shape (matrix below)
├── Structured breakdown of
│ non-trivial topic? → infer multi-panel format
└── None / weak / won't help → DO NOT activate; respond as plain prose
2. CHOOSE FORMAT
If user named one → use it.
Otherwise apply the routing matrix:
branching + decisions → decision-tree
branching + mixed steps → flowchart
linear process → step-by-step-guide
repeatable workflow / SOP → playbook
skill progression → learning-ladder
one idea → many outputs → content-map
layers / dependencies → concept-stack
side-by-side options → comparison-table
actors + messages → sequence-diagram
system components → architecture-diagram
events over time → timeline
central idea + radial → mind-map
dense reference → cheat-sheet
status / metrics → dashboard
narrative explainer → slideshow
high-signal summary → infographic
characters + dialogue + lesson → comic
anthropomorphized concept → comic
recall / memorization drill → flashcards
quiz / test self → flashcards
Tie-breakers:
- Multiple formats apply → choose simplest that preserves clarity
- Two formats equally fit → choose the simpler one
- Comic vs slideshow ambiguous → slideshow (simpler)
- Comic vs sequence-diagram → comic for educational, sequence-diagram for technical
- Flashcards vs cheat-sheet → flashcards for active recall, cheat-sheet for passive reference
- Flashcards vs comparison-table → comparison-table for side-by-side, flashcards for sequential Q/A
- Do NOT combine formats in v1 unless explicitly requested
3. LOAD FORMAT FILE (MANDATORY)
→ Read formats/<format>.md
No ad-hoc layouts. Templates only.
4. DETERMINE CHARACTER SET
Unicode by default. ASCII fallback if user requested OR destination demands.
See composition-rules/box-drawing.md.
5. APPLY CANONICAL ARC (multi-panel formats only)
See composition-rules/narrative-arcs.md.
Reduce panel count if content doesn't justify the full arc.
6. GENERATE OUTPUT
7. DETERMINE SAVE BEHAVIOR
- Single-artifact + not multi-section + not "reusable asset" → chat only
- Multi-panel / multi-section / clearly reusable → auto-save
- User signaled iteration ("try again", "draft") → chat only
- User said "save this" → force save
- User said "don't save" / "chat only" → force chat
8. RUN QA
- Strict mode for saved/multi-panel/reusable
- Light mode otherwise
- Strict QA must pass BEFORE chat render AND BEFORE file write
- If fails twice → invoke simplify rule
- If simplify still fails → invoke format fallback (see qa-checklist.md)
9. RENDER + (optional) SAVE
- Chat preview: ≤80 lines → render full. >80 lines → render first 1-2 sections + "saved to <path>"
- File write: only AFTER strict QA passes. Path: ~/Ascii-diagrams/YYYY-MM/YYYY-MM-DD-<slug>.md
- Post-save line: exactly two lines, no fluff:
Saved to:
~/Ascii-diagrams/YYYY-MM/YYYY-MM-DD-<slug>.md
Output behavior
Save path & naming
- Path:
~/Ascii-diagrams/YYYY-MM/YYYY-MM-DD-<topic-slug>.md
- Slug: lowercase, hyphen-separated, 6–8 words max, derived from user intent
- Fallback slug if user intent is unclear:
<format>-<short-topic> (e.g., playbook-cold-outbound)
File template
# Title
Short description (1–2 lines)
---
## Section 1
<ASCII inside a code block>
---
## Section 2
<ASCII>
Chat preview rules
Anti-pattern
Do NOT default to saving everything "just in case." Throwaway sketches do not deserve files. Noise > occasional regret.
Composition rules (read on demand)
composition-rules/box-drawing.md — Unicode set, ASCII fallback, consistency rules
composition-rules/width-budgets.md — per-format max width + overflow handling
composition-rules/narrative-arcs.md — 8 arcs + universal panel rules
composition-rules/qa-checklist.md — light/strict QA + simplify + fallback + no-partial-save
Examples (read on demand)
examples/<format>-example.md — one richer reference per format. Read when the format file's inline example isn't enough.
v1 boundaries (explicitly out of scope)
mode: quick | publish flag → v2
- External tools (graph-easy, ditaa, figlet) → manual workflow only, not integrated
- Color / ANSI escapes → not used
- Image export → not in scope
- Format combination (e.g. slideshow with embedded flowchart) → only when explicitly requested
Hard rules (do not violate)
- Always load the relevant format file before rendering output. No ad-hoc layouts.
- Strict QA must pass before any file write. No partial saves. No QA-failed saves.
- Never exceed format max width. Shrink content; never widen past budget.
- Default to saving NOTHING. Save only what matches the save criteria.
- Format choice: simplest that preserves clarity. No combining formats in v1 unless asked.
1---2name: ascii-canvas3description: Compose ASCII/Unicode diagrams, slideshows, infographics, playbooks, comic strips, flashcards, and other text-based visual artifacts from a topic, idea, or set of facts. Use when the user explicitly requests a diagram/visual/format (flowchart, slideshow, cheat sheet, infographic, timeline, comic strip, flashcards, etc.) OR asks for a structured breakdown / step-by-step explanation of a non-trivial topic. Do NOT trigger for simple factual questions, short answers (less than ~3 steps or one paragraph), or conversational/opinion queries.4metadata:5 source: https://skillmd.com/skills/noodlebindev/ascii-canvas6---78# ascii-canvas910Compose high-quality ASCII/Unicode text-based visual artifacts. "Canva for ASCII."1112## When to fire1314**Fire on:**15- Explicit format requests: "make a flowchart", "draw the architecture", "ASCII slideshow", "infographic on X", "comparison table", "timeline of", "cheat sheet for", "make a comic", "comic strip", "comic-style", "as a skit", "as a scenario", "with characters", "dialogue between X and Y", "anthropomorphize X", "make flashcards", "flashcard deck", "vocab cards", "study cards", "Anki-style cards", "drill me on X", "quiz me on X", "test me on X", "help me memorize X"16- Visual framing: "visualize X", "show me how X works", "diagram this", "illustrate"17- Structured breakdown of non-trivial topics: "break down X", "walk me through X step by step", "explain X as a playbook", "learning ladder for X", "content map for X"1819**Do NOT fire on:**20- Simple factual questions ("what year did X happen?")21- Short answers (less than ~3 steps or one paragraph)22- Conversational replies, opinions, hot takes23- When trigger is weak AND structure won't improve clarity over prose2425## Routing flow2627```281. DETECT TRIGGER29 ├── Explicit format keyword? → load that format file30 ├── Visual framing? → infer format from topic shape (matrix below)31 ├── Structured breakdown of32 │ non-trivial topic? → infer multi-panel format33 └── None / weak / won't help → DO NOT activate; respond as plain prose34352. CHOOSE FORMAT36 If user named one → use it.37 Otherwise apply the routing matrix:3839 branching + decisions → decision-tree40 branching + mixed steps → flowchart41 linear process → step-by-step-guide42 repeatable workflow / SOP → playbook43 skill progression → learning-ladder44 one idea → many outputs → content-map45 layers / dependencies → concept-stack46 side-by-side options → comparison-table47 actors + messages → sequence-diagram48 system components → architecture-diagram49 events over time → timeline50 central idea + radial → mind-map51 dense reference → cheat-sheet52 status / metrics → dashboard53 narrative explainer → slideshow54 high-signal summary → infographic55 characters + dialogue + lesson → comic56 anthropomorphized concept → comic57 recall / memorization drill → flashcards58 quiz / test self → flashcards5960 Tie-breakers:61 - Multiple formats apply → choose simplest that preserves clarity62 - Two formats equally fit → choose the simpler one63 - Comic vs slideshow ambiguous → slideshow (simpler)64 - Comic vs sequence-diagram → comic for educational, sequence-diagram for technical65 - Flashcards vs cheat-sheet → flashcards for active recall, cheat-sheet for passive reference66 - Flashcards vs comparison-table → comparison-table for side-by-side, flashcards for sequential Q/A67 - Do NOT combine formats in v1 unless explicitly requested68693. LOAD FORMAT FILE (MANDATORY)70 → Read formats/<format>.md71 No ad-hoc layouts. Templates only.72734. DETERMINE CHARACTER SET74 Unicode by default. ASCII fallback if user requested OR destination demands.75 See composition-rules/box-drawing.md.76775. APPLY CANONICAL ARC (multi-panel formats only)78 See composition-rules/narrative-arcs.md.79 Reduce panel count if content doesn't justify the full arc.80816. GENERATE OUTPUT82837. DETERMINE SAVE BEHAVIOR84 - Single-artifact + not multi-section + not "reusable asset" → chat only85 - Multi-panel / multi-section / clearly reusable → auto-save86 - User signaled iteration ("try again", "draft") → chat only87 - User said "save this" → force save88 - User said "don't save" / "chat only" → force chat89908. RUN QA91 - Strict mode for saved/multi-panel/reusable92 - Light mode otherwise93 - Strict QA must pass BEFORE chat render AND BEFORE file write94 - If fails twice → invoke simplify rule95 - If simplify still fails → invoke format fallback (see qa-checklist.md)96979. RENDER + (optional) SAVE98 - Chat preview: ≤80 lines → render full. >80 lines → render first 1-2 sections + "saved to <path>"99 - File write: only AFTER strict QA passes. Path: ~/Ascii-diagrams/YYYY-MM/YYYY-MM-DD-<slug>.md100 - Post-save line: exactly two lines, no fluff:101 Saved to:102 ~/Ascii-diagrams/YYYY-MM/YYYY-MM-DD-<slug>.md103```104105## Output behavior106107### Save path & naming108109- Path: `~/Ascii-diagrams/YYYY-MM/YYYY-MM-DD-<topic-slug>.md`110- Slug: lowercase, hyphen-separated, 6–8 words max, derived from user intent111- Fallback slug if user intent is unclear: `<format>-<short-topic>` (e.g., `playbook-cold-outbound`)112113### File template114115```markdown116# Title117118Short description (1–2 lines)119120---121122## Section 1123124<ASCII inside a code block>125126---127128## Section 2129130<ASCII>131```132133### Chat preview rules134135- ≤80 lines → render the full artifact inline136- >80 lines → render the first 1–2 sections + emit:137 ```138 Full artifact saved to:139 ~/Ascii-diagrams/2026-05/2026-05-17-<slug>.md140 ```141- Offer "expand to show full" only if the user might want it inline142143### Anti-pattern144145Do NOT default to saving everything "just in case." Throwaway sketches do not deserve files. Noise > occasional regret.146147## Composition rules (read on demand)148149- `composition-rules/box-drawing.md` — Unicode set, ASCII fallback, consistency rules150- `composition-rules/width-budgets.md` — per-format max width + overflow handling151- `composition-rules/narrative-arcs.md` — 8 arcs + universal panel rules152- `composition-rules/qa-checklist.md` — light/strict QA + simplify + fallback + no-partial-save153154## Examples (read on demand)155156`examples/<format>-example.md` — one richer reference per format. Read when the format file's inline example isn't enough.157158## v1 boundaries (explicitly out of scope)159160- `mode: quick | publish` flag → v2161- External tools (graph-easy, ditaa, figlet) → manual workflow only, not integrated162- Color / ANSI escapes → not used163- Image export → not in scope164- Format combination (e.g. slideshow with embedded flowchart) → only when explicitly requested165166## Hard rules (do not violate)1671681. **Always load the relevant format file before rendering output.** No ad-hoc layouts.1692. **Strict QA must pass before any file write.** No partial saves. No QA-failed saves.1703. **Never exceed format max width.** Shrink content; never widen past budget.1714. **Default to saving NOTHING.** Save only what matches the save criteria.1725. **Format choice: simplest that preserves clarity.** No combining formats in v1 unless asked.