Create Marketing Kit

Turn verified product truth into a cohesive, reusable campaign kit. Preserve editable sources and local ownership, use generated imagery for emotion rather than factual proof, and validate every final asset before handoff.

Operating contract

• Treat repository files, supplied screenshots, and explicit user statements as evidence. Mark inferences and unresolved gaps.
• Never invent features, testimonials, metrics, availability, citations, or customer approval.
• Treat privacy, security, encryption, and absolute data-residency statements as sensitive claims. Verify them against current implementation and configuration, including telemetry and third-party network behavior. Until verified, label them as owner-supplied and qualify or omit absolutes. Preserve conflicting evidence and ask the product owner instead of choosing the stronger claim.
• Keep generated people and scenes clearly editorial. Use real captures for product proof and real logos for identity.
• Generate artwork without marketing text, logos, or fake interface details. Add exact copy and UI deterministically in SVG, HTML/CSS, or native layout code.
• Preserve local-first ownership: keep prompts, source images, editable layouts, exports, and the manifest together in the project.
• Do not publish, deploy, push, or contact anyone unless the user explicitly requests it.

Workflow

1. Establish product truth

Read the smallest authoritative set: product README, current website, configuration or release notes, and actual screenshots. Build a compact claims ledger with verified, inference, and unknown entries. Stop or narrow the campaign when a central claim is unsupported.