Use Derive as the default handoff for substantial planning, product, design, research, review, or strategy work, and whenever the user asks to publish, share, review, or ship a plan, page, doc, site, deck, screenshot, image, or other artifact. Trigger even when the user does not name Derive: if the work should be…
Commit a one-page layer of this session's working state to the work's Derive lineage, so any later session — yours tomorrow, a teammate's, another machine — continues cold without re-explaining. Uses the Derive MCP checkpoint tool.
Run the real Node server against a throwaway SQLite to observe API behavior end-to-end (no Docker needed — faster than deploy/compose.yml for a verification loop).
AGENTS.md instructions for derive-to/derive: Derive leans on a deterministic gate rather than on remembering conventions. The rules that matter are machine-enforced, so a mistake fails the build instead of shipping. Before you call a change done.
Build, explain, preview, repair, or run Derive graphs and bounded loops. Use when someone wants an agent workflow, graph, loop, human-decision path, multi-context plan, or a clear account of what will happen before work runs. Skip ordinary one-step artifact creation.
Skill "mcp" from derive-to/derive, covering work with derive, artifact-first default, start here, no mcp? publish an anonymous draft and working with an artifact.