Template Creation Checklist

> Advanced workflow: Use this only if you are refreshing assets for internal demos. Alpha users should stick to the hosted gallery until we announce public template authoring.

Use this checklist whenever exporting a new template or refreshing an existing one. It keeps /templates, docs, and ownership metadata in sync so any agent can repeat the process.

1. Generate / Export Assets

Run the eval scenario (or manual flow) that produces eval-output/.bundle.json.

Example: pnpm eval:autopilot -- --scenario notifications-history

Export the template bundle into templates/apps//:

pnpm template:export --force - Verifies weldr.app.json, weldr.ownership.yaml, bundle.json, template.json, and README.md exist. - Auto-refreshes /api/templates/reload in dev so the gallery picks up new entries immediately.

Template-specific enrichers (if applicable):

- Blog Platform: pnpm tsx scripts/templates/enrich-blog-template.ts --bundle eval-output/blog-platform.bundle.json.

2. Fill Template Metadata

Update templates/apps//template.json with:

• title, description, status, version (use YYYY.MM.DD), generatedAt

• scenarioCommand / exportCommand

• docsLink (points to /docs/demos/)

• Summary counts (entities/pages/workflows/capabilities)

Ensure README.md explains the scenario, bundle source, export timestamp, and any manual steps before demos.

3. Documentation

Create/refresh /docs/demos/.md with:

- Overview + key features - Export/refresh commands - Usage steps inside the app - Demo checklist (ownership guard focus, preview data, etc.)

Update docs/templates/catalog.md:

- Add/refresh the row for (status, capabilities, commands, docs link, asset path). - Keep the table sorted/consistent.

4. UX Verification

• Open /templates, confirm card shows metadata + quick-start commands.

• Apply the template and verify:

- Chat redirects with ?fromTemplate= and shows the “Template ready” banner. - Code panel auto-opens (to reassure users). - Ownership manifest is registered (badges visible without manual edits).

• Run pnpm lint + relevant integration test (e.g., pnpm tsx tests/integration/test-template-apply.ts) if assets changed.

5. Analytics (optional but recommended)

• Ensure app/templates/template-card-actions.tsx (and any other apply entry points) track the event.

• Confirm ChatInterfaceV2 logs template_hydration_ready so we know when templates convert.

Following this checklist keeps new templates consistent and makes it easy for future agents to repeat the cadence. Update the checklist whenever the process changes.