Generators catalogue
Every fresh install seeds these eleven Generator rows at boot (seedGenerators() in
apps/api/src/studio/generators/index.ts), idempotently — restarting the API refreshes their
definitions but never duplicates them. Catalogue order below is display order in the Studio.
See Generators for what a Generator actually is (schema, templating,
validation) and how a run differs from a free-text brief.
| Generator | Outputs | Pipeline (role → role → …) |
|---|---|---|
| Blog post | markdown | researcher → strategist → writer → editor |
| Research report | markdown, docx | researcher → researcher → analyst → publisher |
| Landing page | react-app | copywriter → designer → engineer → reviewer |
| Full-stack app | fullstack-app | product → architect → engineer → engineer → writer |
| Business plan | docx, markdown | researcher → analyst → analyst → writer → publisher |
| Data analysis | markdown, image, data | data-scientist → data-scientist → analyst |
| Logo and image set | image, markdown | art-director → illustrator → art-director |
| 3D scene | html, scene3d | scene-designer → engineer |
| Email campaign | markdown | researcher → writer → marketer → editor → courier |
| Widget maker | html | designer → engineer |
| Agent crew & pipeline | markdown | researcher → analyst → lead → lead → writer |
The last one is different in kind from the other ten: instead of producing something for you to read or ship, it produces Novaterra itself — agents that exist in your world after the run, and the generator that puts them to work.
Every one of these is validated at API boot (assertSeedGeneratorsValid()) against the real
skill catalogue, the contract, and a set of structural rules — see
Generators — so what’s documented here is
guaranteed to still match what actually runs.