Frontend
Frontend rules and component guidelines from your code
Reads the frontend and emits framework-appropriate rules, component guidelines, layout patterns, and a UI audit - conventions derived from the components that exist, not a generic style guide.
What it does
Generates frontend conventions from the components already in the repository: naming, composition, layout patterns, plus an audit of where the existing UI diverges from them.
Useful mainly as an agent-readable contract - the file an assistant reads before it writes a component, so the code it adds matches the code already there.
What it emits
4 artifacts, every run. This list is generated from Iliad's program manifest, which its CI checks against the generators themselves — it is what the program actually writes, not a description of it.
frontend-rules.mdcomponent-guidelines.mdlayout-patterns.mdui-audit.md
Listing a tool here
Listing is free and permanent, same as the app directory. If your tool can be called by an agent, it belongs here whether it is an MCP server, a REST endpoint, or a single generator buried in a larger toolbox.
Related microapps
MCP
Full MCP server scaffolding - nineteen artifacts
Closer
Ship-ready packaging for sixteen distribution targets
Deploy
Production deploy scaffolding for Docker, Render, Cloudflare
The AXIS Launch daily
One email a day: a listed app, a tool, or a thread from the community, and now and then a note about the other things we make. Unsubscribe in one click.
You get a confirmation email first, and nothing else until you click it. Every issue carries a one-click unsubscribe and our postal address.