# AI

This section contains the guidance that helps AI assistants — and the developers prompting them — read and write **lsFusion** code correctly. The same materials are served to AI tools through the lsFusion MCP server and published here so they can also be read directly. The per-area articles of the Brief and the Rules are requested by name through the `rules` and `brief` parameters of the `lsfusion_get_guidance` tool.

### [Brief](/Brief.md)[​](#brief "Direct link to brief")

A concise map of **lsFusion** elements — properties, actions, forms, and the core operators — written for quick understanding and code generation. It is deliberately compact, and detailed syntax is looked up in the rest of the documentation as needed.

### [Rules](/Rules.md)[​](#rules "Direct link to rules")

The mandatory conventions for writing **lsFusion** code: how to structure modules, declare and name properties and actions, and which common mistakes to avoid. An AI assistant should read and follow these before generating `.lsf` code.

### [MCP server](/MCP_server.md)[​](#mcp-server "Direct link to mcp-server")

How to run an lsFusion application itself as an MCP server (`enableAPI` + HTTPS) so external AI clients such as `claude.ai` can call its tools — including the OAuth `.well-known` discovery caveat for deployments that are not at the domain root.