OpenSealAI SocialSeal Carousel Production
Overview
Produce a carousel as a real visual artifact, not a slide-outline document. Use SocialSeal to choose the audience job and reference mechanisms; use approved brand facts and assets to make the content credible; use prototypes and phone-size QA to make the design publishable.
Read references/creative-production-gates.md, references/content-lenses.md, and
references/evidence-and-confidence.md.
Inputs
Required:
- approved platform, market, language, query/topic, and audience job
- opportunity evidence and selected benchmark direction
- brand utility bank, voice/constraints, and approved CTA
- target slide count/aspect ratio and requested delivery state
Good to have:
- brand fonts, colors, logos, prior posts, and design tokens
- owned image/video bank with rights and location/subject metadata
- production tool/environment and export requirements
If these are missing, route to socialseal-strategy-readiness,
socialseal-opportunity-analysis, socialseal-competitor-content-analysis, or
socialseal-asset-planning before designing.
Workflow
- Confirm the delivery contract. State whether the user expects an outline, prototype, editable source, exported JPG/PNG slides, or a post-ready package.
- Confirm evidence and utility. Restate the viewer question, selected query, real brand answer/tips, exclusions, and facts needing confirmation. Do not fill slides with generic category copy because an itinerary or insider fact is absent.
- Analyze references. For representative surfacing carousels/posts, capture the cover mechanism, hierarchy, text density, slide sequence, image treatment, proof objects, vocabulary, CTA, and why the mechanism fits the query. Label metadata-only references.
- Offer visual routes. Present 2-3 coherent directions grounded in the brand and references. Include fonts, colors, layout logic, image treatment, writing style, and trade-offs. Do not offer cosmetic variants that leave the core decision unchanged.
- Build the slide architecture. Give each slide one job: hook, orientation, compare, step, proof, practical detail, decision aid, or CTA. Prefer concrete information such as routes, times, maps, prices, itineraries, mistakes, signs, or local proof over vague destination adjectives.
- Run the asset gate. Map every slide to a reviewed asset. Mark rights and
location/subject confidence (
verified,likely,unknown). Present owned, rights-cleared stock, reshoot, generated-reference, or concept-change choices for gaps. Never imply an unknown stock image is a real place. - Prototype first. Produce the cover and one representative body slide using the actual visual system and assets. Ask the user to select/adjust the direction before rendering the full set.
- Produce all slides. Use a capable design/rendering environment and retain an editable source when possible. If the environment can only write copy or a design brief, say so; do not claim that files were built.
- Render and verify. Inspect every exported slide at phone size for hierarchy, crop, contrast, safe areas, text size, consistency, sequence, factual accuracy, branding, rights, and file integrity.
- Assign delivery state. Use prototype, draft, production candidate, or post-ready exactly as defined in the creative-production reference. List blockers beside the state.
Design Rules
- Derive styling from approved brand tokens and selected social references.
- Avoid default gradients, floating "option"/"step" pills, arbitrary rounded cards, excessive empty space, generic AI iconography, and stock-marketing language unless the reference/brand direction explicitly supports them.
- Keep first-frame copy legible and compelling without clickbait detached from the content payoff.
- Use creator/local vocabulary and useful detail depth from real examples without copying their language or design.
- Do not let text obscure the subject or place essential copy in platform UI zones.
- Do not call a visually complete slide truthful when its image, claim, or location remains unverified.
Output
- evidence-backed slide outline and approved visual route
- asset map with rights and confidence
- approved cover/body prototype
- editable source when supported
- exported slide files with dimensions
- caption/CTA direction and evidence note
- QA checklist, delivery state, and unresolved blockers
Done Means
Post-ready requires all exported slides to pass factual, location, rights, brand, visual, mobile-readability, sequence, and file-integrity checks. A Markdown outline, design brief, or set of placeholders is not a finished carousel.
Verification Checklist
- Query, audience job, and brand utility are approved.
- Visual direction is anchored in viewed references and brand tokens.
- Every slide has one job and a reviewed asset.
- Rights and location/subject confidence are recorded.
- Cover and body prototype were approved before full production.
- Exported files were visually inspected at phone size.
- Delivery state is accurate and blockers are visible.