From a prompt to filled pages

Content with Claude Code

Q: Claude Code cannot run heron. What now?

Set up the heron command once, as on Get started , and start Claude Code from the same terminal. Other ways to get the command, without Docker, are on Get started .

Claude Code works in your terminal: it reads files, writes them and runs commands. In a HERON site it does the content: writes and translates the pages, fills the search settings and runs the build to check its work. You describe what the pages should say, and you get filled files that build without errors.

Claude Code does not change the look or the structure of the site. The HERON skill lets it write only to the content folders.

Set up in three steps

1
Open a site folder

Create a new one with heron new my-site -y, or use the folder of an existing site.
Get started
2
Install the HERON skills

npx skills add FMSTM/HERON adds the skills Claude Code loads when the task needs them.
About the skills
3
Start Claude Code in the folder

Run claude in the site folder, so it works with your files and can run heron there.

Copy the prompt

Replace the text in square brackets and paste the prompt into Claude Code.

This is a HERON site. Use the heron-content skill.
Task: [write the pages of a family dental clinic in Vienna: home, three services, prices, about, contacts; English and Russian].
Work only in content/, media/ and data/. Keep the sections each page already has; for a new page copy a page of the same kind and save it under a new name. Fill title, h1 and description on every page.
Never invent phones, prices, addresses or names: leave them empty and list them for me.
Done when: heron build . --env prod --strict passes. Commit after each page.

Commits

You review each page as a small change, not the whole site at once.

Facts

At the end you get a list of what the agent needs from you.

What Claude Code does

Reads the structure

Looks at the pages HERON created: which files exist, which sections each page has, how they show on the site. It reads before it writes, the same way you would open a page before editing it.

Why: The theme draws each section in its place. The agent writes text for the places that exist.
What it looks at: content/ for pages (one folder per language), site.yaml for languages and the domain, theme/theme.yaml for which sections each page type expects.
What it does not change: The order of sections and their labels, the theme, scripts and .github/.
Read: How a page is written

Writes the pages

Fills each section with your text: lists, steps, questions and answers, tables. The form of each block stays the same, so the theme draws it as before.

New page: Copies a page of the same kind, saves it under a new name and fills it in.
You get: Filled page files in content/, in every language of the site.
Your voice: Give it two or three texts you like, and it writes in that tone.
Photos: Put them into media/; the agent inserts them into the pages and writes a description for each.
Forms: How text becomes cards, steps and tables

Fills the required fields

Title for search results, heading on the page, description up to 155 characters, in every language. The fields people forget most often, and the ones search engines read first.

Why: These lines decide how the page looks in search and in AI answers.
Example: title «Teeth whitening in Vienna: prices and how it works», h1 «Teeth whitening», a description that says what the reader gets.
Read: SEO and languages

Builds and checks

Runs the strict build, reads the report and fixes every line that belongs to its files. The work is finished only when the build passes.

You get: Pages that build, and a list of missing facts.
If the error is in the theme: The agent does not fix it; it tells you which file and what is wrong.
The command: heron build . --env prod --strict: the same check GitHub runs before publishing.
Preview: It can start heron serve . so you look at the pages in the browser before you accept them.

What it does not touch

The theme

theme/ is closed: a new look is a task for the designer role. A theme with Claude Design

A theme with Claude Design

The structure

The menu, languages, domain and page types in site.yaml change only when you ask for it.

Scripts and publishing

scripts/ and .github/ stay as they are.

Check the result yourself

The first command shows the site at localhost:8000, the second is the same check Claude Code used.

heron serve .

heron build . --env prod --strict && ls dist

When the build passes, publish the finished site the way you chose: store and publish. With git, every later change from Claude Code is built into a fresh image after a push.

Questions

Do I need to know how to code?

No. You describe the pages and check the result in the browser. Claude Code works with the files and the commands.

Claude Code cannot run heron. What now?

Set up the heron command once, as on Get started, and start Claude Code from the same terminal. Other ways to get the command, without Docker, are on Get started.

Can it move the texts of my old site?

Yes. Give it the old pages or their addresses. It puts the texts into HERON pages and lists the old addresses in each page, so HERON writes real 301 redirects.

Can it change the design too?

Not in the content role. Give the design to the designer role as a separate task: A theme with Claude Design. The rules of every role are in the docs.