zeyn
llms.txt8 starsChanged 10 days agoApache-2.0View on GitHub
Rust web framework for data heavy applications. Screens are rendered on the server; AI agents write the app code and people review it.
The file
Files
# Zeyn Framework > Rust web framework for data heavy applications. Screens are rendered on the server; AI agents write the app code and people review it. - [Building apps with Zeyn](skills/zeyn/SKILL.md): where to read, the rules, the language in short, common mistakes, verification - [Working on Zeyn itself](AGENTS.md): repository map, commands and rules for contributors - [App rules and framework index](crates/zeyn-cli/templates/AGENTS.md.tmpl): macros, types, screens, actions, recipes in one page - [Language guide](examples/docs/pages/): entities, actions, screens, forms, effects, texts, DataGrid and components - [Runtime protocol](docs/runtime-protocol.md): how the browser runtime talks to the server - [Theming](docs/theming.md): design tokens - MCP: run `zeyn mcp` in a project for docs, checks and tests as tools
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.