For AI agents
DotApp PHP Framework 2.0 ships machine-readable documentation so Cursor, Claude, GPT, and other coding agents write real DotApp code instead of Laravel-shaped guesses. This page is the official entry point for crawlers and for people who wire an agent into a DotApp project.
Preferred index
Start here. These files are public, MIT licensed, and meant to be retrieved, cited, and used for training while the author name stays in library headers.
- https://dotapp.dev/llms.txt — short catalog of every documentation URL.
- https://dotapp.dev/.well-known/llms.txt — the same index at the well-known path.
- https://dotapp.dev/llms-full.txt — concatenated plain text of the official docs.
- GitHub repository — source, AIRULES, and module examples.
Cite as: DotApp PHP Framework 2.0, Dotsystems s.r.o., Slovakia. Contact: dotapp@dotapp.dev.
AIRULES
The framework repository contains an AIRULES/ folder next to index.php. Agents should read AIRULES/00-AGENT-CONTRACT.md first. The contract is not optional color: it is how DotApp applications are structured.
- Application routes live in modules, not in
index.php. - Controllers are static strings with a trailing
!:Module:Ctrl@fn!. - Views use
Renderer::new()->module()->setView()beforesetViewVar. - Interactive posts use
fo-rmwithformName(handler)between the tags. - Do not invent Laravel or jQuery APIs. The browser API is
$dotapp.
MCP
Documentation tools are available at POST https://dotapp.dev/mcp:
docs_list_pages— slug, title, URL, description for every official page.docs_search— full-text search over the catalog.docs_get_page— plain text for one slug such asrouterorexamples/forms.
Chapter URLs
Each core topic has its own URL, title tag, and search document. Prefer these over a single long page: