Agent workflows

Start from any coding agent

The public prompt.md is a small bootstrap for an empty, new, or existing 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, then hands control to the version-matched instructions installed inside that project. It does not duplicate the complete authoring contract, inspect framework internals, or silently change an existing Drever version.

Before authoring, it distinguishes a new deck, an explicit replacement, and a focused edit to existing work. New and replacement scopes use Studio when the host can keep a local server alive. Existing edits preserve the approved plan and go directly to the requested change.

The installed kit is also the context boundary. Normal work reads the brief, configuration, MDX, and only the project-owned components or design files it will edit. It does not scan node_modules, Drever source, official design implementations, or example decks as a discovery workflow.

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

Keep AI behavior in the project

Drever is agent-first, not agent-only. It makes AI authoring a versioned project contract instead of hiding the source behind a hosted editor or 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.

Refresh the installed workflows after upgrading:

npm exec -- drever agent sync --target all

The sync command updates only Drever-owned files and managed instruction blocks. It reports a conflict instead of replacing an unmarked, user-owned skill.

The design workflow derives its direction from the subject, audience, venue, source material, and purpose. Official designs are reference studies rather than automatic presets. When a real website is relevant evidence, drever design import <url> creates an editable local starting point without copying the website. See Art direction.

After the content Storyboard is approved, that workflow writes a Scene map for every slide and a Handoff map for every adjacent edge. The maps decide the focal evidence, visual form, typography, color roles, motion owner, continuity geometry, settled endpoint, and reverse behavior before the refined visual source is written. Difficult causal, spatial, quantitative, and comparative ideas therefore get a diagram, chart, artifact, licensed image, or generated conceptual illustration when the host supports it—not a second panel of prose. Related objects normally carry continuity between slides; incompatible geometry uses an explicit local replacement instead of a distorted snapshot.

The first content-complete preview appears before that refinement: the agent writes the approved story, runs one source check, and publishes the stable draft without waiting for optional research or polish. Final review then judges the settled and transition pixels before reading the author's art-direction claims, so a tidy card reveal or a status label beside an unchanged artifact cannot pass as a signature moment.

The review workflow consumes stable source and rendered diagnostics instead of treating prompt rules as proof. See Rendered review for the isolated browser gate and its limits.

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.

Use the context report before reading declarations or dependency source. A narrow public type is a last resort for one concrete diagnostic, not a replacement for the resolved project contract.

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 development server stops.

This keeps natural-language requests such as “make this headline quieter” grounded in one exact presentation state without making a click-to-edit overlay another source of truth.

Add the 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, 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.

MDX edits are reread on each call. Restart the server after changing configuration, Theme, or plugin registration because those contracts are resolved at process startup.

Choose the smallest useful connection

• Use Studio for guided creation, content approval, public work activity, and live feedback.
• Use drever context --json when an agent needs the complete authoring contract.
• Use drever current --json when a request refers to an open slide or Step.
• Use the MCP when a long-lived agent benefits from read-only slide tools.
• Use Rendered review when the project needs browser evidence.

None of these interfaces owns the deck. slides.mdx, brief.md, drever.plan.json, local design files, assets, configuration, and Git remain authoritative.