Supported Types

Generate ASCII diagrams from $ARGUMENTS. Detect type, render in monospace code block.

Supported Types

Type	Trigger keywords	Pattern
Timeline	timeline, journey, D0, phases, milestones	Vertical D0 → D1 → D3+
Compare	compare, vs, side-by-side, A/B, options	┃ A ┃ B ┃ columns
Funnel	funnel, experiment, trial, variants, conversion	CTO pres style (see template)
Flowchart	flow, process, steps, pipeline, architecture	┌─┐ → ┌─┐ boxes
Scorecard	scorecard, actions, tasks, owner, checklist	☑/☐ grouped by owner
Explain	explain, pyramid, layers, levels, tier, ELI	Pyramid + deep dive
Sequence	sequence, interaction, request, call, API, message	Lifelines + ──►
State	state, lifecycle, status, transition, machine, cycle	[S] ──► [S]
Tree	tree, hierarchy, org, structure, taxonomy, nested	├── └──

⚠ "hierarchy" → Tree (primary). "breakdown" → Explain.

If type is ambiguous → use AskUserQuestion to clarify.

---

Template: Funnel Experiment (CTO pres style)

╔════════════════════════════════════════════════════════════╗
║  EXPERIMENT NAME                              D0: YYYY-MM  ║
╠════════════════╦═════════════════╦════════════════════════╣
║  CONTROL       ║  VARIANT-A      ║  VARIANT-B             ║
║  Condition A   ║  Condition B    ║  Condition C           ║
╚════════════════╩═════════════════╩════════════════════════╝

TIMELINE ↓       CONTROL          VARIANT-A        VARIANT-B
──────────────────────────────────────────────────────────────
D0               👤 Signup         👤 Signup        👤 Signup
                 Free access       [🔒 paywall]     [🔒 soft]

D0–D3            ⏫ Upload          ⏫ Upload         ⏫ Upload
                 🎬 Export free    🎬 Export free   🎬 Export
                                  ┌─────────────┐
D3               💸 Debit          │ 💸 Debit    │  💸 Debit
                                  └─────────────┘

D3+              💳 Pay            💳 Pay           💳 Pay
                 💔 Cancel         💔 Cancel        💔 Cancel
                 ✅ Clean          ✅ Clean         ✅ Clean

════════════════════════════════════════════════════════════
METRICS          CONTROL          VARIANT-A        VARIANT-B
────────────────────────────────────────────────────────────
Retention D30    42%              38%              ≈44%
ARPU             $12.40           $13.10           $11.90
MRR/1K           $5 220           $4 980           ≈$5 240
Lift vs control  —                -4.6%            ≈+0.4%
════════════════════════════════════════════════════════════

Naming conventions:

• Generic: CONTROL / VARIANT-A / VARIANT-B
• Trial context: FREEMIUM / SOFT-TRIAL / HARD-TRIAL / HARD-EXPORT

METRICS rules:

• No emoji in METRICS section — numbers only
• ARPU = clean active subscribers (not all subs)
• MRR/1K = (clean/1K) × ARPU (durable, not snapshot)
• ≈ prefix for estimates

---

Template: Timeline (vertical)

TIMELINE: User Journey — Free → Paid
══════════════════════════════════
D0    👤 Signup → onboarding email
      └── Feature discovery

D1–D3  ⏫ First upload
       🎬 Export attempt
       [🔒 paywall hit if no plan]

D3    ┌──────────────────┐
      │ 💸 Trial expires │  ← blocking event
      └──────────────────┘

D7    💳 Convert / 💔 Churn decision

D30   ✅ Clean retained
      💔 Lapsed → winback flow
══════════════════════════════════

---

Template: Comparison (side-by-side)

                ┃  OPTION A       ┃  OPTION B       ┃
