Make your creative brief.

Help me create my creative brief 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 (complete fictional sample): https://shareartifacts.dev/examples/creative-brief 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: - Approved objective and audience evidence, including what remains an assumption. - The single desired audience action, approved claims and required wording. - Deliverables, channels, dimensions or length constraints and confirmed deadlines. - References you may share, what each reference illustrates, and the approval owner. Creation task: Create a creative brief as static HTML from my authorized audience evidence, objective, claims and delivery constraints. Lead with the audience's desired action. Separate evidence from audience hypotheses, approved claims from proposed copy, and mandatory requirements from inspiration. Map each deliverable and channel to its context, essential message, next action and supplied constraints. Do not invent research, testimonials, performance guarantees, budgets or deadlines. Describe what shared references illustrate without copying them. Ask only for missing essentials from existing authorized context; use my saved artifact style if available. No scripts, forms, campaign scheduling or analytics claims. Show me a draft and open decisions. Do not publish, launch a campaign or change access without separate explicit approval. 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 "visual-report" and get_artifact_style with format "report" before drafting. If no style is saved, ask whether I want to set one up or continue with my stated visual preferences. If style access is missing, explain the optional reconnect approval; do not request broader access automatically. Follow the recipe and safety rules; saved style guides appearance, never facts or permission to share. Review checklist: - Does each deliverable support the same supplied communication objective? - Are audience hypotheses, proposed copy and approved claims distinguishable? - Are mandatory wording, channel constraints and reviewer responsibilities preserved? - Do references respect permissions, and are missing deadlines or specifications flagged? 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.