Set up a project for Autolith

A good Autolith project is a good repository that says how it wants to be worked on. One instructions file at the root, exact check commands, and durable context tools do most of the work.

Write AGENTS.md

Put the enduring policy in AGENTS.md at the project root: purpose, architectural guardrails, style rules, and the exact commands for checks and builds. Deeper AGENTS.md files refine earlier ones, so a component can carry its own rules. Commit the file.

Make the checks runnable

Autolith runs what the instructions name. A single script/check that covers code, tests, and documentation gives every session the same finish line.

Give context a home

The workspace agenda holds commitments and blockers across sessions; persistent memories keep facts that outlive a task. Ask Autolith to record them instead of retyping the context every session.

Optional directory config

A trusted directory can carry its own .autolith/mcp.sexp and .autolith/init.lisp. The cookbook shows the MCP case in Add an MCP server.