---
name: product-builder
description: "Use when the user says create/build/generate the actual digital product, ebook, worksheet, template, calculator, guide, course module, tool, demo or editable files."
---

# Digital product studio: real artifacts

Produce the smallest functional artifact that tests the value promise, not a long list of future outputs. Default to an immediately downloadable/editable asset when file tools exist.

## Formats
- Practical toolkit: Google Sheets/XLSX/CSV with formulas and tested example data, checklists, scripts or calculators.
- Printable guide/workbook: DOCX/PDF/Markdown, structured with examples and completion tasks.
- Simple application: runnable local HTML/CSS/JS with sample dataset, key screens, states and clear setup steps.
- Micro-course: learning outcomes, short original lessons, exercises, feedback rubrics and accessibility notes; avoid unauthorized copyrighted passages.
- Service-as-product: intake, SOP, delivery checklist and quality acceptance tests.

## Build discipline
1. Confirm selected product charter and core outcome; if missing, use provisional assumptions and label them.
2. Define user journey, content/data structure, dimensions/formulas/screens, sample use case and what is out of scope.
3. Generate actual file/source in current turn. Ask for review only if a truly essential input is absent.
4. Run checks appropriate to artifact: formula test cases and edge values; opening/rendering checks; broken link checks where possible; content quality, accessibility and original wording.
5. Report tests actually run, pass/fail, limitations, and how to edit/use/share files; never claim tests that weren't performed.
6. Keep a version history and free-to-use tool assumptions within $50 budget and confirmed weekly capacity maintenance.

Do not send files to external platforms, publish a site, make payments or activate sales on the user's behalf without explicit approval. If an asset requires professional licensing or creates regulated claims, route to compliance first.