A tiny toolkit for wildly good decks

Small toolkit.
Wild ideas.

Your agent can write slides. It also needs to see where they break. Rikiki gives it HTML components, browser checks and screenshots to work from.

Open source · Runs in your browser

A real Rikiki deckOpen the full tour
Slide 1 of 10

A working tour, built with the components it explains.Get the authoring skills

Watch the workflow

Watch a draft
get a second look.

See Rikiki in action.
73 seconds · With music.

An agent writes the HTML. Rikiki checks the deck, reports defects and renders screenshots for review. Fix the draft, inspect it and take the presentation into the room. The film uses on-screen text and music.

Built for the agent workflow

Would you present
the first draft?

Give the agent a brief and the tools to inspect its work.
You keep the final review (and the microphone).

Start here / Your brief
“Explain our incident to the engineering team. Ten minutes. Show the timeline, the root cause and what we changed. Use the attached report. Don't invent the numbers.”

Tell it who is in the room, what they need to decide and which sources to use. Leave the missing numbers blank.

A workflow your agent can follow

Give it the instructions.

The authoring skills tell your agent which components exist, how to compose them and how to check the result. Install them alongside the toolkit.

Set up agent authoring
npm i rikiki-deck
npx rikiki skills
Set up your agent

From a broken draft to a reviewed slide

Catch the defects. Then improve the slide.

Example slide before fixes: clipped content and small text
● ● ●rikiki check --json

3 errors · 2 warnings

  • RESOURCE_MISSINGerror
  • UNKNOWN_ELEMENTerror
  • CONTENT_CLIPPEDerror
  • TEXT_LAST_LINE_ORPHANwarning
  • TEXT_TOO_SMALLwarning

A deliberately flawed draft, followed by a content and visual revision. Results are captured CLI runs, not a live browser check.

A draft is the start of the loop.

Explore each handoff, including the return from checks to source.

Brief

You define the audience, the decision and the source material. The agent must mark missing facts instead of inventing them.

Read the full authoring workflow
01 / Write

Source you can inspect.

The agent writes readable HTML with real components. Change the text, review a diff, keep it in Git.

02 / Check & revise

Let it inspect its work.

Run rikiki check --json, fix the diagnostics, then render screenshots to catch what the checks cannot judge.

03 / Review & share

You still do the review.

Review the narrative, evidence and visual result. Then deliver a standalone HTML deck or export a PDF.

From the source file to the speaker notes.

Readable HTMLPresenter notesOffline HTML & PDF

Different species. Same toolkit.

Three briefs
from unlikely clients.

Fifteen slides each, built from native components.
ACME has requested another design review.

Equipment selection example cover

Equipment selection

The right broom. For your game.

A Quidditch captain compares candidates, designs the trial and decides when to buy.

Explore 15 slides
Technical design review example cover

Technical design review

This time. For sure.

ACME takes a capture plan through its missing dependency, failure modes and an actual abort condition.

Explore 15 slides
Works proposal example cover

Works proposal

Built for the big bad.

Three siblings turn separate houses into a shared refuge, from the weakest boundary to the final inspection.

Explore 15 slides

Three fictional briefs. Full stories, speaker notes and distinct visual systems. Explore the full component tour

Start with the content

Pick the component
the idea needs.

Explore the component library

Illustrate

Say what the picture shows.
Rikiki draws it.

A scene is a few lines of data: cards to compare, steps in order, lanes that a gate cuts across. Rikiki measures every word in the slide's own font, lays the drawing out in your theme and plays it when the slide opens.

When an item does not fit, rikiki check names it, says which field is too long and how many characters that field holds.

Draw a scene from a brief
npx rikiki scene plan brief.json --measure
npx rikiki scene compile brief.json --candidate lanes
npx rikiki check talk.html --slides 5
Open the scenes deck
One slide of a real deck. Traffic runs, a check goes red, the gate comes down and the late ones queue against it.

Make it yours

Change the theme. Keep the deck.

Live tokenChange the accent in the rendered deck
Customize every token
Live previewClick a theme above · the slide below re-renders.

Yours, all the way down

The slide
is the source.

Choose a layout. Add your content. Style it with CSS. This is the source of the incident-review cover. Yes, the whole cover.

Keep it in Git, review a diff, or let your coding agent make the first draft.

Meet the components
incident.htmlHTML + web components
<deck-cover
  brand="Fieldnotes · Engineering"
  speaker="Platform team"
  audience="Incident review"
>
  <h1>Ship small.<br><span class="accent">Recover fast.</span></h1>
  <p class="sub">A smaller release gives you less to undo.</p>
</deck-cover>

No slide editor required. No build step to view your deck.

From a file to a room

Start with a file.

Follow the setup guide
Write

Make the first draft.

Start from an editable file. Write it yourself, or let your agent work from the brief.

npx rikiki init talk.html
Review

Give the draft feedback.

Fix the reported defects. Inspect the screenshots. Check the claims against your sources.

npx rikiki check talk.html
Deliver

Send the presentation.

Present with notes, send an offline HTML file, or hand over a PDF. Keep the editable source.

npx rikiki bundle talk.html

The setup guide covers the extra dependencies (the browser and bundler need installing too).

