Soul Chat

"Everything is alive. Everything can speak."

"YAML Jazz" and "Markup With Typed Code Blocks" dialogues between characters, objects, rooms, documents, concepts—anything with a soul.

[!TIP] Give anything a voice. Characters, concepts, documents, rooms — if it exists, it can speak.

What This Is

A skill for creating conversations where the structure carries meaning beyond the words. Not just characters talking—documents can talk to documents, rooms can welcome visitors, concepts can explain themselves.

Prefer Markdown format — more human readable, can embed any typed code block.

Format: ## Speaker Name headers, prose, then typed code blocks for data.

# Example structure (not a real code block, just illustration):
# 
# ## The Gardener
# 
# I've been tending these patterns for a while now.
# 
# ```yaml
# observation:
#   pattern: "Files cluster by prefix"
# ```
# 
# ## The Archivist
# 
# Let me add some context...

Characters share data by embedding YAML/JSON blocks in their dialogue — YAML-JAZZ in action.

Contents

Quick Start

Chats live OUTSIDE this directory (per ABOUT-NOT-INSIDE).

Use Markdown format — .md not .yml.

Name chats with the subject first: readme-symposium.md, yaml-jazz-debate.md

See CHAT.md.tmpl for the full template.

Entity Types

The Intertwingularity

Everything speaks. Everything is connected.

graph LR
    SC[💬 soul-chat] -->|voices| TC[🎴 card]
    SC -->|voices| R[🚪 room]
    SC -->|voices| DOC[📄 documents]
    SC -->|voices| CON[💡 concepts]
    
    TC -->|has voice via| SC
    R -->|welcomes via| SC

Dovetails With

Sister Skills

Protocol Symbols

Kernel

• kernel/NAMING.yml — How to name chat files

Navigation