Problem
The preview_creative task reference page does not explicitly state that the task renders an existing creative manifest into viewable output — it does not generate or modify the manifest itself. Implementers reading the page can reasonably infer that supplying a manifest with assets (e.g. hero_image, headline) triggers generation, conflating this task with build_creative.
The boundary between preview_creative (render) and build_creative (generate) is the central distinction between these two tasks, and it is not stated anywhere on either page.
Proposed fix
Add one explicit sentence at the top of both task pages:
preview_creative:
preview_creative renders an existing creative manifest into viewable output. It does not generate or modify the manifest itself — use build_creative for that.
build_creative:
build_creative generates a creative manifest from a message or input assets. To render a visual preview of the resulting manifest, pass it to preview_creative.
Affected files
docs/creative/task-reference/preview_creative.mdxdocs/creative/task-reference/build_creative.mdx
Problem
The
preview_creativetask reference page does not explicitly state that the task renders an existing creative manifest into viewable output — it does not generate or modify the manifest itself. Implementers reading the page can reasonably infer that supplying a manifest with assets (e.g.hero_image,headline) triggers generation, conflating this task withbuild_creative.The boundary between
preview_creative(render) andbuild_creative(generate) is the central distinction between these two tasks, and it is not stated anywhere on either page.Proposed fix
Add one explicit sentence at the top of both task pages:
preview_creative:build_creative:Affected files
docs/creative/task-reference/preview_creative.mdxdocs/creative/task-reference/build_creative.mdx