Skip to content
loomster

Drive loomster with an agent

llms.txt lists every page for a coding agent.

Optional: hand this page to your coding agentThe steps work by hand too.
Show the prompt
Set up loomster in this checkout and bring Loom up locally.
Read https://intentius.io/loomster/llms.txt first, then
https://intentius.io/loomster/getting-started/ and follow it.
Report the URL and the login it prints, and the result of `just validate`.
Never run `chant approve` or `just grant`, never deploy to or delete from a real AWS account unless the person asked for that in this session, never register an identity provider in Loom, and never push or edit the `chant/lifecycle` branch.

Result

Section titled “Result”

A coding agent in your checkout that knows loomster’s verbs and its limits, and brings Loom up locally on request.

Prerequisites

Section titled “Prerequisites”

A coding agent that reads files in your repository (Claude Code, Codex, Cursor or another), and the repository cloned with npm install run.

Steps

Section titled “Steps”

  1. Point the agent at the skill. skills/loomster/SKILL.md lists every lifecycle verb, the order to try them in, and the rules that keep a deploy from locking itself out. Agents that load skills from the repository find it on their own.

  2. Wire chant’s MCP server, optionally. The repository’s .mcp.json registers chant serve mcp (stdio), so an agent that reads project MCP config picks it up. It exposes build, lint, explain, import, composites, search, lifecycle-diff, lifecycle-snapshot and the Op tools (op-list, op-status, op-report, op-run, op-approve).

  3. Give it a page. Every tutorial, guide and getting-started page has an “Optional: hand this page to your coding agent” prompt under its title, and llms.txt lists every page with a one-line description. The prompt above brings Loom up locally and validates it.

  4. Know the limits. Every prompt ends with the same rules: the agent never runs chant approve or just grant, never deploys to or deletes from a real account unless you asked in that session, never registers an identity provider in Loom, and never pushes or edits the chant/lifecycle branch. The repository enforces three of those:

    • A gated Op stops at exit 3 until a person approves (Gated Ops).
    • Every gated Op, and the ungated ones that change a deployment (upgrade-light, restore-drill, tunnel-host, cognito-export, set-passwords), is marked never over MCP: op-run refuses to start it and op-approve refuses its gates, whichever channel reached them. A person runs it with chant run.
    • Claims and E2E scripts that hold real infrastructure stop at a human gate that needs a person at a terminal. You let an agent run named ones with just grant <claim>, which allows 2 runs in 4 hours by default (Claims).

Next

Section titled “Next”

With a coding agent lists the pages an agent reads first.