rikikiHTML slides · built for you and your agent

Your agent writes.
Rikiki checks.
You present.

Turn a brief into slides you can inspect, improve and take into the room.

talk.html / readable source
<deck-feature> <h1 slot="title"> One idea. Clear evidence. </h1> <deck-code lang="ts">…</deck-code> </deck-feature>
$ rikiki check talk.html --json

Read diagnostics → fix → render → review

Brief → HTML → checks → visual reviewPresent live · share offline HTML · export PDF
Rikiki is an HTML presentation toolkit. Give a coding agent a brief and the installed authoring skills, or write the HTML yourself. Components handle slide layouts. The check command inspects the rendered deck and returns diagnostics, including machine-readable JSON, for revision. Rendering produces screenshots for a separate visual review. Automated checks do not judge the argument or validate its evidence: that remains the author's job. Present the result in the browser, bundle standalone HTML or export a PDF. The commands shown are an authoring workflow, not an executed check result. Playwright and the bundler are optional dependencies documented in the setup guide.

The layout is already a component.

Give ideas a place.

This is a native bento. Three cells, one shared grid, room for a clear argument.

<deck-bento>

Keep the evidence.

Use code, tables, diagrams and images. Pick the form that explains the point.

<deck-code>

Shape the rhythm.

Switch layouts to give each idea its own rhythm.

<deck-split>
The tour is itself made from the public components. This slide uses deck-bento and deck-cell, with deck-icon for the section markers. Layout components handle the composition while the author chooses the content and the theme.

What you see is what you edit.

A file you own

Open HTML.
Change an idea.

Readable tags. Ordinary CSS. Keep the source in Git and review exactly what changed.

This slide: deck-split + deck-code

<deck-bento cols="3"> <h1 slot="title"> The layout is a component. </h1> <deck-cell> <h3>Give ideas a place.</h3> <p>One clear argument.</p> </deck-cell> </deck-bento> This is a shortened example of the previous slide's markup. The full slide has three cells. There is no proprietary slide document behind it: the author edits HTML and CSS. The syntax-highlighted example is rendered by deck-code.

Make the trade-off visible.

A quick draft

Get the idea
onto the page.

Choose a layout. Add a claim and its evidence.

A deck for the room

Make the idea
easy to follow.

Check the rendering. Review the story. Rehearse the transitions.

Native deck-versus gives each side equal space. You supply the distinction.

A draft is a useful intermediate state, not a completed presentation. The versus component creates a comparison without having to build its two-column structure by hand. Neither side is declared a winner: they are different stages of the work.

Let the room follow your thinking.

Advance to reveal the next step. The slide stays put.

Start with one sentence.

Show the source or the example.

Make the requested action explicit.

Use the next arrow repeatedly. The native reveal controller advances the flow's internal states before moving to the next slide. This is a working demonstration, not a video or a simulated animation. The same states appear in presenter mode.

Same components. Your visual language.

Palette → semantics → components

A theme is more
than an accent.

Set the type, surfaces, contrast and spacing. Then give individual components their own treatment.

This slide switches from night to paper.

.paper { --rik-surface-page: #f5efe5; --rik-text-default: #201c26; --rik-text-default--muted: #554d60; --rik-accent: #aa3d08; } This slide changes semantic tokens on the same native split layout. The three story decks below the hero take theming further, with different typography, palettes and narrative structures. Readability needs to be checked after a theme change, including component status colours.

Give your agent a feedback loop.

01 / Brief

Set the job.

Name the audience, the decision and the sources. Install the authoring skills.

npx rikiki skills

02 / Inspect

Find defects.

Check the rendered deck. Send the diagnostics back for revision.

npx rikiki check talk.html --json

03 / Review

Look at the result.

Render screenshots, inspect them and revise. Revise until each slide makes its point.

npx rikiki render talk.html
These commands describe the workflow; they are not a live check running in this embedded deck. The skills install the component reference and authoring process. Check and render require the optional Playwright dependency and a browser installation.

A clean check is the start of a review.

Browser inspection

Does it render
correctly?

Catch reported defects in the rendered deck. Inspect every slide and reveal state.

Editorial judgment

Does it make
the point?

Read the evidence. Judge the hierarchy, pacing and visual composition.

Zero reported errors does not certify a persuasive or beautiful presentation.

Mechanical diagnostics and visual editorial review answer different questions. Rikiki's check is useful feedback, but it does not validate facts or guarantee design quality. An author or reviewer needs to inspect the result. This distinction is why the workflow includes screenshots.

A deck built for the moment you present.

Find your place Open presenter mode Keep the rhythm

Open this tour full screen to try the shortcuts. These are native presentation controls.

The keyboard shortcuts work when the deck has focus. In an iframe, click the deck first. Opening the tour in its own tab gives the overview and presenter window more room. Presenter mode includes the slide's internal reveal state as well as its number.

From one file to the room.

Keep the editable source

Share the work.
Make it yours.

Present in the browser. Bundle offline HTML. Export a PDF for the audience.

Start with the setup guide below this deck.

Start a deck

npx rikiki init talk.html

Bundle a standalone file

npx rikiki bundle talk.html

Export a PDF

npx rikiki export talk.html
The setup guide covers Node versions and optional dependencies: Playwright for browser-driven commands, and the bundler for standalone output. PDF is a static output; keep the HTML when you want interactivity and presenter features. This completes the tour.