────────────────╋─────────────────╋─────────────────╋
Criteria 1      ┃  Value          ┃  Value          ┃
Criteria 2      ┃  Value          ┃  Value          ┃
Criteria 3      ┃  ✓ strong       ┃  ⚠ weak         ┃
────────────────╋─────────────────╋─────────────────╋
Verdict         ┃  ► Recommended  ┃  ✗ Rejected     ┃

---

Template: Flowchart (Boxes + Arrows)

┌──────────┐     ┌──────────┐     ┌──────────┐
│  Step 1  │  →  │  Step 2  │  →  │  Step 3  │
└──────────┘     └──────────┘     └──────────┘
                      │
                      ▼ (condition)
                 ┌──────────┐
                 │  Alt     │
                 └──────────┘

---

Template: Scorecard (Owner + Checkboxes)

════ OWNER: Engineering ══════════════
☑  Task 1 — done
☐  Task 2 — pending          ⚠ blocker
☐  Task 3

════ OWNER: Product ══════════════════
☑  Spec complete
☐  Validation                ► by D+3

---

Template: Explain (Pyramid + Layers)

╔══════════════════════════════════════╗
║  CONCEPT: [Name]                     ║
╠══════════════════════════════════════╣
║         ▲                            ║
║        ███  L3 — Expert              ║
║       █████  L2 — Practitioner       ║
║      ███████  L1 — Beginner (ELI5)   ║
╠══════════════════════════════════════╣
║  LEVEL: L1 — Beginner                ║
║                                      ║
║  What     → [one-sentence def]       ║
║  Analogy  → [concrete metaphor]      ║
║  Example  → [real-world case]        ║
║  Why care → [impact / so what]       ║
╚══════════════════════════════════════╝

Rules:

• Default: L1 unless "expert", "deep", or "levels" in prompt
• Levels: L1 Beginner / L2 Practitioner / L3 Expert
• DEEP DIVE always present, depth scales with level
• "breakdown" → Explain; "hierarchy" → Tree

---

Template: Sequence (Interaction Flow)

  Actor A          Actor B          Actor C
     │                │                │
  1. │ ──── req ─────►│                │
     │                │ ──── fwd ─────►│
  2. │                │                │ process
     │                │◄─── resp ──────│
  3. │◄─── result ────│                │
     │                │                │

Notes:
  • Async: description
  • Error: description

Rules:

• Number each exchange group (1. 2. 3.)
• ──► request / ◄── response
• Notes section for async, error, retry paths
• Max 4 actors; split into sub-diagrams if larger

---

Template: State Machine

  ● START
  │
  ▼
┌─────────┐  event A  ┌─────────┐
│ State 1 │──────────►│ State 2 │
└─────────┘           └─────────┘
     │                     │
     │ event B              │ event C
     ▼                     ▼
┌─────────┐           ┌─────────┐
│ State 3 │           │  END ◉  │
└─────────┘           └─────────┘

TRANSITIONS
────────────────────────────────
From      │ Event   │ To
──────────┼─────────┼──────────
State 1   │ event A │ State 2
State 1   │ event B │ State 3
State 2   │ event C │ END

Rules:

• ● initial state, ◉ terminal state
• Label every arrow with event or condition
• Transitions table for machines with >4 states

---

Template: Tree / Hierarchy

Root
├── Branch A
│   ├── Leaf A1
│   └── Leaf A2
├── Branch B
│   ├── Leaf B1
│   │   └── Sub-leaf
│   └── Leaf B2
└── Branch C
    └── Leaf C1

Legend: ├── sibling  └── last child  │   continuation

Rules:

• ├── non-last children, └── last child
• │ (pipe + 3 spaces) for vertical continuation
• 4-space indent per level
• "hierarchy" → Tree; for concept layers → Explain

---

Instructions

1. Parse $ARGUMENTS → detect type from keywords
2. If ambiguous → AskUserQuestion: "Type de diagramme : timeline / compare / funnel / flowchart / scorecard / explain / sequence / state / tree ?"
3. Fill appropriate template with user content
4. Output in triple-backtick code block (monospace)
5. Width ≤ 80 chars, align columns