Skip to content

Doc type

Presentations

A slide deck you rehearse, mark up and approve.

A presentation is a deck of 16:9 HTML slides, stacked in the order they play. Present plays it full-window with the speaker notes one key away, and each comment names the element on the slide it is about.

"type": "presentation"

Present the deck full-window. Present plays the slides one at a time, each as large as the window allows. ← → step through them and Esc leaves.

What it’s for

Slides from a few plain shapes.

The plain kit’s slide classes cover most decks, and the theme pick colours every slide at once.

  • Kicker and title

    An eyebrow line over the slide’s one point.

  • Body

    36 px text, with accent bullets on its lists.

  • Columns

    Equal columns, one per child: points beside a number.

  • Big number

    One stat, as large as the slide allows.

  • Quote

    A member’s or a customer’s words, set large.

Features

What you can do on the page.

Scroll the deck in one column

The board stacks the slides top to bottom in deck order, the order Present plays them, beside the brief.

Show the speaker notes

Each slide’s notes are Markdown in the doc, never on the slide. In Present, N shows them under it.

Re-skin the deck, then sketch it

The brief’s theme pick re-skins every slide at once. Sketch redraws the deck hand-drawn for a rough first pass.

Comment on a number on a slide

Point at an element on a slide. The comment’s key names the slide and the element, so the agent edits that element in that file.

Compare a slide with the last revision

The Revisions tab puts a slide at two revisions side by side, or lays one over the other as an onion skin.

Approve the presentation

Approve presentation records the approval and your picks on this revision. An edit to any slide asks for approval again.

Works on every doc

Comments, revisions and approval, the same on every type.

See every shared feature
  • Follow a comment to Resolved

    Notes go from Pending to Open when sent, and to Resolved when the agent’s revision says it dealt with them.

  • Send change requests to the agent

    Request changes previews your notes as Markdown, then sends them in one go.

How the agent uses it

The agent writes JSON. The server draws the page.

Each slide is a slide artboard in the doc and a small HTML fragment in the deck’s .design folder. Speaker notes go in the artboard’s notes, never on the slide.

python3 <skill>/scripts/build.py new presentation docs/decks/q3-review.bluedoc.json --title "Acme Fit: Q3 launch review"
python3 <skill>/scripts/build.py docs/decks/q3-review.bluedoc.json
python3 <skill>/scripts/serve.py open docs/decks/q3-review.bluedoc.json
python3 <skill>/scripts/serve.py wait docs/decks/q3-review.bluedoc.json --kind any
acme-fit-deck.bluedoc.json · a slide
{  "id": "actives",  "title": "Weekly actives",  "device": "slide",  "fidelity": "hifi",  "notes": "This is the number to remember: **41,800** members active every week, up from 19,900 in June."}
acme-fit-deck.design/actives.html · the slide
<section class="slide center" data-bd="actives">  <p class="slide-kicker" data-bd="kicker">Weekly active members</p>  <p class="slide-big" data-bd="stat">41,800</p>  <p class="slide-body muted" data-bd="context">Up from 19,900 in June, most of it from the watch app.</p>  <footer class="slide-foot" data-n="3" data-bd="foot">Acme Fit · Q3 launch review</footer></section>

The server wraps each slide in the plain kit, so the agent never writes <head> or tokens. The build fails on any artboard that isn’t a slide.

Install

Pick your agent.

Each one installs the same skill from the GitHub repository.

claude plugin marketplace add andreiverdes/bluedoc
claude plugin install bluedoc@bluedoc

Inside a session the same commands are /plugin marketplace add andreiverdes/bluedoc and /plugin install bluedoc@bluedoc. Start a new session to load the skill.

Needs: Python 3.9 or later on PATH · git, for code reviews · gh, only to import GitHub review threads.