Start with one sentence
Tell your AI agent what the presentation must achieve. Review its brief and outline, then refine one live draft into a verified deck.
What should this presentation help people understand, decide, or do?
What the handoff completes
- Prepare — creates a safe project and installs its version-matched Codex and Claude Code workflows.
- Plan — for a new or explicitly replacement-scoped deck, resolves the brief, writes a complete outline plus a machine-checkable story contract, opens its plan-only Storyboard, and stops for your approval.
- Create — turns the approved plan into readable MDX, speaker notes, a topic-specific visual system, and intentional motion.
- Preview — reuses that local server as soon as a coherent end-to-end Draft 1 compiles, then shares the audience URL for content feedback without pausing the work.
- Refine and deliver — checks every rendered state, improves the same live draft, and only then builds the production presentation or requested PDF.
The public prompt.md only starts the work. Once the project exists, its local
instructions and skills take over so the agent always follows the contract for the installed Drever
version.
When the brief is incomplete, the agent asks a short adaptive interview. It starts with the topic
when that is missing, then resolves essentials such as the audience outcome, duration, and visible
slide density before asking subject-specific questions about evidence, scope, story, visuals, or
delivery. The density choice distinguishes concise presenter-led slides with fuller notes, a
balanced deck, and more detailed reader-led slides. Every decision offers concrete lettered options,
explains what each option changes, and still accepts a combined or free-form answer. Reply
compactly—for example, 1A, 2C—or use the single escape at the end of any round: Skip remaining
questions — surprise me. The next round responds to your earlier choices instead of repeating a
fixed questionnaire, and the escape ends the interview immediately.
The agent then writes the resolved direction and numbered outline to brief.md, records every
slide's job, evidence, focal artifact, composition, density, and motion ownership in
drever.plan.json, runs the fast source check, and opens the exact /storyboard URL reported by
the development server before stopping for approval. The Storyboard is a polished, read-only view
of the plan and does not import the MDX deck, Theme, or presentation runtime. The escape delegates
unanswered choices but does not bypass this review. Once you approve the plan, the same server and
contract guide initial design and authoring until the live Draft 1 opens; deeper rendered review then
improves that same URL while you can already inspect the story.
The work happens in ordinary files on your machine. Setup succeeds when the agent leaves a running
local preview, a readable slides.mdx, and the requested web or PDF outputs ready for review.
The first URL is intentionally a progress milestone, not a claim that the deck is finished. Review the story, facts, and emphasis immediately while the agent continues checking readability, layout, motion, Steps, and browser behavior. Feedback can arrive during that pass; the agent updates the same live preview, discards stale checks, and delays the production build until the refined preview is stable. Authoring and design use source-only and affected-route checks during iteration; review owns the exhaustive rendered gate, and delivery reuses fresh review evidence for the final build or requested export.
Know what runs where
The website button copies text; it does not upload the brief or start a hosted generation job. Paste the prompt into the coding agent you already trust. That agent creates a local React and MDX project, installs packages from npm, and may use the network for research only when the brief and your agent permissions allow it.
Drever does not add telemetry to the generated project. Your chosen AI provider, any remote media, and the platform where you later publish the static build each keep their own privacy contract.
Give the agent a useful outcome
A single sentence is enough to begin. Include the audience, the change you want, and any required source material when you know them:
Create a short presentation for local residents about three proposals for a shared public space. Help them understand the trade-offs and decide which proposal to support. Use the planning brief and survey results as source material.
The agent can infer ordinary details and state its assumptions. It marks at most one option as recommended when your brief supports a clear default. After the topic is known, say Skip remaining questions — surprise me in any round to let it resolve every unanswered choice, answer with option letters, combine options, or reply in your own words while the questions remain useful.
Set up manuallyFor people who prefer to control every command.
Requirements
Drever targets current tools on purpose:
- Node.js 24.18 or newer.
- A current Safari or Chromium-family browser.
- Playwright Chromium only for rendered checks, design import, or PDF export.
There is no legacy router or animation fallback. Drever respects prefers-reduced-motion while keeping the same presentation-state model.
Create a project
npm create drever@latest my-slides
cd my-slides
npm run devThe creator writes brief.md, slides.mdx, package scripts, and project-local skills for Codex and Claude Code.
Inspect and deliver
npm run check
npm run build
npm exec -- drever browser install
npm run exportInstall Playwright Chromium only when a browser-backed workflow requires it. See the command reference for every command and option, the authoring guide for MDX and the delivery guide for build, deploy, and export behavior.
See how project-local skills, live context, and optional MCP keep AI work grounded.