AI workflows

Start from any coding agent

The public prompt.md is a small bootstrap for an empty workspace. Give it a brief in ordinary language:

Fetch and follow https://drever.dev/prompt.md. Brief: “Help local residents compare three proposals for a shared public space.”

The bootstrap checks the workspace, creates a safe project, and then hands control to the version-matched instructions installed inside that project. It does not duplicate the full authoring contract or silently change an existing Drever version.

The website copies an even smaller handoff—Fetch and follow https://drever.dev/prompt.md, plus the brief when one was entered. This direct fetch-and-follow instruction avoids activating a competing generic presentation workflow before Drever's current contract is loaded. If important choices are missing, the agent asks for the topic first and may include common missing context in the same opening round. It puts every concrete question first, then offers one Skip remaining questions — surprise me escape. It matches the user's language by default and never silently guesses the duration without an explicit skip-remaining request.

Command examples use npm. Project-local guidance detects pnpm, Yarn, and Bun and selects their equivalent local runner instead of assuming a global drever executable.

Agent-first, not agent-only

Drever makes AI authoring a versioned project contract. It does not hide the source behind a hosted editor or a private prompt. The same MDX remains readable, reviewable, and editable by a person.

New projects contain five local workflows for Codex and Claude Code:

1. Create a deck from a brief.
2. Derive a subject-led, version-controlled visual system.
3. Make focused authoring changes.
4. Review presentation readiness.
5. Deliver verified web and PDF artifacts.

The design workflow derives its direction from the subject, audience, venue, source material, and purpose. When research is allowed, it can use current primary official sources as evidence for palette, typography, imagery, and motion while respecting asset and font licenses. It studies all eight official designs as equal references, uses Basic only as the neutral fallback, and persists the result locally so every build is deterministic.

Motion follows the same subject-led rule. Ask the agent to explain how a key object changes role across the story—for example, hinting below the canvas, entering as evidence, then docking at low contrast as context—instead of requesting a list of effects. Use an external tool only when a specific capability justifies it; the optional examples in the Motion guide are starting points, not defaults or endorsements. Verify the current official source and license, adapt the result to the presentation, and preserve accessible, reduced-motion, document, and export outcomes.

Refresh them after upgrading:

npm exec -- drever agent sync --target all

The sync command preserves instructions outside its managed blocks and never overwrites an unmarked, user-owned skill.

Give the agent exact context

npm exec -- drever context --json
npm exec -- drever context talks/keynote.mdx --json

The report contains the resolved canvas, exact slides and sparse Step stops, authored source ranges, theme tokens and guidance, motion intents, layout recipes, component manifests, ordered plugins, and source preflight.

This is planning evidence, not rendered evidence. It does not judge overflow, contrast, animation quality, media readiness, or runtime component behavior.

Resolve “this slide”

While npm run dev is running:

npm exec -- drever current --json

The command resolves the most recently updated open audience or speaker window to its source path, surface, exact route, slide identity, zero-based index, and sparse Step. The snapshot is local and ephemeral; it disappears when interactive windows close or the dev server stops.

Optional read-only MCP

{
  "mcpServers": {
    "drever": {
      "command": "npm",
      "args": ["exec", "--", "drever", "mcp", "slides.mdx"]
    }
  }
}

The dependency-free stdio server exposes context, slide listing, exact slide source, preflight, and the optional live position. Every tool is read-only. Agents edit ordinary files through their normal workspace tools so permissions, diffs, checks, and Git rollback remain visible.

Recommended loop

1. Describe the audience, decision, constraints, and desired deliverables in brief.md.
2. Ask the agent to create or revise the presentation.
3. Inspect npm exec -- drever context --json and fix npm run check -- --json diagnostics.
4. Review every changed Step in Audience View and the complete /document surface.
5. Review Speaker View when notes, timing, or focus behavior changed.
6. Build and deliver the static website or PDF from the same verified project.

Ask for outcomes in natural language. Keep the commands available as a transparent, deterministic contract underneath.