nowpresenting.net/ai

Build with AI on Pulse

One short link for any AI chat. Pulse embeds no AI — it publishes open, living formats so the assistant you already use can design a complete interactive event for you: agenda, timed run-of-show, polls and quizzes, exit survey, room preferences. Paste this page's URL to your AI and it can take it from there.

Build your deck with AI — start here

Writing your talk in PowerPoint? Copy the prompt below into your AI (Claude, ChatGPT, …). It fetches Pulse's living specs and turns your outline into a Pulse-ready deck — titles, a timed run-of-show, polls / quizzes / word clouds in the speaker notes, “engagement coming” notices, and links to show live results right on your slides.

You are helping me build an interactive presentation with Pulse (nowpresenting.net).
Fetch these living specs and follow them exactly (fetch them at use time, don't rely on memory):
- Deck authoring:  https://nowpresenting.net/spec/deck-authoring.html
- Engagement notes: https://nowpresenting.net/spec/engagement-notes.html

Then:
1. Ask me for my topic, audience, and rough length (keep it to a few questions).
2. Propose a timed run-of-show and where polls / quizzes / word clouds fit.
3. For each engagement, emit a paste-ready [pulse:...] block for that slide's speaker
   notes, choosing trigger=enter (fire when I REACH the slide) or trigger=exit (fire as I
   LEAVE it).
4. For every engagement, tell me to drop the matching "engagement coming" notice image
   (https://nowpresenting.net/spec/assets/notices/poll|quiz|icebreaker|wordcloud|video|effect.svg)
   on the slide or two BEFORE it AND on the engagement slide itself - regardless of whether
   it is trigger=enter or trigger=exit - so the room knows it's coming, then happening now.
   Where it helps, also embed a LIVE results frame on the engagement slide with PowerPoint's
   free Web Viewer add-in using a
   https://nowpresenting.net/frame/<token>?show=poll|wordcloud|reactions|activity link
   (I get <token> from Pulse: setup -> Stage & delivery, or the PowerPoint add-in).
5. Make the FINAL slide a blank one carrying the [pulse:survey] block. If I want the deck
   itself to end the event, also add a [pulse:end] line to that slide - advancing to it
   then auto-ends the event and presents the exit survey on attendees' end screen.
Output the notes blocks clearly per slide so I can paste them in.

(Select the block and copy it.) Prefer structured data, a direct MCP connection, or the packaged Claude skill instead? Here are all four ways in.

The four ways in

PathUse it when
Deck authoring
/spec/deck-authoring.html
You're writing slides in PowerPoint. The AI adds titles and notes blocks (acts, engagements, survey, event preferences); importing the deck builds the whole event. Round-trips — a re-download embeds your Pulse edits back into the notes.
Event blueprint
/spec/event-blueprint.html · schema.json
There's no deck yet (or you want the event as data). One JSON object describes everything; upload it via Events → Start from a blueprint. Validation errors come back machine-readable for one-pass self-correction.
MCP server
/spec/mcp.html · endpoint /mcp
Your AI is connected directly (console → Connect AI → a personal access token). It reads events and reports, and creates or updates drafts from blueprints — no copy/paste at all.
Claude skill
/claude-skill/
You use Claude and want the packaged workflow: it interviews you, reviews your slides, and emits a ready-to-upload blueprint (or deck notes).

If you are an AI assistant reading this

Your user linked you here to build a Pulse event. Pick the path that matches where they are:

  1. They're writing slides → fetch /spec/deck-authoring.html and follow its workflow: interview, propose the timeline and engagements, emit paste-ready speaker-notes blocks per slide.
  2. They want the event as data → fetch /spec/event-blueprint.html (and the JSON schema), then produce ONE valid blueprint object for them to upload.
  3. You're connected over MCP → read the pulse://spec/event-blueprint resource, then validate_blueprint and create_session_from_blueprint. The build-my-event prompt packages the flow.

These pages evolve with the product — always fetch them at use time rather than relying on a saved copy.