CLAUDE CODE PLUGIN · VISUAL ARTIFACTS
roxabi-forge
A Claude Code plugin that turns "explain this" into a picture you can ship. Eight skills produce self-contained HTML artifacts — diagrams, galleries, decks, guides, presentations — brand-aware, file://-safe, and deployable to a URL in one command. No Figma, no slide tool, no leaving the terminal.
What it is
Language models write a lot of words. Sometimes you need a picture: an architecture diagram, a side-by-side comparison, a pitch deck, a tabbed guide, a one-pager that lives at a URL. roxabi-forge turns "explain this" into a self-contained HTML artifact you can scroll, share, and ship — triggered from a skill, written to a file, no other tool in the loop.
It is a sibling to roxabi-plugins: where dev-core drives the dev lifecycle, forge drives the visual output. A brand-aware, manifest-indexed HTML pipeline for Claude Code users who want publication-grade visuals without leaving the terminal.
The artifact is one file. No build step, no server, no external assets — open it anywhere, including straight off disk.
Eight skills
Each skill is a trigger phrase that produces one kind of artifact. Pick the shape that fits the thing you're explaining.
| Skill | Produces |
|---|---|
forge-chart | A single-file native diagram — hub-and-spoke, gantt, ER, sequence, data charts. |
forge-slides | A magazine-quality scroll-snap deck, keyboard- and touch-navigated. |
forge-presentation | A long-form scroll presentation — hero, numbered sections, reveals. |
forge-guide | A split-file multi-tab document — user guide, architecture, recap. |
forge-gallery | A manifest-indexed image or audio gallery — pivot, filter, lightbox. |
forge-epic | An issue-linked analysis — scope, dependency graph, acceptance criteria. |
forge-md | Renders existing Markdown to themed HTML — single-file or tabbed. |
forge-init | Initializes the runtime under ~/.roxabi/forge/. |
Self-contained by design
Three properties hold across every skill. They are what make a forge artifact something you can hand to anyone, anywhere.
- Brand-aware — outputs carry the Roxabi design tokens by default; consistent type, colour, and spacing without restyling each one.
- Self-contained — CSS, scripts, and data inline into one file. Nothing to host, nothing to break later.
- file://-safe — every artifact opens straight off disk in a browser, no server required to preview it.
Outputs land in ~/.roxabi/forge/<project>/visuals/, indexed by a manifest so the gallery and the runtime can find and group them.
Ship it to a URL
An artifact that opens off disk also publishes unchanged. One command pushes the visuals/ tree to Cloudflare Pages — the same file you previewed becomes a link you can send. The Roxabi instance lives at forge.roxabi.com.
make forge deploy # push visuals/ → Cloudflare PagesBecause the output is static and self-contained, there is no runtime to operate — the deploy is a file copy, and the URL is just where the file now lives.
Run it
Forge installs as a Claude Code plugin from its marketplace. Add it, install, initialize the runtime once, then trigger a skill by describing what you want.
claude plugin marketplace add Roxabi/roxabi-forge
claude plugin install forge
"init forge" # one-time runtime setup
"draw the architecture of this repo" # → forge-chart
"create deck from #42" # → forge-slidesThe skills, templates, and runtime are all in the open.
- The repo · github.com/Roxabi/roxabi-forge →