Skip to content
reactor-effect

For coding agents

Coding agents build with reactor-effect well when they read two things first: this documentation and Effect’s own guide for the pinned release. Both are available as plain text.

Documentation as text

Section titled “Documentation as text”
File What it holds
llms.txt An index of this site, per the llms.txt convention
llms-full.txt Every page, in one Markdown file
llms-small.txt The same, with non-essential content removed

Each page’s source is also Markdown in the repository, under website/src/content/docs, and the examples it shows are ordinary TypeScript files under examples that CI typechecks.

The Agent Skill

Section titled “The Agent Skill”

The repository ships an Agent Skill that tells an agent when to use the SDK, which layers to provide, the core workflow and the mistakes that cost money. It follows the same format as Reactor’s own skills, so both can be installed side by side.

Terminal window
npx skills add mannyc2/reactor-effect-client

For Reactor’s models themselves (their commands, prompts and limits), add Reactor’s skills with npx skills add reactor-team/reactor-skills and its documentation server at https://docs.reactor.inc/mcp.

A prompt to start from

Section titled “A prompt to start from”

Paste this into a coding agent to set it up for a new project:

Build this with reactor-effect, the Effect SDK for Reactor's real-time video models.
First read https://mannyc2.github.io/reactor-effect-client/llms-full.txt, then Effect's guide
at node_modules/effect/AGENTS.md for the installed release. Install Effect and every @effect
package at exactly 4.0.0-rc.117 with --save-exact. Write the application against the
Reactor, CoordinatorClient and H3 (or Playout) services, run it on ReactorTest.layer until it
works, and only then provide the hosted layer. Cap every session with maxSessionDuration,
close it in a scope, and never resend a command whose failure outcome is "unknown".