holocron

Holocron — Star Wars Old Republic Writing Plugin

A Claude Code plugin for writing Star Wars Old Republic short stories, novellas, and novels. Forked from fiction by Daniel Howells (MIT) and re-tooled for Legends/EU-era prose work.

Status: v1.6.0 — adds AI voiceover via the official ElevenLabs MCP server. New /holocron:voice-act command and voice-actor agent. Four modes — audition (compare candidate voices for casting), soundbite (confirm a locked voice), scene (multi-voice render of a finished scene), line (single-line re-take). Per-character voice assignments live in world/voice-cast.md. Renders land in inserts/audio/ with .transcript.txt sidecars. The manuscript stays clean — no SSML, no emotion tags written into chapter files; all per-render direction lives in the in-flight ElevenLabs prompt. First MCP integration in the plugin. v1.2.0's author voice as first-class concept. New Voice phase in /holocron:new (Phase 2, between Era and Premise) where you declare YOUR voice in your own words. Voice lives in craft/voice.md and is imported into CLAUDE.md as shared agent context — so every agent reads it as authoritative. The critic personas (Lucas, Zahn, Stover, Karpyshyn, Traviss, James Wood) are now explicitly framed as reviewers only, not voice models. Voice travels across projects via the new import flow. /holocron:adopt now produces craft/voice-analysis.md (raw evidence) instead of writing the declared voice itself — the author authors voice.md during the wizard's Voice phase. v1.1.0's /holocron:adopt entry-point and v1.0.0's writing workflow (plan → outline → write → review → critique → edit → build), persona reviewers, specialist reviewers, ~130-file master knowledge base, interactive dashboard, in-universe script renderer, and EPUB build pipeline are all carried forward. On top of the 1.0.0 baseline: the core writing workflow (plan → outline → write → review → critique → edit → build), the persona reviewers (Karpyshyn / Zahn / Traviss / Stover / Lucas / James Wood), the specialist reviewers (Force lore, era continuity, Mando'a / Sith / Huttese linguistics, in-universe beta), the ~130-file master knowledge base, the interactive project dashboard, the in-universe script renderer, and the EPUB build pipeline are all production-ready for personal Old Republic writing projects. See CHANGELOG.md for per-release detail.

Why "Holocron"

In-universe, a holocron is a Jedi or Sith knowledge container — a record of teachings, history, and craft. That's the metaphor for this plugin: a structured store of writing tools and Old Republic lore that you carry from story to story.

Scope

• Era: Old Republic, Legends/EU primary canon. Covers Pre-Republic Jedi/Sith, Tales of the Jedi (~5000–4000 BBY), the Mandalorian Wars and Jedi Civil War (~3964–3950 BBY), KOTOR II, SWTOR / Cold War (~3653 BBY), the New Sith Wars, and Bane / Rule of Two (~1000 BBY) — eight timeline files at consistent depth, plus cross-references into factions, people, places, tech, and language.
• Lengths: short story → novella → novel.
• Use: personal first, but installable as a Claude Code plugin (see below).

Install

Holocron is a Claude Code plugin distributed as a single-plugin marketplace inside this repo. Inside Claude Code:

/plugin marketplace add PetitChu/holocron
/plugin install holocron@holocron

That clones the repo, registers the marketplace, and installs the plugin. After install, the slash commands listed below become available under the /holocron: prefix.

To upgrade later: /plugin marketplace update holocron then /plugin install holocron@holocron --upgrade.

Each tagged release also produces a downloadable holocron-<version>.zip on the Releases page for offline install. The release pipeline is documented in RELEASING.md.

Dependencies

/holocron:build compiles your manuscript into an EPUB via pandoc, so a pandoc binary on your PATH is required for that command. Quick install: winget install --id JohnMacFarlane.Pandoc -e (Windows), brew install pandoc (macOS), or the package-manager equivalent on Linux (apt, dnf, pacman all carry it). The build skill runs a preflight check and surfaces the full cross-platform install guide if pandoc is missing — no other day-to-day commands depend on it.