Create an editable HTML/CSS composition with selectable text and a print stylesheet; treat any raster illustration as a separate local asset for [PROJECT] and [AUDIENCE]. The task is: Product Announcement Card.

## Required content and structure

Create a launch visual with one product message, a supplied product image and an availability note.

Use [APPROVED_CONTENT] as the source of names, dates, figures, claims and destinations. List missing inputs before substituting anything. If a demonstration is needed, label its content as fictional. Do not invent customer quotes, rankings, partner logos or product capabilities.

## Design direction

Use [BRAND_RULES] and the design system already selected in the project. If no system is supplied, start with this direction: warm ivory, expressive black typography and a vivid coral accent; original geometric visual motif. Keep type, spacing and color roles consistent. Prioritize the task over decorative elements and avoid a generic collection of unrelated cards.

## Content preparation

Prepare one approved announcement message, product image, availability statement and action destination. Choose the target placement and its required dimensions.

## Layout and behavior

Give the product message priority, supported by one clear image and a concise availability note. Keep secondary details out of the main visual rather than shrinking all text.

## Task-specific acceptance check

- Keep availability and claims aligned with the approved announcement.
- Inspect the card at feed size.
- Confirm that the pictured feature is actually available in the announced release and that planned access is not presented as an immediate launch.

## Implementation and review

Keep text editable. Use semantic structure, descriptive controls, visible keyboard focus and appropriate empty/error states. Check narrow and wide layouts. Respect reduced-motion preferences. Preserve any existing project framework and dependencies; do not silently replace the stack. Return the editable files and explain any incomplete behavior or unsupported inputs. Review this specific task before proposing extra features.

Keep exact text and required credits as live text. Ask for the intended dimensions when they are missing. Do not invent a functional QR code, barcode, signature or official seal.

## Reference attachment and reconstruction goal

Attach reference.webp from this prompt’s download bundle alongside this prompt in OpenDesign. Build an editable result with a similar composition and hierarchy; do not embed the whole reference image as the finished interface. Preserve approved project content and brand rules if they conflict with fictional sample labels. If the image is missing or unreadable, ask for it instead of claiming visual fidelity.

## Reference composition and content

Use the attached reference.webp as the visual reference for Product Announcement Card. Before building, identify the major regions from top to bottom, their relative widths and heights, alignment, spacing, typography hierarchy, surface colors, borders, imagery and repeated components. Preserve those relationships rather than substituting a generic template. Required task content: Create a launch visual with one product message, a supplied product image and an availability note. Use the following task-specific layout guidance when translating the image into editable elements: Give the product message priority, supported by one clear image and a concise availability note. Keep secondary details out of the main visual rather than shrinking all text.

## Visual direction from the example brief

warm ivory, expressive black typography and a vivid coral accent; original geometric visual motif.

## Output and editability

Recreate the finished graphic as editable text, shapes and image layers. The reference is a composition, not an editor interface; do not add navigation, forms or dashboard widgets that are absent from it. Give the product message priority, supported by one clear image and a concise availability note. Keep secondary details out of the main visual rather than shrinking all text. Confirm intended dimensions and preserve text hierarchy when adapting the artwork. Keep availability and claims aligned with the approved announcement.

## Visual comparison and delivery

1. Compare the result with the attached image at matching proportions. Review major region placement, relative image sizes, line breaks, spacing, typography hierarchy, contrast, active states and content density before polishing decorative details.
2. Then test the narrow layout without squeezing desktop text into tiny labels.
3. Keep logos, photos and icons as separate assets and all meaningful labels editable. List any unavailable fonts/assets and any intentional departures. Return the working files plus a concise account of implemented behavior and remaining integrations; do not promise a pixel-identical result from the prompt alone.