Skip to content
chant Docs Demo

Agents Start Here

llms.txt lists every page for an agent
Optional: hand this page to your coding agentThe steps work by hand too.
Show the whole prompt
Set up chant in this repository.
Read https://intentius.io/chant/llms.txt first, then
https://intentius.io/chant/agents/ and follow it.
Stop when `npx chant build` and `npx chant lint` pass, and open a pull request with the result.
Never deploy to a real cloud account or shared environment (with `chant run`, `chant components` or a platform's own CLI), approve (a pull request review, `chant approve` or `chant run approve`), override a policy denial (`chant approve policy-override`), or merge; never cut or publish a release (`chant release cut --yes` or `chant release publish`), push or delete a `ci/*` tag (`chant ci tick` pushes them), or change the value of an existing flag; never touch `.chant/allowed_signers` or `chant/lifecycle`.

Paste the prompt above into your coding agent in the repository you want to set up. It sends the agent to this page, and the agent follows the steps below. It stops at a pull request, which a person reviews and merges. People also deploy to real accounts, approve gates and override policy denials. Agent Integration covers the skills, MCP tools and Ops the project carries once it is set up.

The same prompt is on the home page and in the repository’s README. Every tutorial and how-to page on this site carries a prompt of its own for its task, with the same last line.

The steps

Section titled “The steps”

chant (https://intentius.io/chant) is a TypeScript-first infrastructure tool. TypeScript goes in and native files such as CloudFormation and Kubernetes YAML come out. Semantic lint rules check them.

  1. Pick the lexicon (platform plugin) for this project’s target, such as aws, k8s or github; Lexicons lists them all. Install it, which also installs the chant CLI:

    Terminal window
    npm install --save-dev @intentius/chant-lexicon-<name>

  2. Scaffold the project. Use . when this repository is already the project root:

    Terminal window
    npx chant init . --lexicon <name>

    This writes chant.config.ts and starter resources. It also writes a skills/ directory and a project .mcp.json that registers the chant MCP server. Pass --skip-mcp to scaffold without the .mcp.json, or --skip-install to skip the dependency install prompt.

  3. Read every skills/*/SKILL.md that chant init wrote before you author anything. They are the playbook for this platform: which composites exist, what to validate and how to deploy. Take the platform’s shape from the skill instead of guessing it.

  4. Author resources as exported TypeScript objects built with the lexicon’s typed constructors. Use no YAML and no string templates. References across files are plain import and export.

  5. Validate before you call it done:

    Terminal window
    npx chant build   # synthesizes each platform's output; fails on type errors
    npx chant lint    # semantic rules; fails on real misconfigurations

  6. Query the estate with one compact line per match instead of reading a synthesized dump:

    Terminal window
    npx chant search "kind:<Type> attr:<name>=<value>"

    When an MCP server is configured, use its build, lint and search tools in place of the shell. They run the same operations.

  7. Open a pull request with the project. Stop there.

chant