Agent skills
Teach any coding agent to write valid .lolo, with the same catalog and checks the compiler uses.
Any coding agent can write Orb programs. It needs the language's vocabulary, a way to see what is valid at a cursor, and a checker it cannot argue with. All three ship in the CLI.
The catalog
orb signatures --out signatures.lolosignatures.lolo is the typed catalog of every operator, pattern, struct and installed behavior contract, written in .lolo itself. Give it to the agent as reference: it is what the compiler checks against, so it is always current.
Completion
orb complete app.lolo --offset 512orb complete answers what may be written at a position: keywords, effect operators, pattern tags and props, import paths and the typed config keys of a referenced trait. It never invents a name and works on unfinished code.
The checker
orb validate app.lolo --json --deny-warningsEvery finding carries a code, a path, a message, a suggestion and a source span. Agents loop on it until the program reports 0 errors and 0 warnings. orb verify --json adds the behavioural checks.
A working loop
- Read
signatures.loloand the language guide. - Prefer composing a standard behavior over writing a state machine.
- Write the program, then run
orb validate --json --deny-warnings. - Fix every finding at its source position and validate again.
- Run
orb verifybefore calling it done.
The built-in agent (orb with no command) follows exactly this loop.
Orb
The language where the rule is the program.