Story-Driven Invitation Poster

Problem

Invitation posters often face two conflicts: templates erase real details such as people, pets, and home spaces, while raw photo stacks let decorative elements crowd out the title, date, venue, and RSVP. This skill targets birthday, housewarming, wedding, anniversary, and similar invitation scenarios, turning the user's own photos and memories into a coherent hero visual and then composing a readable poster.

Core Capabilities and Key Steps

• API key handling: It reuses a validated mew.design API key from the current conversation, asking again only when the key is missing, invalid, rejected, or explicitly replaced.
• Input collection: It gathers event type, title, subtitle, date, time, venue, RSVP line, tone, and optional style, preferring public image URLs.
• Stage 1: It calls the official image-process API to process key photos into an invitation-grade hero visual while preserving people, pets, spaces, and emotional context, without adding poster text.
• Stage 2: It calls design-generate to compose the final poster using the transformed visual as assetImages, with title, event facts, text-safe areas, and layout hierarchy.
• Style matching: It can follow an explicit style or auto-select presets such as classic-movie-poster, modern-minimalist, creative-illustrative, vintage-retro, and scrapbook-collage.

Boundaries

• Image URL requirement: The downstream APIs need server-accessible image URLs; local attachments are not treated as directly usable assets.
• Privacy confirmation: If no usable URL exists, it explains the privacy tradeoff of temporary third-party file hosting and asks for consent before uploading.
• Copy length: Long blessings or invitation text are condensed into a short headline, supporting line, and essential details rather than forced into the layout.
• Output scope: The result is a legible, personal invitation poster, not mass marketing collateral or a full brand identity system.