HERON for AI agents

Opens a page file, sees which sections the theme expects and writes the text for each of them. You talk about your business in your own words; the agent turns it into finished pages.

Copies a page of the right kind, saves it under a new name and fills it in. On the next build the new file becomes a page of the site.

Every page starts with a search block: title, heading, description. The agent fills them in every language and keeps them within length.

Phones, prices, addresses and names come from you. When they are missing, the field stays empty and the agent gives you a list.

For a page that exists but has demo text.

This is a HERON site. Use the heron-content skill.
Fill the page [about.md] in the folder of the main language with text about [our clinic: who we are, since when, what we do]. Keep the sections the page already has. Fill title, h1 and description. Translate the page into every language of the site.
Never invent phones, prices, addresses or names: leave them empty and list them for me.
Done when: heron build . --env prod --strict passes.

For a new service, article or project.

This is a HERON site. Use the heron-content skill.
Add a page about [teeth whitening] next to the other service pages: copy one of them, give the file a new name, write the text for every section, fill title, h1 and description, translate it into every language of the site.
Do not change the theme or site.yaml. Never invent prices or names: list what you need from me.
Done when: heron build . --env prod --strict passes.

For a language you added in the configurator.

This is a HERON site. Use the heron-content skill.
Translate every page of the main language into a new language folder [de] inside content/, with the same file names. Write natural text, not word for word. Fill title, h1 and description in the new language.
Done when: heron build . --env prod --strict passes.

Works with Claude Code, Codex and other agents that read skills. Run it once in the site folder; the agent picks the right skill by itself when you give it a task.

npx skills add FMSTM/HERON

Agents without skills get the same rules from HERON itself. The docs come from the HERON image, so they always match the version that builds your site.

heron docs --export .heron-docs && ls .heron-docs

Everything an agent needs is also written here, in plain words. Give the agent a link, or read it yourself to know what to expect.

Works in your terminal: writes the pages, runs the build, fixes what it reports. You see every file it changes and can undo any step.

Turns a mockup or a description into a theme. It works on the look of the site, not on its texts.

Works in a branch and opens a pull request that GitHub checks. You read the changes on GitHub and press Merge when you are happy.

Anything that can read a file and run a command can work with HERON. The rules are plain text, not code.

Writes and translates pages, fills the search settings. This is the role you will use most: day-to-day work on a site is text.

Builds the theme: templates, blocks, styles, light and dark. A theme is made once and then serves every page.

Plans pages, addresses, page types and languages before the work starts. Like a floor plan before building a house.

Makes the strict build pass, packs the image and publishes it. The last step before visitors see anything.