Generate

/generate is the mirror of /ingest. Where /ingest funnels many formats into one canonical wiki, /generate fans that canonical wiki back out into any number of consumable formats.

flowchart LR
    src1["URLs"] --> ingest[["/ingest"]]
    src2["PDFs"] --> ingest
    src3["Videos"] --> ingest
    src4["Gists"] --> ingest
    ingest --> wiki[("wiki/**<br/>markdown pages")]
    wiki --> generate[["/generate"]]
    generate --> out1["book.pdf"]
    generate --> out2["slides.pdf"]
    generate --> out3["podcast.mp3"]
    generate --> out4["video.mp4"]
    generate --> out5["quiz.html"]

    classDef source fill:#e0af40,stroke:#8a6d1a,color:#1a1a1a
    classDef engine fill:#5bbcd6,stroke:#2e6c7c,color:#0b0f14
    classDef output fill:#7dcea0,stroke:#2d6a4f,color:#0b0f14
    class src1,src2,src3,src4 source
    class ingest,generate,wiki engine
    class out1,out2,out3,out4,out5 output

Usage

/generate <type> <topic> [--vault <name>] [handler-specific flags]

Examples:

/generate book transformers --vault llm-wiki-research
/generate pdf wiki/concepts/attention.md --vault llm-wiki-research
/generate slides rag-patterns --vault llm-wiki-research --count 15
/generate podcast "llm wiki design" --length medium
/generate video transformers
/generate quiz attention --difficulty medium --count 10

How It Works

/generate is a thin router. It:

1. Reads the first positional argument as the artifact type (book, pdf, slides, …).
2. Looks up the matching handler skill at .claude/skills/generate-<type>/SKILL.md.
3. Resolves --vault (single vault auto-picks; multi-vault prompts).
4. Forwards every remaining argument to the handler.
5. The handler does the rest — selection, rendering, sidecar, commit.

No registry. Adding a new artifact type is just creating a new .claude/skills/generate-<your-type>/ directory. The router picks it up on the next invocation.

Currently-Implemented Handlers

Phases 2A–2D have shipped the full artifact surface:

Type	Handler	Phase	Purpose
book	generate-book	2A ✅	Pandoc-rendered book PDF with title page + TOC
pdf	generate-pdf	2A ✅	Shareable PDF from a page or folder (no ceremony)
slides	generate-slides	2B ✅	Marp (default) or Reveal.js deck
mindmap	generate-mindmap	2B ✅	Markmap HTML (Mermaid fallback)
infographic	generate-infographic	2B ✅	Observatory-themed SVG + optional PNG
podcast	generate-podcast	2C ✅	TTS-rendered MP3 (ElevenLabs / OpenAI / Piper)
video	generate-video	2C ✅	Remotion MP4 with optional voiceover mux
quiz	generate-quiz	2D ✅	Single-file HTML self-test
flashcards	generate-flashcards	2D ✅	Anki .apkg deck (stable deck IDs)
app	generate-app	2D ✅	Vite + React explorer app (2 templates)

Invoking a not-yet-implemented type prints a clear error listing the handlers currently available.

Artifact Contract

Every handler must follow the artifact conventions:

• Output path vaults/<vault>/artifacts/<type>/<topic>-<date>.<ext>
• .meta.yaml sidecar with provenance fields
• Deterministic source-hash via the shared source-hash.sh helper

This contract is what makes drift detection and round-trip fidelity testing possible in later phases.

See Also

• generate-book — the full-book handler
• generate-pdf — the single-page/folder handler
• generate-slides — presentation deck handler
• generate-mindmap — interactive mindmap handler
• generate-infographic — SVG infographic handler
• generate-podcast — spoken-word MP3 handler
• generate-video — Remotion MP4 handler
• generate-quiz — single-file HTML self-test
• generate-flashcards — Anki .apkg deck
• generate-app — Vite + React explorer app
• artifact conventions — storage path, sidecar schema, source-hash algorithm
• /ingest — the opposite direction