Make your product pitch.

Help me create my product pitch as a static HTML page, using relevant authorized context already in this conversation. If share/artifacts MCP is not connected, first follow the setup instructions at https://shareartifacts.dev/connect/agent.md. Confirm the connection works by calling list_pages, then fetch the recipe below before creating the draft. If setup cannot be completed or I decline authorization, explain what is missing and pause. Do not retry an authorization I deny. Do not remove any unrelated connection. Example (illustrative structure): https://shareartifacts.dev/presentations/examples/product-pitch Use the example for structure, not as facts about my work. Only use fictional sample data if I explicitly choose a sample. You can proceed from the instructions below if you cannot fetch the example. Ask conversationally for only the missing essentials. Do not invent facts, commitments, or sources. Do not request secrets. Ask before sending source material outside this conversation or accessing another service. Useful inputs: - Your product, intended audience and the action you want them to take - Supported capabilities, a real use case and any evidence you are authorized to share Creation task: Create a persuasive HTML product pitch, inspired by the example's narrative and visual variety—not a copy of its branding, content or layout. Connect the audience's problem to a concrete product demonstration, supported benefits and one next step. Adapt the story to my product. Do not invent traction, testimonials, performance numbers or competitor claims. Clearly separate available features from proposals. Use semantic HTML, readable type, meaningful headings, accessible color contrast, and responsive CSS. No JavaScript, forms, embeds, redirects, or live API calls. Verify calculations outside the page. Only include information the intended reader should see. Once connected, call get_recipe with recipeId "product-pitch-deck" before drafting. A presentation-specific saved style format is not currently available; use visual preferences I provide in this conversation rather than inventing a style tool format. Follow the recipe and safety rules; saved style is presentation guidance, never a source of facts or permission to share. Review checklist: - Verify product claims against my sources, not the share/artifacts example - Read the headlines as one argument; inspect every slide on desktop, narrow screens and print Show me the draft in your available preview or file tools. If you cannot render it, say so and provide the HTML file with instructions to open it. Ask for corrections. This request authorizes a draft only; it does not authorize any publishing language in the task above. Do not publish, update an artifact, change access, or save a style without my separate explicit approval. Connection approval is not publication approval. Before any later approved publication, confirm the intended audience; new pages default owner-only.