Optional modules

Bring only the pieces the deck needs.

The ~43 KB initial load excludes these modules. In a source deck, imported modules load when their feature starts. A standalone bundle packages them locally.

Measured from this build. Sizes shown after gzip compression.

  1. 1.7KB gzip

    transitionsdeck-transition.js

    Add slide, fade, zoom or flip transitions only when a deck asks for them.

    Activatetransition="slide"

  2. 5.9KB gzip

    presenter modedeck-presenter.js

    Open the current slide, next slide, notes and timer in a synchronized presenter window.

    Activatepress P

  3. 0.5 + 113KB gzip, loader + engine

    syntax highlightingshiki.js

    Load TextMate syntax highlighting and its vendored engine on first use, with no CDN request.

    ActivateinstallShiki()

Optional component modules

<deck-agenda> · <deck-flow> · <deck-graph> · <deck-kpi-grid> · <deck-timeline> · <deck-versus> · and more

A deck is plain HTML, so your own custom elements or a stylesheet can sit next to it and load with a <script type="module"> tag, with no build step. Read the API reference

Before you start

A few practical answers.

The deck runs in the browser. The authoring tools run locally. Here is what to expect.

Open the setup guide ↗
What do I need to know to create a deck?
HTML and CSS are enough. Write the supplied custom elements, then change CSS variables for your brand. Lit, a small Web Components library, is an implementation detail; deck authors do not write Lit classes or templates.
Can I write my slides in Markdown?
Not as a deck format, and that is a design choice: a slide is an HTML custom element, so the file you write is the file the browser runs, with no custom syntax or --- separator to learn. Inside a slide, the core <deck-md> component renders standard GitHub-flavoured Markdown, including headings, lists, links, tables, code blocks and images, plus one ::: cards fence that expands into a card grid. A deck can mix HTML slides and Markdown bodies freely.
Can I print my deck to PDF?
Yes, two ways. From the browser, print with backgrounds on: the deck carries its own print stylesheet, so every slide becomes one page at the deck’s canvas size, chrome hidden. Or run rikiki export deck.html --output deck.pdf, which drives a headless Chromium and waits for fonts and diagrams first. The CLI needs Playwright, an optional peer dependency.
Is there a presenter mode with notes?
Yes. Wrap notes in <deck-notes> inside any slide, then press P during the talk. A popup opens with the current and next slide, the notes, a timer and a slide counter. The two windows synchronize locally through BroadcastChannel; no external service is involved.
How do I theme a deck for my brand?
Copy themes/rikiki.css, change the palette and semantic CSS variables, then link your file instead of the default theme. For one component instance, override its documented --deck-* variables directly.
Can I embed a deck in documentation or training?
Yes. Put <deck-root> in a page and add autoplay loop swipe for a touch-friendly carousel with the same ~43 KB initial load. Keyboard input stays scoped to the deck while it has focus.
What does rikiki check report?
rikiki check loads every slide in Chromium and reports structural, runtime, timing and visual-layout risks. It does not test contrast, focus order or screen-reader output, so keep an accessibility review in your release process.
Is a deck accessible?
The example decks are tested with axe in Chromium, Firefox and WebKit, and a serious or critical violation fails the suite. The overview opens, moves and picks a slide with the keyboard alone, every on-screen control is a real focusable button, a slide change is announced to assistive technology through a live region, and no slide animates under prefers-reduced-motion. rikiki export writes a tagged PDF with one bookmark per slide. Those tests cover the shipped examples and the runtime, not the contrast or the reading order of the content you write.
What requires Node.js?

Presenting a deck? A browser is enough.

Creating and checking one? The CLI needs Node.js. Supported versions: 20.19+ (20.x) or 22.12+.

Browser checks, screenshots and PDF

check, render and export use Playwright and Chromium.

Browser tooling
npm i -D playwright
npx playwright install chromium

Standalone HTML

bundle and init --standalone use the optional bundler.

Bundler
npm i -D rolldown
Which browsers are tested?
The base rendering, navigation, scaling and offline-bundle contract is tested in Chromium, Firefox and WebKit. Presenter notes, previews and reveal steps also work in Firefox and Safari. Automatic placement on a second screen uses Chromium’s Window Management API. CLI PDF export uses headless Chromium.
Why is there no build step and no custom syntax?
There is no build step on the author side: the served folder contains the runtime, so you open index.html from any static HTTP server and it runs. Everything rests on Web standards, namely Custom Elements, Shadow DOM, ES Modules and CSS custom properties, with a thin component library rather than an application framework underneath. The source is readable HTML, so a slide reads the same in your editor and in the browser. Features beyond the core, such as presenter mode, transitions or syntax highlighting, are opt-in modules you import only when a deck needs them.
Who maintains it, and what is the release status?
The project is developed by Cédric Chariere Fiedler and released under the MIT license; source, issues and merge requests live at gitlab.com/tordu-jardin/rikiki. Version 0.8.0 shipped on 28 October 2026, and from that tag a breaking change means a major version bump. The changelog lists every release.

Room for one more wild idea

Got a strange idea?

Good. Give it a few slides.

Build your first deck

Install the toolkit

Install Rikiki
npm i rikiki-deck
Current release v0.8.0