Build-v1-metadata
title: Build v1 product metadata description: How Nullshot resolves product descriptions, cover art, and promo video from your CodeBox files.
Build v1 product metadata
When you run Build version 1.0 (or publish a jam for the first time), Nullshot generates:
- A public product description
- An AI cover image
- An optional promo hover video
These assets should describe your product, not your agent session, deploy logs, or infrastructure fixes.
Resolution order
Nullshot reads your synced CodeBox on the main branch in this order:
nullshot.build.json(machine-readable, highest priority)PRODUCT.md— especially the section titled Build v1 summaryindex.htmlorpublic/index.html—<title>,<meta name="description">, Open Graph tagssrc/index.tsx,src/App.tsx, orapp/page.tsx— visible product copy
Agent chat, deploy transcripts, Wrangler notes, and merge/CI jargon are not used when file-based metadata is available.
nullshot.build.json
| Field | Used for |
| --- | --- |
| name | App title hints for media generation |
| tagline | Short subtitle when description is assembled |
| description | Primary product copy for description, cover, and video |
| category | Tags/category hints for cover and video prompts |
| keywords | Additional tags (merged with category) |
PRODUCT.md
Use a Build v1 summary section for the description Nullshot should show in the confirm step:
Confirm before Build v1
Build v1 is one-shot. Before merging, Nullshot shows the resolved description so you can edit it. Saving there updates your jam description before the default cover image generation runs.
After v1: updating cover media
You cannot re-run Build v1 on the same room. If you change the description later in jam settings, use Regenerate cover so gallery media matches the updated copy. Video covers are a separate paid add-on and must be generated explicitly.
New webapp rooms
New webapp rooms receive starter nullshot.build.json and PRODUCT.md templates if those files are not already present. Replace the placeholder text before your first Build v1.
CLI / repo workflow
If you maintain product copy in a separate repo, sync nullshot.build.json and PRODUCT.md into the jam workspace before Build v1 (for example via jam sync from your CLI-watched directory).