Agent Recipes

This section is aimed at developers who are configuring an AI coding assistant (Claude Code, Cursor, Copilot, or similar) to automate Reoclo integration tasks. Each recipe is a structured, self-contained document that an agent can follow verbatim.

Machine-readable index

A plain-text listing of all recipes with one-line summaries is available at /agents/llms.txt. This file follows a robots.txt-style convention and is suitable for consumption by agent tooling that pre-fetches context before running a recipe.

Available recipes

Recipe	Use when
Inject Secrets Manager values into a CI workflow	A workflow step needs secrets stored in Reoclo. You need to swap per-secret CI variables for one automation key and `reoclo run`.
Enhance an existing GitHub workflow with Reoclo route sync	The repo already has a workflow that runs `docker compose up` or `docker run`. You need to add the `reoclo/deploy-sync@v2` step.
Set up External Deployment from scratch	The repo has no Reoclo integration at all. You need to walk the user through generating an API key and writing a new workflow.
Prepare a deploy folder on the server	You are wiring `reoclo/run@v2` to run `docker compose up` and need to pick a folder, set the right group ownership, and avoid the chown-after-every-deploy trap.
Diagnose a deployment failure	A sync step has errored or returned unexpected statuses. You need to map the error to a root cause and fix.
Interpret a drift warning	A sync result contains `status: drift_recovered`. You need to explain what it means.

Using these recipes

Agents should:

Fetch the recipe page for the relevant task before taking any action.
Follow the Detection section to confirm the recipe applies to the current codebase.
Apply the The change section as a literal diff or set of edits.
Run the commands in the Verification section to confirm the result.
Stop after verification. Do not apply changes from other recipes unless the user explicitly requests it.