5
く
ネコミミ少女の可愛さ炸裂！
くまくん
character: mio_\(pixai\). A medium shot, eye-level square composition designed as an album cover, featuring Mio centered against a minimalist backdrop. She has short, voluminous white hair with a heart-shaped strand on top and purple highlights on the underside, complemented by white cat ears and large, shimmering purple eyes with white eyelashes. She wears a navy blue sailor-style crop top with a white collar and a blue ribbon with a heart brooch, paired with white high-waisted shorts with navy blue stripes, a black beret, and a black choker. Her hands, clad in white gloves with black bows, are resting gently on her lap. The background consists of soft pastel colors and clean geometric lines with a flat color aesthetic, devoid of complex textures. The overall atmosphere is gentle and poetic, utilizing a high-key palette and a simplified, clean visual style reminiscent of a modern slice-of-life art piece.
매개변수 표시
- 원본 프롬프트
- The user wants me to take the watercolor-style visual and design it as an album cover for PixAI's character Mio. Looking at the previous turn, the watercolor image has mediaId `746019196611257668`. I should reuse this for the album cover composition. For album cover design: - Genre slice-of-life (matches the watercolor mood) or maybe dark-fantasy or something more atmospheric... actually for a personal/elegant album cover, slice-of-life fits well. Or maybe just leave it as slice-of-life since the mood is gentle. - Artifact: album-cover - The user specifically said "アルバムカバー" (album cover) Standard album cover dimensions are square (1:1). Let me follow the workflow: 1. Call getCompositionGuidelines first 2. Use existing watercolor image (no need to regenerate) 3. Call compositionGenerate Since this is essentially transforming an existing concept into a new artifact type, I should first check the guidelines, then compose. No need to regenerate the image since the watercolor illustration already exists and is perfect for an album cover. Let me also think about the design - album covers typically have: - Artist/title name prominently - Sometimes a subtitle - Strong visual focus on the artwork - Clean typography - Less cluttered than posters/flyers For Mio's album cover - since she's the PixAI mascot, this is a fun concept. Watercolor style suits a poetic, atmospheric album cover well. I should pass the htmlContentId from the previous birthday visual as templateId to preserve some design continuity... actually wait, an album cover is a different artifact type with different proportions. Let me think about whether using the templateId makes sense. The templateId reuse is for "series consistency" within the same conversation - it preserves palette, font, and textbox style across scenes. The birthday visual template was a specific layout structure. An album cover has its own structure requirements (typically square, with the title prominent). Actually, per the workflow: "All other artifacts are standalone — call compositionGenerate directly with the character images, no template step needed." Hmm wait, that says "no template step needed". But the birthday visual was a successful composition with htmlContentId. Let me re-read the rules. The exception for templateId is specifically about visual-novel-screen where maintaining consistency across scenes is important. For other artifacts, each is standalone. But there's also: "When passing a templateId (modifying an existing composition): write the prompt as an explicit delta". This implies templateId can be used for any artifact type modification. For an album cover transformation from the birthday visual, since they're different artifact types with different structures, I think it's better to NOT use the templateId and create a fresh album cover design. The birthday visual had tall portrait layout; an album cover is square. They have different structural needs. Let me proceed: 1. getCompositionGuidelines for album-cover 2. compositionGenerate using the watercolor image and a fresh album cover design Let me start by getting the guidelines.
- 모드
- lite
- 스타일
- 미니멀 플랫
- 크기
- 1152 x 1536
스타일: 미니멀 플랫
프롬프트 도우미
