{"name":"LouisianAI Ads Explorer prompt wall","version":"2026-06-14","sourceSkill":"creative-production:ads-explorer","sourcePack":"diverse-image-ad-archetypes","url":"https://louisianai.com/ads.json","sourceArtifact":"outputs/imagegen/louisianai-source-cited-growth-kit-diverse-image-ads/prompts-manifest.json","campaignManifestUrl":"https://louisianai.com/campaign.json","polishManifestUrl":"https://louisianai.com/polish.json","subject":"LouisianAI Source-Cited Growth Kit","subjectKind":"digital-product","artifactMode":"prompt-ready Ads Explorer wall plus six generated first-pass visual references wrapped in deterministic public SVG cards; publish-bound LouisianaAI ad text must still be recomposited deterministically after a direction is selected","objective":"Explore a broad set of paid-social, display, partner, newsletter, OOH, proof, launch, and editorial ad directions for source-grounded LouisianAI distribution.","approvedCopyRule":"Readable ad copy must come from campaign.json copy blocks. Generated imagery is exploratory only and cannot introduce new claims, metrics, logos, endorsements, or public-record language.","claimConstraints":["Do not claim unsupported subscriber, readership, traffic, citation, adoption, ranking, performance, savings, rate-impact, or endorsement metrics.","Preserve source confidence labels, exact public-record language, docket identifiers, and canonical LouisianAI URLs.","Do not invent partner logos, government or utility seals, customer testimonials, ratings, AI-engine screenshots, analytics dashboards, source counts, or docket records.","Use deterministic layout and the polish manifest before publishing any readable ad asset."],"reviewWall":{"localArtifact":"outputs/imagegen/louisianai-source-cited-growth-kit-diverse-image-ads/review-board.html","widgetPayload":"outputs/imagegen/louisianai-source-cited-growth-kit-diverse-image-ads/moodboard-widget-payload.json","runState":"outputs/imagegen/louisianai-source-cited-growth-kit-diverse-image-ads/run-state.json","promptManifest":"outputs/imagegen/louisianai-source-cited-growth-kit-diverse-image-ads/prompts-manifest.json","jobs":"outputs/imagegen/louisianai-source-cited-growth-kit-diverse-image-ads/jobs.jsonl","imagesGenerated":6,"status":"local-partial-review-wall-with-public-reference-svgs","captionsSuppressed":true,"publicReferenceCards":[{"id":"ad-problem-solution-split-screen","sourceFamilyId":"problem-solution-split-screen","title":"Problem-solution Ads Explorer reference","url":"https://louisianai.com/share/cards/ad-problem-solution-split-screen","backgroundPath":"/share/ads/problem-solution-split-screen.jpg","landingUrl":"https://louisianai.com/louisiana-data-centers","localAssetPath":"outputs/imagegen/louisianai-source-cited-growth-kit-diverse-image-ads/generated/direct/05-problem-solution-split-screen.png","reviewStatus":"public-reference-svg","guardrail":"Generated image is visual reference only; do not use generated readable text, fake UI, unsupported metrics, or before-after performance claims."},{"id":"ad-app-ui-holographic-overlay","sourceFamilyId":"app-ui-holographic-overlay","title":"AI-reader file Ads Explorer reference","url":"https://louisianai.com/share/cards/ad-app-ui-holographic-overlay","backgroundPath":"/share/ads/app-ui-holographic-overlay.jpg","landingUrl":"https://louisianai.com/distribution.json","localAssetPath":"outputs/imagegen/louisianai-source-cited-growth-kit-diverse-image-ads/generated/direct/07-app-ui-holographic-overlay.png","reviewStatus":"public-reference-svg","guardrail":"Do not imply fake AI-engine screenshots, rankings, model endorsements, private dashboards, or unsourced automation performance."},{"id":"ad-minimal-premium-whitespace","sourceFamilyId":"minimal-premium-whitespace","title":"Minimal source-card Ads Explorer reference","url":"https://louisianai.com/share/cards/ad-minimal-premium-whitespace","backgroundPath":"/share/ads/minimal-premium-whitespace.jpg","landingUrl":"https://louisianai.com/share","localAssetPath":"outputs/imagegen/louisianai-source-cited-growth-kit-diverse-image-ads/generated/direct/10-minimal-premium-whitespace.png","reviewStatus":"public-reference-svg","guardrail":"Do not add luxury, official, most-read, fastest-growing, ranking, subscriber, or readership claims."},{"id":"ad-cinematic-noir-spotlight","sourceFamilyId":"cinematic-noir-spotlight","title":"Watch-desk Ads Explorer reference","url":"https://louisianai.com/share/cards/ad-cinematic-noir-spotlight","backgroundPath":"/share/ads/cinematic-noir-spotlight.jpg","landingUrl":"https://louisianai.com/lpsc-dockets","localAssetPath":"outputs/imagegen/louisianai-source-cited-growth-kit-diverse-image-ads/generated/direct/12-cinematic-noir-spotlight.png","reviewStatus":"public-reference-svg","guardrail":"Do not state docket outcomes, approvals, legal conclusions, water impacts, or rate impacts unless the source page supports the exact claim."},{"id":"ad-testimonial-proof-wall","sourceFamilyId":"testimonial-proof-wall","title":"Proof-wall Ads Explorer reference","url":"https://louisianai.com/share/cards/ad-testimonial-proof-wall","backgroundPath":"/share/ads/testimonial-proof-wall.jpg","landingUrl":"https://louisianai.com/claims.json","localAssetPath":"outputs/imagegen/louisianai-source-cited-growth-kit-diverse-image-ads/generated/direct/18-testimonial-proof-wall.png","reviewStatus":"public-reference-svg","guardrail":"Never use generated testimonial, rating, logo, source-count, endorsement, or citation-count visuals as factual proof."},{"id":"ad-cinematic-hands-demo","sourceFamilyId":"cinematic-hands-demo","title":"Hands-demo Ads Explorer reference","url":"https://louisianai.com/share/cards/ad-cinematic-hands-demo","backgroundPath":"/share/ads/cinematic-hands-demo.jpg","landingUrl":"https://louisianai.com/share","localAssetPath":"outputs/imagegen/louisianai-source-cited-growth-kit-diverse-image-ads/generated/direct/25-cinematic-hands-demo.png","reviewStatus":"public-reference-svg","guardrail":"Do not imply partner adoption, install counts, official use, or measured lift without verified source evidence."}]},"generationHandoff":{"nextOwner":"creative-production:generative-polish","generateOnlyAfterSelection":"Pick one or more prompt families first, generate background or product-context imagery, then rebuild exact headline, CTA, URL, source labels, and proof copy deterministically.","requiredBeforePublish":["Match the selected family to an approved campaign.json direction and copyBlock.","Use the source route or share-card SVG as the deterministic text/layout layer.","Reject generated images with readable fake copy, partner marks, official seals, model logos, analytics, testimonials, source counts, or altered docket language.","Attach canonical LouisianAI URLs for every factual claim in the final asset."]},"promptFamilyCount":25,"promptFamilies":[{"id":"ugc-offering-pose-thumbnail","index":1,"title":"UGC Offering Pose Thumbnail","category":"Social Native / UGC","size":"1024x1536","output":"01-ugc-offering-pose-thumbnail.png","prompt":"Create one polished business visual review image for the prompt family: UGC Offering Pose Thumbnail.\nDigital product anchor: LouisianAI Source-Cited Growth Kit.\nProduct UI and workflow facts to preserve: Business: LouisianAI. Objective: Grow source-cited organic and AI-engine visibility for louisianai.com while keeping claims evidence-grounded. Audience: Louisiana business, policy, utility, CRE, data-center, and economic-development readers. Location: Louisiana. Channels: SEO, AEO, social sharing, embeds, feeds, AI-reader files, newsletter capture. Product proof objects: source-linked tracker, project profiles, LPSC docket tracker, compare pages, embed kit, llms.txt, openapi.json, linkset.json, citation.json, assets.json, scenes.json, shots.json, brand.json, polish.json, RSS and JSON feeds. Approved readable copy must come only from campaign manifest copy blocks. Constraints: no unsupported subscriber/readership/traffic/citation/adoption/ranking/performance/savings/rate-impact claims; preserve source confidence labels, exact public-record language, docket identifiers, and canonical URLs; no partner logos, official seals, fake AI-engine screenshots, fake analytics, testimonials, or invented source counts.\nThe visual must be clearly about this digital product and should not introduce another digital product, app, SaaS workflow, or UI category.\nFamily intent: A high-energy creator-style image where a person offers the subject close to the camera while copy and marker-like accents make the ad feel native to short-form social.\nBusiness goal: test whether the subject can feel human, direct, and recommendation-led without losing product fidelity.\nScene: a real-life interior or street-fashion environment with side light, tactile shadows, a wide-angle foreground subject, and the creator mid-ground with a vivid expression.\nAd format: lifestyle creator thumbnail.\nHuman presence: one expressive creator or customer.\nRendering mode: photorealistic lifestyle commercial.\nChannel fit: TikTok thumbnail, Reels cover, Meta static ad, influencer whitelisting.\nDigital product proof: make the product UI, workflow state, and interface feedback the visual evidence.\nUI fidelity: use sparse, plausible labels and placeholder data only; do not invent real customer names, private data, or unsupported metrics.\nDo not drift into generic abstract SaaS imagery when UI/product proof is requested.\nFocus: personal recommendation, immediacy, and product visibility.\nDecision being supported: whether a social-native human thumbnail should lead the first paid or creator test.\nReusable prompt pattern: Create a photorealistic UGC-style lifestyle ad thumbnail for LouisianAI Source-Cited Growth Kit. Show one expressive the target audience described in the product facts creator in a plausible real-life setting, holding the subject close to the camera in an offering pose. Use the supplied brand palette and material cues accents in wardrobe and decor. Integrate the exact supplied headline in the product facts, if any as large clean type with depth behind the person, add short handwritten tags only if supplied, and place the exact supplied CTA or contact detail in the product facts, or no CTA if none is supplied in a small clean footer capsule. Preserve subject shape, label, logo, proportions, and claims exactly. Avoid the avoid list and fidelity risks in the product facts. Product facts: Business: LouisianAI. Objective: Grow source-cited organic and AI-engine visibility for louisianai.com while keeping claims evidence-grounded. Audience: Louisiana business, policy, utility, CRE, data-center, and economic-development readers. Location: Louisiana. Channels: SEO, AEO, social sharing, embeds, feeds, AI-reader files, newsletter capture. Product proof objects: source-linked tracker, project profiles, LPSC docket tracker, compare pages, embed kit, llms.txt, openapi.json, linkset.json, citation.json, assets.json, scenes.json, shots.json, brand.json, polish.json, RSS and JSON feeds. Approved readable copy must come only from campaign manifest copy blocks. Constraints: no unsupported subscriber/readership/traffic/citation/adoption/ranking/performance/savings/rate-impact claims; preserve source confidence labels, exact public-record language, docket identifiers, and canonical URLs; no partner logos, official seals, fake AI-engine screenshots, fake analytics, testimonials, or invented source counts.\nCopy rules: headline: Use exact supplied headline only; place behind the person or subject for depth.; supportingText: Use up to three short exact benefit tags.; cta: Use exact supplied CTA or contact detail only..\nInclude: foreground subject held toward lens, expressive human face, wide-angle perspective, large integrated headline zone, small handwritten benefit tags, minimal CTA or contact capsule.\nConstraints: preserve product label and orientation; keep hands and fingers anatomically natural; do not invent demographics beyond the brief; do not add fake creator handles; keep benefit tags short and exact; do not add subtitles, body-copy captions, explanatory footer text, or small descriptive text unless the user supplied exact copy for it; keep text sparse; use short labels, UI placeholder blocks, or visual markers only when needed; keep the product UI, workflow, and product-proof cues recognizable.\nAvoid: extra hands, warped limbs, flipped labels, plastic skin, fake endorsements, illegible headline, product hidden by text; fake endorsements; unsupported claims; misspelled large text; watermarks; clutter; other brands."},{"id":"surreal-y2k-floating-product-sculpture","index":2,"title":"Surreal Y2K Floating Product Sculpture","category":"Surreal 3D / Product Hero","size":"1024x1024","output":"02-surreal-y2k-floating-product-sculpture.png","prompt":"Create one polished business visual review image for the prompt family: Surreal Y2K Floating Product Sculpture.\nDigital product anchor: LouisianAI Source-Cited Growth Kit.\nProduct UI and workflow facts to preserve: Business: LouisianAI. Objective: Grow source-cited organic and AI-engine visibility for louisianai.com while keeping claims evidence-grounded. Audience: Louisiana business, policy, utility, CRE, data-center, and economic-development readers. Location: Louisiana. Channels: SEO, AEO, social sharing, embeds, feeds, AI-reader files, newsletter capture. Product proof objects: source-linked tracker, project profiles, LPSC docket tracker, compare pages, embed kit, llms.txt, openapi.json, linkset.json, citation.json, assets.json, scenes.json, shots.json, brand.json, polish.json, RSS and JSON feeds. Approved readable copy must come only from campaign manifest copy blocks. Constraints: no unsupported subscriber/readership/traffic/citation/adoption/ranking/performance/savings/rate-impact claims; preserve source confidence labels, exact public-record language, docket identifiers, and canonical URLs; no partner logos, official seals, fake AI-engine screenshots, fake analytics, testimonials, or invented source counts.\nThe visual must be clearly about this digital product and should not introduce another digital product, app, SaaS workflow, or UI category.\nFamily intent: A glossy Y2K-inspired product cluster with inflated objects, floating type, saturated sky or studio depth, and playful category symbols.\nBusiness goal: test whether the subject can become an iconic sculptural hero with strong recall and playful social appeal.\nScene: a bright saturated world with floating product duplicates, glossy balloon-like support objects, puffy ribbons, bloom, rim light, and atmospheric depth.\nAd format: glossy inflated 3D poster.\nHuman presence: none.\nRendering mode: stylized commercial 3D render.\nChannel fit: drop announcement, fashion ecommerce, Gen Z social, digital billboard.\nDigital product proof: make the product UI, workflow state, and interface feedback the visual evidence.\nUI fidelity: use sparse, plausible labels and placeholder data only; do not invent real customer names, private data, or unsupported metrics.\nDo not drift into generic abstract SaaS imagery when UI/product proof is requested.\nFocus: product silhouette, playful abundance, and memorable visual identity.\nDecision being supported: whether a surreal render system should carry a drop, fashion, novelty, or youth-facing campaign.\nReusable prompt pattern: Create a surreal Y2K-inspired commercial 3D poster for LouisianAI Source-Cited Growth Kit. Float multiple readable versions of the subject as hero sculptures with glossy inflated supporting symbols tied to the approved primary benefit in the product facts and the supplied brand palette and material cues. Use radiant backlight, soft bloom, high-gloss reflections, and crisp product edges. Add the exact supplied headline in the product facts, if any as clean 3D inflated or chrome type. Add the exact supplied CTA or contact detail in the product facts, or no CTA if none is supplied only if supplied. Preserve the subject exactly. Avoid the avoid list and fidelity risks in the product facts. Product facts: Business: LouisianAI. Objective: Grow source-cited organic and AI-engine visibility for louisianai.com while keeping claims evidence-grounded. Audience: Louisiana business, policy, utility, CRE, data-center, and economic-development readers. Location: Louisiana. Channels: SEO, AEO, social sharing, embeds, feeds, AI-reader files, newsletter capture. Product proof objects: source-linked tracker, project profiles, LPSC docket tracker, compare pages, embed kit, llms.txt, openapi.json, linkset.json, citation.json, assets.json, scenes.json, shots.json, brand.json, polish.json, RSS and JSON feeds. Approved readable copy must come only from campaign manifest copy blocks. Constraints: no unsupported subscriber/readership/traffic/citation/adoption/ranking/performance/savings/rate-impact claims; preserve source confidence labels, exact public-record language, docket identifiers, and canonical URLs; no partner logos, official seals, fake AI-engine screenshots, fake analytics, testimonials, or invented source counts.\nCopy rules: headline: Use exact supplied headline as giant 3D inflated or chrome lettering.; supportingText: Avoid extra labels unless supplied.; cta: No button unless the brief explicitly asks for one..\nInclude: floating subject cluster, inflated category symbols, giant 3D headline, glossy highlights, soft bloom, single footer contact line when supplied.\nConstraints: keep product readable and not mirrored; separate product material from balloon material; use support symbols that fit the category; do not add faces unless requested; keep text sparse; do not add subtitles, body-copy captions, explanatory footer text, or small descriptive text unless the user supplied exact copy for it; keep text sparse; use short labels, UI placeholder blocks, or visual markers only when needed; keep the product UI, workflow, and product-proof cues recognizable.\nAvoid: scorched texture, damaged product, melted logo, chaotic overlap, unreadable 3D type, duplicate unsupplied logos; fake endorsements; unsupported claims; misspelled large text; watermarks; clutter; other brands."},{"id":"luxury-editorial-still-life","index":3,"title":"Luxury Editorial Still Life","category":"Premium / Editorial","size":"1536x1024","output":"03-luxury-editorial-still-life.png","prompt":"Create one polished business visual review image for the prompt family: Luxury Editorial Still Life.\nDigital product anchor: LouisianAI Source-Cited Growth Kit.\nProduct UI and workflow facts to preserve: Business: LouisianAI. Objective: Grow source-cited organic and AI-engine visibility for louisianai.com while keeping claims evidence-grounded. Audience: Louisiana business, policy, utility, CRE, data-center, and economic-development readers. Location: Louisiana. Channels: SEO, AEO, social sharing, embeds, feeds, AI-reader files, newsletter capture. Product proof objects: source-linked tracker, project profiles, LPSC docket tracker, compare pages, embed kit, llms.txt, openapi.json, linkset.json, citation.json, assets.json, scenes.json, shots.json, brand.json, polish.json, RSS and JSON feeds. Approved readable copy must come only from campaign manifest copy blocks. Constraints: no unsupported subscriber/readership/traffic/citation/adoption/ranking/performance/savings/rate-impact claims; preserve source confidence labels, exact public-record language, docket identifiers, and canonical URLs; no partner logos, official seals, fake AI-engine screenshots, fake analytics, testimonials, or invented source counts.\nThe visual must be clearly about this digital product and should not introduce another digital product, app, SaaS workflow, or UI category.\nFamily intent: A restrained high-end still life using premium surfaces, negative space, material contrast, and exacting light control.\nBusiness goal: make the subject feel expensive, considered, and visually ownable without overexplaining the offer.\nScene: a precise studio or architectural still-life setup with marble, lacquer, brushed metal, linen, glass, or other category-appropriate materials.\nAd format: magazine-style product spread.\nHuman presence: none or cropped hand only.\nRendering mode: photorealistic editorial photography.\nChannel fit: print ad, luxury social, landing hero, press kit.\nDigital product proof: make the product UI, workflow state, and interface feedback the visual evidence.\nUI fidelity: use sparse, plausible labels and placeholder data only; do not invent real customer names, private data, or unsupported metrics.\nDo not drift into generic abstract SaaS imagery when UI/product proof is requested.\nFocus: craft, finish, taste, and premium recognition.\nDecision being supported: whether a premium editorial route fits the category and audience.\nReusable prompt pattern: Create a luxury editorial still-life advertisement for LouisianAI Source-Cited Growth Kit. Place the subject on a refined the supplied brand palette and material cues-compatible surface with disciplined negative space, controlled reflections, and one restrained prop family that supports the approved primary benefit in the product facts. Use magazine-quality lighting and exact product preservation. Add only exact supplied text. Avoid the avoid list and fidelity risks in the product facts. Product facts: Business: LouisianAI. Objective: Grow source-cited organic and AI-engine visibility for louisianai.com while keeping claims evidence-grounded. Audience: Louisiana business, policy, utility, CRE, data-center, and economic-development readers. Location: Louisiana. Channels: SEO, AEO, social sharing, embeds, feeds, AI-reader files, newsletter capture. Product proof objects: source-linked tracker, project profiles, LPSC docket tracker, compare pages, embed kit, llms.txt, openapi.json, linkset.json, citation.json, assets.json, scenes.json, shots.json, brand.json, polish.json, RSS and JSON feeds. Approved readable copy must come only from campaign manifest copy blocks. Constraints: no unsupported subscriber/readership/traffic/citation/adoption/ranking/performance/savings/rate-impact claims; preserve source confidence labels, exact public-record language, docket identifiers, and canonical URLs; no partner logos, official seals, fake AI-engine screenshots, fake analytics, testimonials, or invented source counts.\nCopy rules: headline: Use either no headline or a small exact editorial headline.; supportingText: Keep body text as placeholder lines unless supplied.; cta: Usually omit CTA..\nInclude: hero subject on refined surface, controlled reflection, single prop family, large negative space, small editorial caption zone.\nConstraints: preserve label, shape, material, and scale; avoid stock-photo generic props; keep composition quiet; do not invent awards or premium claims; do not add subtitles, body-copy captions, explanatory footer text, or small descriptive text unless the user supplied exact copy for it; keep text sparse; use short labels, UI placeholder blocks, or visual markers only when needed; keep the product UI, workflow, and product-proof cues recognizable.\nAvoid: busy prop styling, fake luxury logos, unreadable microtext, distorted reflections, unrelated jewelry or fragrance cues; fake endorsements; unsupported claims; misspelled large text; watermarks; clutter; other brands."},{"id":"hard-sell-direct-response-card","index":4,"title":"Hard Sell Direct Response Card","category":"Performance / Direct Response","size":"1024x1536","output":"04-hard-sell-direct-response-card.png","prompt":"Create one polished business visual review image for the prompt family: Hard Sell Direct Response Card.\nDigital product anchor: LouisianAI Source-Cited Growth Kit.\nProduct UI and workflow facts to preserve: Business: LouisianAI. Objective: Grow source-cited organic and AI-engine visibility for louisianai.com while keeping claims evidence-grounded. Audience: Louisiana business, policy, utility, CRE, data-center, and economic-development readers. Location: Louisiana. Channels: SEO, AEO, social sharing, embeds, feeds, AI-reader files, newsletter capture. Product proof objects: source-linked tracker, project profiles, LPSC docket tracker, compare pages, embed kit, llms.txt, openapi.json, linkset.json, citation.json, assets.json, scenes.json, shots.json, brand.json, polish.json, RSS and JSON feeds. Approved readable copy must come only from campaign manifest copy blocks. Constraints: no unsupported subscriber/readership/traffic/citation/adoption/ranking/performance/savings/rate-impact claims; preserve source confidence labels, exact public-record language, docket identifiers, and canonical URLs; no partner logos, official seals, fake AI-engine screenshots, fake analytics, testimonials, or invented source counts.\nThe visual must be clearly about this digital product and should not introduce another digital product, app, SaaS workflow, or UI category.\nFamily intent: A clear conversion ad with product, headline, proof slot, benefit stack, CTA, and urgency space when approved.\nBusiness goal: test whether a straightforward conversion layout communicates the offer quickly and reviewably.\nScene: a clean high-contrast ad card with product hero, benefit hierarchy, proof or rating placeholder, CTA block, and channel-safe margins.\nAd format: benefit-led static conversion ad.\nHuman presence: optional customer or product-only.\nRendering mode: polished performance composite.\nChannel fit: Meta feed, display ad, landing page module, retargeting.\nDigital product proof: make the product UI, workflow state, and interface feedback the visual evidence.\nUI fidelity: use sparse, plausible labels and placeholder data only; do not invent real customer names, private data, or unsupported metrics.\nDo not drift into generic abstract SaaS imagery when UI/product proof is requested.\nFocus: offer clarity and fast comprehension.\nDecision being supported: whether the subject should be sold through a direct response angle.\nReusable prompt pattern: Create a polished direct-response image ad for LouisianAI Source-Cited Growth Kit. Build a clear conversion card with product hero, the exact supplied headline in the product facts, if any, up to three exact approved benefit bullets, proof placeholder only if supplied, and the exact supplied CTA or contact detail in the product facts, or no CTA if none is supplied as a clean button or footer. Use the supplied brand palette and material cues for hierarchy and contrast. Preserve all subject facts. Avoid the avoid list and fidelity risks in the product facts. Product facts: Business: LouisianAI. Objective: Grow source-cited organic and AI-engine visibility for louisianai.com while keeping claims evidence-grounded. Audience: Louisiana business, policy, utility, CRE, data-center, and economic-development readers. Location: Louisiana. Channels: SEO, AEO, social sharing, embeds, feeds, AI-reader files, newsletter capture. Product proof objects: source-linked tracker, project profiles, LPSC docket tracker, compare pages, embed kit, llms.txt, openapi.json, linkset.json, citation.json, assets.json, scenes.json, shots.json, brand.json, polish.json, RSS and JSON feeds. Approved readable copy must come only from campaign manifest copy blocks. Constraints: no unsupported subscriber/readership/traffic/citation/adoption/ranking/performance/savings/rate-impact claims; preserve source confidence labels, exact public-record language, docket identifiers, and canonical URLs; no partner logos, official seals, fake AI-engine screenshots, fake analytics, testimonials, or invented source counts.\nCopy rules: headline: Use exact supplied headline only.; supportingText: Use exact approved benefits or abstract placeholder lines.; cta: Use exact supplied CTA only..\nInclude: product hero, large headline, three benefit bullets, proof or rating slot, CTA button, safe-zone margins.\nConstraints: do not invent discounts, reviews, prices, or ratings; keep the layout readable at feed size; use deterministic-looking text zones; preserve product exactly; do not add subtitles, body-copy captions, explanatory footer text, or small descriptive text unless the user supplied exact copy for it; keep text sparse; use short labels, UI placeholder blocks, or visual markers only when needed; keep the product UI, workflow, and product-proof cues recognizable.\nAvoid: fake countdowns, fake star ratings, too many claims, noisy badges, broken text hierarchy; fake endorsements; unsupported claims; misspelled large text; watermarks; clutter; other brands."},{"id":"problem-solution-split-screen","index":5,"title":"Problem Solution Split Screen","category":"Performance / Comparison","size":"1536x1024","output":"05-problem-solution-split-screen.png","prompt":"Create one polished business visual review image for the prompt family: Problem Solution Split Screen.\nDigital product anchor: LouisianAI Source-Cited Growth Kit.\nProduct UI and workflow facts to preserve: Business: LouisianAI. Objective: Grow source-cited organic and AI-engine visibility for louisianai.com while keeping claims evidence-grounded. Audience: Louisiana business, policy, utility, CRE, data-center, and economic-development readers. Location: Louisiana. Channels: SEO, AEO, social sharing, embeds, feeds, AI-reader files, newsletter capture. Product proof objects: source-linked tracker, project profiles, LPSC docket tracker, compare pages, embed kit, llms.txt, openapi.json, linkset.json, citation.json, assets.json, scenes.json, shots.json, brand.json, polish.json, RSS and JSON feeds. Approved readable copy must come only from campaign manifest copy blocks. Constraints: no unsupported subscriber/readership/traffic/citation/adoption/ranking/performance/savings/rate-impact claims; preserve source confidence labels, exact public-record language, docket identifiers, and canonical URLs; no partner logos, official seals, fake AI-engine screenshots, fake analytics, testimonials, or invented source counts.\nThe visual must be clearly about this digital product and should not introduce another digital product, app, SaaS workflow, or UI category.\nFamily intent: A two-panel ad that contrasts a problem context with the improved state enabled by the subject while avoiding exaggerated claims.\nBusiness goal: make the need-state and the product role understandable without relying on long copy.\nScene: a clean split image with left-side friction, right-side resolved moment, and the subject clearly bridging or anchoring the improvement.\nAd format: two-panel before-and-after ad.\nHuman presence: optional lifestyle or object scenes.\nRendering mode: photorealistic or polished composite.\nChannel fit: paid social, landing page, email hero, sales enablement.\nDigital product proof: make the product UI, workflow state, and interface feedback the visual evidence.\nUI fidelity: use sparse, plausible labels and placeholder data only; do not invent real customer names, private data, or unsupported metrics.\nDo not drift into generic abstract SaaS imagery when UI/product proof is requested.\nFocus: what changes for the buyer or user.\nDecision being supported: whether contrast-based messaging is appropriate for the offer.\nReusable prompt pattern: Create a problem-solution split-screen advertisement for LouisianAI Source-Cited Growth Kit. Show the problem state on the left and the improved state on the right, with the subject clearly preserved and central to the change. Use neutral, believable visual contrast and the supplied brand palette and material cues. Add exact supplied labels only. Avoid exaggerated outcomes and the avoid list and fidelity risks in the product facts. Product facts: Business: LouisianAI. Objective: Grow source-cited organic and AI-engine visibility for louisianai.com while keeping claims evidence-grounded. Audience: Louisiana business, policy, utility, CRE, data-center, and economic-development readers. Location: Louisiana. Channels: SEO, AEO, social sharing, embeds, feeds, AI-reader files, newsletter capture. Product proof objects: source-linked tracker, project profiles, LPSC docket tracker, compare pages, embed kit, llms.txt, openapi.json, linkset.json, citation.json, assets.json, scenes.json, shots.json, brand.json, polish.json, RSS and JSON feeds. Approved readable copy must come only from campaign manifest copy blocks. Constraints: no unsupported subscriber/readership/traffic/citation/adoption/ranking/performance/savings/rate-impact claims; preserve source confidence labels, exact public-record language, docket identifiers, and canonical URLs; no partner logos, official seals, fake AI-engine screenshots, fake analytics, testimonials, or invented source counts.\nCopy rules: headline: Use exact supplied headline or no headline.; supportingText: Use neutral labels such as Before and After only when supplied or appropriate.; cta: Optional small CTA..\nInclude: left problem panel, right solution panel, center product or transition device, short labels, visual consistency across panels.\nConstraints: avoid medical, financial, or performance claims unless approved; make both sides plausible; do not shame users; keep the subject visible; do not add subtitles, body-copy captions, explanatory footer text, or small descriptive text unless the user supplied exact copy for it; keep text sparse; use short labels, UI placeholder blocks, or visual markers only when needed; keep the product UI, workflow, and product-proof cues recognizable.\nAvoid: fearmongering, unrealistic transformation, fake metrics, aggressive red-green cliches, unreadable labels; fake endorsements; unsupported claims; misspelled large text; watermarks; clutter; other brands."},{"id":"cinematic-outdoor-action-hero","index":6,"title":"Cinematic Outdoor Action Hero","category":"Lifestyle / Action","size":"1536x1024","output":"06-cinematic-outdoor-action-hero.png","prompt":"Create one polished business visual review image for the prompt family: Cinematic Outdoor Action Hero.\nDigital product anchor: LouisianAI Source-Cited Growth Kit.\nProduct UI and workflow facts to preserve: Business: LouisianAI. Objective: Grow source-cited organic and AI-engine visibility for louisianai.com while keeping claims evidence-grounded. Audience: Louisiana business, policy, utility, CRE, data-center, and economic-development readers. Location: Louisiana. Channels: SEO, AEO, social sharing, embeds, feeds, AI-reader files, newsletter capture. Product proof objects: source-linked tracker, project profiles, LPSC docket tracker, compare pages, embed kit, llms.txt, openapi.json, linkset.json, citation.json, assets.json, scenes.json, shots.json, brand.json, polish.json, RSS and JSON feeds. Approved readable copy must come only from campaign manifest copy blocks. Constraints: no unsupported subscriber/readership/traffic/citation/adoption/ranking/performance/savings/rate-impact claims; preserve source confidence labels, exact public-record language, docket identifiers, and canonical URLs; no partner logos, official seals, fake AI-engine screenshots, fake analytics, testimonials, or invented source counts.\nThe visual must be clearly about this digital product and should not introduce another digital product, app, SaaS workflow, or UI category.\nFamily intent: A dramatic action scene where the subject is used in motion with environmental energy, scale, and premium cinematography.\nBusiness goal: test whether the subject can credibly own an active performance or adventure moment.\nScene: a real outdoor or urban environment with directional light, motion cues, environmental texture, and the subject clearly visible in use.\nAd format: motion-rich hero ad.\nHuman presence: one or more users when relevant.\nRendering mode: cinematic photorealistic commercial.\nChannel fit: sports social, outdoor OOH, brand film key art, launch hero.\nDigital product proof: make the product UI, workflow state, and interface feedback the visual evidence.\nUI fidelity: use sparse, plausible labels and placeholder data only; do not invent real customer names, private data, or unsupported metrics.\nDo not drift into generic abstract SaaS imagery when UI/product proof is requested.\nFocus: capability, momentum, and aspiration.\nDecision being supported: whether active-use storytelling should lead the campaign.\nReusable prompt pattern: Create a cinematic outdoor action advertisement for LouisianAI Source-Cited Growth Kit. Show the subject credibly in use by the target audience described in the product facts or staged as the hero in an active environment. Use strong natural light, movement cues, atmospheric depth, and the supplied brand palette and material cues accents. Preserve the subject exactly and add only exact supplied text. Avoid the avoid list and fidelity risks in the product facts. Product facts: Business: LouisianAI. Objective: Grow source-cited organic and AI-engine visibility for louisianai.com while keeping claims evidence-grounded. Audience: Louisiana business, policy, utility, CRE, data-center, and economic-development readers. Location: Louisiana. Channels: SEO, AEO, social sharing, embeds, feeds, AI-reader files, newsletter capture. Product proof objects: source-linked tracker, project profiles, LPSC docket tracker, compare pages, embed kit, llms.txt, openapi.json, linkset.json, citation.json, assets.json, scenes.json, shots.json, brand.json, polish.json, RSS and JSON feeds. Approved readable copy must come only from campaign manifest copy blocks. Constraints: no unsupported subscriber/readership/traffic/citation/adoption/ranking/performance/savings/rate-impact claims; preserve source confidence labels, exact public-record language, docket identifiers, and canonical URLs; no partner logos, official seals, fake AI-engine screenshots, fake analytics, testimonials, or invented source counts.\nCopy rules: headline: Use no headline or one exact short headline in open space.; supportingText: Avoid benefit tags unless supplied.; cta: Usually omit CTA..\nInclude: subject in use, motion trails or natural action cues, strong environmental scale, cinematic backlight, headline-safe sky or wall space.\nConstraints: keep action physically plausible; do not obscure the subject; avoid unsafe usage; respect real-world scale; do not add subtitles, body-copy captions, explanatory footer text, or small descriptive text unless the user supplied exact copy for it; keep text sparse; use short labels, UI placeholder blocks, or visual markers only when needed; keep the product UI, workflow, and product-proof cues recognizable.\nAvoid: extreme stunt fantasy, product motion blur, impossible body positions, generic adventure stock look; fake endorsements; unsupported claims; misspelled large text; watermarks; clutter; other brands."},{"id":"app-ui-holographic-overlay","index":7,"title":"App UI Holographic Overlay","category":"Technology / UI","size":"1536x1024","output":"07-app-ui-holographic-overlay.png","prompt":"Create one polished business visual review image for the prompt family: App UI Holographic Overlay.\nDigital product anchor: LouisianAI Source-Cited Growth Kit.\nProduct UI and workflow facts to preserve: Business: LouisianAI. Objective: Grow source-cited organic and AI-engine visibility for louisianai.com while keeping claims evidence-grounded. Audience: Louisiana business, policy, utility, CRE, data-center, and economic-development readers. Location: Louisiana. Channels: SEO, AEO, social sharing, embeds, feeds, AI-reader files, newsletter capture. Product proof objects: source-linked tracker, project profiles, LPSC docket tracker, compare pages, embed kit, llms.txt, openapi.json, linkset.json, citation.json, assets.json, scenes.json, shots.json, brand.json, polish.json, RSS and JSON feeds. Approved readable copy must come only from campaign manifest copy blocks. Constraints: no unsupported subscriber/readership/traffic/citation/adoption/ranking/performance/savings/rate-impact claims; preserve source confidence labels, exact public-record language, docket identifiers, and canonical URLs; no partner logos, official seals, fake AI-engine screenshots, fake analytics, testimonials, or invented source counts.\nThe visual must be clearly about this digital product and should not introduce another digital product, app, SaaS workflow, or UI category.\nFamily intent: A technology ad that shows the subject with clean floating UI layers, workflow indicators, or feature modules without inventing product screens.\nBusiness goal: make a digital or connected product feel tangible while keeping UI claims controlled.\nScene: a dark or bright technical environment with the subject foregrounded and translucent interface cards arranged in perspective.\nAd format: product plus interface visualization.\nHuman presence: optional hand or user silhouette.\nRendering mode: photorealistic technology composite.\nChannel fit: SaaS launch, mobile app ad, feature announcement, B2B social.\nDigital product proof: make the product UI, workflow state, and interface feedback the visual evidence.\nUI fidelity: use sparse, plausible labels and placeholder data only; do not invent real customer names, private data, or unsupported metrics.\nDo not drift into generic abstract SaaS imagery when UI/product proof is requested.\nFocus: feature clarity, control, and modern utility.\nDecision being supported: whether UI-led visual explanation should be used before a deterministic product mockup is built.\nReusable prompt pattern: Create a premium technology image ad for LouisianAI Source-Cited Growth Kit with holographic UI overlays. Preserve the actual product, app, or device boundaries exactly. Show translucent feature cards and workflow indicators that imply the approved primary benefit in the product facts without inventing real UI copy. Use the supplied brand palette and material cues, controlled glow, and clean composition. Avoid the avoid list and fidelity risks in the product facts. Product facts: Business: LouisianAI. Objective: Grow source-cited organic and AI-engine visibility for louisianai.com while keeping claims evidence-grounded. Audience: Louisiana business, policy, utility, CRE, data-center, and economic-development readers. Location: Louisiana. Channels: SEO, AEO, social sharing, embeds, feeds, AI-reader files, newsletter capture. Product proof objects: source-linked tracker, project profiles, LPSC docket tracker, compare pages, embed kit, llms.txt, openapi.json, linkset.json, citation.json, assets.json, scenes.json, shots.json, brand.json, polish.json, RSS and JSON feeds. Approved readable copy must come only from campaign manifest copy blocks. Constraints: no unsupported subscriber/readership/traffic/citation/adoption/ranking/performance/savings/rate-impact claims; preserve source confidence labels, exact public-record language, docket identifiers, and canonical URLs; no partner logos, official seals, fake AI-engine screenshots, fake analytics, testimonials, or invented source counts.\nCopy rules: headline: Use exact supplied headline only.; supportingText: Use placeholder UI blocks unless real UI copy is supplied.; cta: Optional exact CTA..\nInclude: device or product hero, floating UI cards, workflow arrows, feature module placeholders, clean light grid.\nConstraints: do not invent product interface claims; keep UI text abstract unless supplied; do not distort screens; avoid cybersecurity or AI claims unless approved; do not add subtitles, body-copy captions, explanatory footer text, or small descriptive text unless the user supplied exact copy for it; keep text sparse; use short labels, UI placeholder blocks, or visual markers only when needed; keep the product UI, workflow, and product-proof cues recognizable.\nAvoid: fake dashboards, random code, unreadable neon clutter, overdone sci-fi effects, wrong device OS; fake endorsements; unsupported claims; misspelled large text; watermarks; clutter; other brands."},{"id":"exploded-view-benefit-diagram","index":8,"title":"Exploded View Benefit Diagram","category":"Explainer / Product Demo","size":"1536x1024","output":"08-exploded-view-benefit-diagram.png","prompt":"Create one polished business visual review image for the prompt family: Exploded View Benefit Diagram.\nDigital product anchor: LouisianAI Source-Cited Growth Kit.\nProduct UI and workflow facts to preserve: Business: LouisianAI. Objective: Grow source-cited organic and AI-engine visibility for louisianai.com while keeping claims evidence-grounded. Audience: Louisiana business, policy, utility, CRE, data-center, and economic-development readers. Location: Louisiana. Channels: SEO, AEO, social sharing, embeds, feeds, AI-reader files, newsletter capture. Product proof objects: source-linked tracker, project profiles, LPSC docket tracker, compare pages, embed kit, llms.txt, openapi.json, linkset.json, citation.json, assets.json, scenes.json, shots.json, brand.json, polish.json, RSS and JSON feeds. Approved readable copy must come only from campaign manifest copy blocks. Constraints: no unsupported subscriber/readership/traffic/citation/adoption/ranking/performance/savings/rate-impact claims; preserve source confidence labels, exact public-record language, docket identifiers, and canonical URLs; no partner logos, official seals, fake AI-engine screenshots, fake analytics, testimonials, or invented source counts.\nThe visual must be clearly about this digital product and should not introduce another digital product, app, SaaS workflow, or UI category.\nFamily intent: An exploded or cutaway ad that visualizes components, ingredients, layers, or service parts as a clear benefit story.\nBusiness goal: turn product construction or service logic into a concise visual proof system.\nScene: a clean studio or technical diagram space where subject layers float apart with callout lines and disciplined labels.\nAd format: technical product breakdown ad.\nHuman presence: none.\nRendering mode: premium 3D or clean vector-like composite.\nChannel fit: PDP module, launch explainer, sales deck, email feature block.\nDigital product proof: make the product UI, workflow state, and interface feedback the visual evidence.\nUI fidelity: use sparse, plausible labels and placeholder data only; do not invent real customer names, private data, or unsupported metrics.\nDo not drift into generic abstract SaaS imagery when UI/product proof is requested.\nFocus: how the subject works or why it is different.\nDecision being supported: whether the offer needs a demo-led ad rather than a lifestyle ad.\nReusable prompt pattern: Create an exploded-view benefit diagram ad for LouisianAI Source-Cited Growth Kit. Separate the subject into plausible layers, components, ingredients, or service steps only when supported by the brief. Use clean callouts, numbered markers, and the supplied brand palette and material cues. Preserve the product form and avoid inventing internal mechanisms. Add exact supplied text only. Avoid the avoid list and fidelity risks in the product facts. Product facts: Business: LouisianAI. Objective: Grow source-cited organic and AI-engine visibility for louisianai.com while keeping claims evidence-grounded. Audience: Louisiana business, policy, utility, CRE, data-center, and economic-development readers. Location: Louisiana. Channels: SEO, AEO, social sharing, embeds, feeds, AI-reader files, newsletter capture. Product proof objects: source-linked tracker, project profiles, LPSC docket tracker, compare pages, embed kit, llms.txt, openapi.json, linkset.json, citation.json, assets.json, scenes.json, shots.json, brand.json, polish.json, RSS and JSON feeds. Approved readable copy must come only from campaign manifest copy blocks. Constraints: no unsupported subscriber/readership/traffic/citation/adoption/ranking/performance/savings/rate-impact claims; preserve source confidence labels, exact public-record language, docket identifiers, and canonical URLs; no partner logos, official seals, fake AI-engine screenshots, fake analytics, testimonials, or invented source counts.\nCopy rules: headline: Use exact supplied headline or no headline.; supportingText: Use numbered placeholders unless real feature names are supplied.; cta: Omit CTA unless requested..\nInclude: exploded subject layers, callout lines, numbered benefit markers, material or feature details, clean caption rail.\nConstraints: do not show false internal parts; label assumptions as placeholders; keep callouts sparse; preserve outer product recognition; do not add subtitles, body-copy captions, explanatory footer text, or small descriptive text unless the user supplied exact copy for it; keep text sparse; use short labels, UI placeholder blocks, or visual markers only when needed; keep the product UI, workflow, and product-proof cues recognizable.\nAvoid: fake engineering claims, excessive labels, impossible cross-sections, medical diagrams for nonmedical products; fake endorsements; unsupported claims; misspelled large text; watermarks; clutter; other brands."},{"id":"retail-shelf-battle-card","index":9,"title":"Retail Shelf Battle Card","category":"Retail / Shopper","size":"1536x1024","output":"09-retail-shelf-battle-card.png","prompt":"Create one polished business visual review image for the prompt family: Retail Shelf Battle Card.\nDigital product anchor: LouisianAI Source-Cited Growth Kit.\nProduct UI and workflow facts to preserve: Business: LouisianAI. Objective: Grow source-cited organic and AI-engine visibility for louisianai.com while keeping claims evidence-grounded. Audience: Louisiana business, policy, utility, CRE, data-center, and economic-development readers. Location: Louisiana. Channels: SEO, AEO, social sharing, embeds, feeds, AI-reader files, newsletter capture. Product proof objects: source-linked tracker, project profiles, LPSC docket tracker, compare pages, embed kit, llms.txt, openapi.json, linkset.json, citation.json, assets.json, scenes.json, shots.json, brand.json, polish.json, RSS and JSON feeds. Approved readable copy must come only from campaign manifest copy blocks. Constraints: no unsupported subscriber/readership/traffic/citation/adoption/ranking/performance/savings/rate-impact claims; preserve source confidence labels, exact public-record language, docket identifiers, and canonical URLs; no partner logos, official seals, fake AI-engine screenshots, fake analytics, testimonials, or invented source counts.\nThe visual must be clearly about this digital product and should not introduce another digital product, app, SaaS workflow, or UI category.\nFamily intent: A shelf or marketplace-style image that tests whether the subject stands out in a buying environment while avoiding fake competitor brands.\nBusiness goal: evaluate shelf clarity, category fit, and shopper recognition.\nScene: a clean retail shelf, endcap, marketplace grid, or display context with the subject repeated or heroed at realistic scale.\nAd format: shelf-impact static ad.\nHuman presence: optional shopper hand.\nRendering mode: photorealistic retail composite.\nChannel fit: shopper marketing, retail pitch, Amazon module, trade deck.\nDigital product proof: make the product UI, workflow state, and interface feedback the visual evidence.\nUI fidelity: use sparse, plausible labels and placeholder data only; do not invent real customer names, private data, or unsupported metrics.\nDo not drift into generic abstract SaaS imagery when UI/product proof is requested.\nFocus: visibility, pack read, and purchase readiness.\nDecision being supported: whether retail or ecommerce context should be prioritized for the campaign.\nReusable prompt pattern: Create a retail shelf-impact ad for LouisianAI Source-Cited Growth Kit. Place the subject in a plausible shelf, endcap, or ecommerce grid context with generic category neighbors and clean purchase cues. Preserve packaging, scale, and label hierarchy. Use the supplied brand palette and material cues for display accents. Add exact supplied text only. Avoid the avoid list and fidelity risks in the product facts. Product facts: Business: LouisianAI. Objective: Grow source-cited organic and AI-engine visibility for louisianai.com while keeping claims evidence-grounded. Audience: Louisiana business, policy, utility, CRE, data-center, and economic-development readers. Location: Louisiana. Channels: SEO, AEO, social sharing, embeds, feeds, AI-reader files, newsletter capture. Product proof objects: source-linked tracker, project profiles, LPSC docket tracker, compare pages, embed kit, llms.txt, openapi.json, linkset.json, citation.json, assets.json, scenes.json, shots.json, brand.json, polish.json, RSS and JSON feeds. Approved readable copy must come only from campaign manifest copy blocks. Constraints: no unsupported subscriber/readership/traffic/citation/adoption/ranking/performance/savings/rate-impact claims; preserve source confidence labels, exact public-record language, docket identifiers, and canonical URLs; no partner logos, official seals, fake AI-engine screenshots, fake analytics, testimonials, or invented source counts.\nCopy rules: headline: Use no headline or exact retail message.; supportingText: Use generic shelf tags unless supplied.; cta: Usually omit CTA..\nInclude: subject on shelf or grid, generic category neighbors, price-tag placeholder, shelf talker zone, shopper decision cue.\nConstraints: do not invent retailer names; do not create competitor lookalikes; keep price and promo tags generic unless supplied; preserve product hierarchy; do not add subtitles, body-copy captions, explanatory footer text, or small descriptive text unless the user supplied exact copy for it; keep text sparse; use short labels, UI placeholder blocks, or visual markers only when needed; keep the product UI, workflow, and product-proof cues recognizable.\nAvoid: fake retailer branding, chaotic shelf clutter, wrong product category, unreadable repeated facings; fake endorsements; unsupported claims; misspelled large text; watermarks; clutter; other brands."},{"id":"minimal-premium-whitespace","index":10,"title":"Minimal Premium Whitespace","category":"Brand / Minimal","size":"1024x1024","output":"10-minimal-premium-whitespace.png","prompt":"Create one polished business visual review image for the prompt family: Minimal Premium Whitespace.\nDigital product anchor: LouisianAI Source-Cited Growth Kit.\nProduct UI and workflow facts to preserve: Business: LouisianAI. Objective: Grow source-cited organic and AI-engine visibility for louisianai.com while keeping claims evidence-grounded. Audience: Louisiana business, policy, utility, CRE, data-center, and economic-development readers. Location: Louisiana. Channels: SEO, AEO, social sharing, embeds, feeds, AI-reader files, newsletter capture. Product proof objects: source-linked tracker, project profiles, LPSC docket tracker, compare pages, embed kit, llms.txt, openapi.json, linkset.json, citation.json, assets.json, scenes.json, shots.json, brand.json, polish.json, RSS and JSON feeds. Approved readable copy must come only from campaign manifest copy blocks. Constraints: no unsupported subscriber/readership/traffic/citation/adoption/ranking/performance/savings/rate-impact claims; preserve source confidence labels, exact public-record language, docket identifiers, and canonical URLs; no partner logos, official seals, fake AI-engine screenshots, fake analytics, testimonials, or invented source counts.\nThe visual must be clearly about this digital product and should not introduce another digital product, app, SaaS workflow, or UI category.\nFamily intent: A spare, high-control image where the subject and a single line of exact copy carry the ad.\nBusiness goal: test whether the brand can communicate confidence through restraint.\nScene: a clean white, off-white, or muted color field with the subject precisely placed, elegant shadow, and generous negative space.\nAd format: clean product poster.\nHuman presence: none.\nRendering mode: premium studio photography or render.\nChannel fit: brand launch, website hero, print insert, premium social.\nDigital product proof: make the product UI, workflow state, and interface feedback the visual evidence.\nUI fidelity: use sparse, plausible labels and placeholder data only; do not invent real customer names, private data, or unsupported metrics.\nDo not drift into generic abstract SaaS imagery when UI/product proof is requested.\nFocus: clarity, restraint, and product confidence.\nDecision being supported: whether a minimal premium system is strong enough for the category.\nReusable prompt pattern: Create a minimal premium image ad for LouisianAI Source-Cited Growth Kit. Use a clean field, precise product placement, refined shadow, and generous negative space. Add the exact supplied headline in the product facts, if any only if supplied, set with quiet premium typography. Preserve the subject exactly and avoid decorative clutter. Avoid the avoid list and fidelity risks in the product facts. Product facts: Business: LouisianAI. Objective: Grow source-cited organic and AI-engine visibility for louisianai.com while keeping claims evidence-grounded. Audience: Louisiana business, policy, utility, CRE, data-center, and economic-development readers. Location: Louisiana. Channels: SEO, AEO, social sharing, embeds, feeds, AI-reader files, newsletter capture. Product proof objects: source-linked tracker, project profiles, LPSC docket tracker, compare pages, embed kit, llms.txt, openapi.json, linkset.json, citation.json, assets.json, scenes.json, shots.json, brand.json, polish.json, RSS and JSON feeds. Approved readable copy must come only from campaign manifest copy blocks. Constraints: no unsupported subscriber/readership/traffic/citation/adoption/ranking/performance/savings/rate-impact claims; preserve source confidence labels, exact public-record language, docket identifiers, and canonical URLs; no partner logos, official seals, fake AI-engine screenshots, fake analytics, testimonials, or invented source counts.\nCopy rules: headline: Use one exact short line only.; supportingText: Avoid supporting copy.; cta: Use a small exact CTA only if supplied..\nInclude: single subject hero, subtle floor shadow, large negative space, one-line headline, small brand or CTA zone.\nConstraints: do not fill the space with props; keep product scale deliberate; use exact text only; avoid generic tech gradients; do not add subtitles, body-copy captions, explanatory footer text, or small descriptive text unless the user supplied exact copy for it; keep text sparse; use short labels, UI placeholder blocks, or visual markers only when needed; keep the product UI, workflow, and product-proof cues recognizable.\nAvoid: floating orbs, random abstract shapes, tiny product, over-styled typography, missing subject detail; fake endorsements; unsupported claims; misspelled large text; watermarks; clutter; other brands."},{"id":"maximalist-collage-scrapbook","index":11,"title":"Maximalist Collage Scrapbook","category":"Social Native / Collage","size":"1024x1024","output":"11-maximalist-collage-scrapbook.png","prompt":"Create one polished business visual review image for the prompt family: Maximalist Collage Scrapbook.\nDigital product anchor: LouisianAI Source-Cited Growth Kit.\nProduct UI and workflow facts to preserve: Business: LouisianAI. Objective: Grow source-cited organic and AI-engine visibility for louisianai.com while keeping claims evidence-grounded. Audience: Louisiana business, policy, utility, CRE, data-center, and economic-development readers. Location: Louisiana. Channels: SEO, AEO, social sharing, embeds, feeds, AI-reader files, newsletter capture. Product proof objects: source-linked tracker, project profiles, LPSC docket tracker, compare pages, embed kit, llms.txt, openapi.json, linkset.json, citation.json, assets.json, scenes.json, shots.json, brand.json, polish.json, RSS and JSON feeds. Approved readable copy must come only from campaign manifest copy blocks. Constraints: no unsupported subscriber/readership/traffic/citation/adoption/ranking/performance/savings/rate-impact claims; preserve source confidence labels, exact public-record language, docket identifiers, and canonical URLs; no partner logos, official seals, fake AI-engine screenshots, fake analytics, testimonials, or invented source counts.\nThe visual must be clearly about this digital product and should not introduce another digital product, app, SaaS workflow, or UI category.\nFamily intent: A layered collage ad with cutouts, stickers, tape, snapshots, scribbles, swatches, and product repeats arranged with intentional energy.\nBusiness goal: test a playful high-information route for audiences that respond to taste cues and social proof texture.\nScene: a tabletop, wall, or digital scrapbook composition layered with product cutouts, lifestyle fragments, stickers, notes, and palette cues.\nAd format: scrapbook-style ad poster.\nHuman presence: optional cutout people or hands.\nRendering mode: mixed-media photoreal collage.\nChannel fit: Instagram feed, Pinterest, youth campaign, festival launch.\nDigital product proof: make the product UI, workflow state, and interface feedback the visual evidence.\nUI fidelity: use sparse, plausible labels and placeholder data only; do not invent real customer names, private data, or unsupported metrics.\nDo not drift into generic abstract SaaS imagery when UI/product proof is requested.\nFocus: abundance, personality, and shareable campaign texture.\nDecision being supported: whether the campaign should lean social, expressive, and collected rather than polished and minimal.\nReusable prompt pattern: Create a maximalist collage scrapbook image ad for LouisianAI Source-Cited Growth Kit. Build layered product cutouts, lifestyle fragments, stickers, tape, texture, and the supplied brand palette and material cues swatches around the approved primary benefit in the product facts. Keep the subject recognizable in every repeat. Use exact supplied copy only and preserve product details. Avoid the avoid list and fidelity risks in the product facts. Product facts: Business: LouisianAI. Objective: Grow source-cited organic and AI-engine visibility for louisianai.com while keeping claims evidence-grounded. Audience: Louisiana business, policy, utility, CRE, data-center, and economic-development readers. Location: Louisiana. Channels: SEO, AEO, social sharing, embeds, feeds, AI-reader files, newsletter capture. Product proof objects: source-linked tracker, project profiles, LPSC docket tracker, compare pages, embed kit, llms.txt, openapi.json, linkset.json, citation.json, assets.json, scenes.json, shots.json, brand.json, polish.json, RSS and JSON feeds. Approved readable copy must come only from campaign manifest copy blocks. Constraints: no unsupported subscriber/readership/traffic/citation/adoption/ranking/performance/savings/rate-impact claims; preserve source confidence labels, exact public-record language, docket identifiers, and canonical URLs; no partner logos, official seals, fake AI-engine screenshots, fake analytics, testimonials, or invented source counts.\nCopy rules: headline: Use exact supplied headline as one dominant cutout or sticker.; supportingText: Use only supplied short notes or placeholder marks.; cta: Small exact CTA sticker if supplied..\nInclude: product cutouts, photo fragments, sticker labels, tape edges, palette swatches, handwritten notes.\nConstraints: keep at least one clean product hero; do not hide labels under stickers; avoid copyrighted character-like stickers; control visual hierarchy; do not add subtitles, body-copy captions, explanatory footer text, or small descriptive text unless the user supplied exact copy for it; keep text sparse; use short labels, UI placeholder blocks, or visual markers only when needed; keep the product UI, workflow, and product-proof cues recognizable.\nAvoid: messy moodboard filler, illegible sticker text, too many product duplicates, unrelated pop-culture references; fake endorsements; unsupported claims; misspelled large text; watermarks; clutter; other brands."},{"id":"cinematic-noir-spotlight","index":12,"title":"Cinematic Noir Spotlight","category":"Entertainment / Dramatic","size":"1536x1024","output":"12-cinematic-noir-spotlight.png","prompt":"Create one polished business visual review image for the prompt family: Cinematic Noir Spotlight.\nDigital product anchor: LouisianAI Source-Cited Growth Kit.\nProduct UI and workflow facts to preserve: Business: LouisianAI. Objective: Grow source-cited organic and AI-engine visibility for louisianai.com while keeping claims evidence-grounded. Audience: Louisiana business, policy, utility, CRE, data-center, and economic-development readers. Location: Louisiana. Channels: SEO, AEO, social sharing, embeds, feeds, AI-reader files, newsletter capture. Product proof objects: source-linked tracker, project profiles, LPSC docket tracker, compare pages, embed kit, llms.txt, openapi.json, linkset.json, citation.json, assets.json, scenes.json, shots.json, brand.json, polish.json, RSS and JSON feeds. Approved readable copy must come only from campaign manifest copy blocks. Constraints: no unsupported subscriber/readership/traffic/citation/adoption/ranking/performance/savings/rate-impact claims; preserve source confidence labels, exact public-record language, docket identifiers, and canonical URLs; no partner logos, official seals, fake AI-engine screenshots, fake analytics, testimonials, or invented source counts.\nThe visual must be clearly about this digital product and should not introduce another digital product, app, SaaS workflow, or UI category.\nFamily intent: A dramatic low-key ad using spotlight, haze, shadow, and controlled color to make the subject feel consequential.\nBusiness goal: test whether mystery, tension, and premium drama can elevate the subject.\nScene: a dark stage, alley, studio, or architectural set with one precise beam of light, haze, reflective surfaces, and a restrained headline zone.\nAd format: dark poster-lit ad.\nHuman presence: optional silhouette.\nRendering mode: cinematic photorealistic poster.\nChannel fit: premium launch, teaser campaign, film-style social, OOH.\nDigital product proof: make the product UI, workflow state, and interface feedback the visual evidence.\nUI fidelity: use sparse, plausible labels and placeholder data only; do not invent real customer names, private data, or unsupported metrics.\nDo not drift into generic abstract SaaS imagery when UI/product proof is requested.\nFocus: intrigue, focus, and premium tension.\nDecision being supported: whether a cinematic teaser route fits the brand and category.\nReusable prompt pattern: Create a cinematic noir spotlight ad for LouisianAI Source-Cited Growth Kit. Place the subject in a dark dramatic environment with one controlled light source, deep shadow, haze, and the supplied brand palette and material cues accent highlights. Use sparse exact copy only. Preserve the subject shape, material, and label. Avoid the avoid list and fidelity risks in the product facts. Product facts: Business: LouisianAI. Objective: Grow source-cited organic and AI-engine visibility for louisianai.com while keeping claims evidence-grounded. Audience: Louisiana business, policy, utility, CRE, data-center, and economic-development readers. Location: Louisiana. Channels: SEO, AEO, social sharing, embeds, feeds, AI-reader files, newsletter capture. Product proof objects: source-linked tracker, project profiles, LPSC docket tracker, compare pages, embed kit, llms.txt, openapi.json, linkset.json, citation.json, assets.json, scenes.json, shots.json, brand.json, polish.json, RSS and JSON feeds. Approved readable copy must come only from campaign manifest copy blocks. Constraints: no unsupported subscriber/readership/traffic/citation/adoption/ranking/performance/savings/rate-impact claims; preserve source confidence labels, exact public-record language, docket identifiers, and canonical URLs; no partner logos, official seals, fake AI-engine screenshots, fake analytics, testimonials, or invented source counts.\nCopy rules: headline: Use one exact teaser line or no text.; supportingText: Avoid explanatory copy.; cta: Omit or use very small exact CTA..\nInclude: spotlit subject, deep shadow, light beam or haze, single accent color, small teaser headline.\nConstraints: keep subject readable despite darkness; avoid horror cues unless requested; do not invent film titles or awards; control reflections; do not add subtitles, body-copy captions, explanatory footer text, or small descriptive text unless the user supplied exact copy for it; keep text sparse; use short labels, UI placeholder blocks, or visual markers only when needed; keep the product UI, workflow, and product-proof cues recognizable.\nAvoid: muddy underexposure, fake movie billing blocks, unreadable product, excessive smoke, dangerous usage; fake endorsements; unsupported claims; misspelled large text; watermarks; clutter; other brands."},{"id":"cold-splash-refreshment","index":13,"title":"Cold Splash Flavor Word Backdrop","category":"Food Beverage / Motion","size":"1024x1024","output":"13-cold-splash-refreshment.png","prompt":"Create one polished business visual review image for the prompt family: Cold Splash Flavor Word Backdrop.\nDigital product anchor: LouisianAI Source-Cited Growth Kit.\nProduct UI and workflow facts to preserve: Business: LouisianAI. Objective: Grow source-cited organic and AI-engine visibility for louisianai.com while keeping claims evidence-grounded. Audience: Louisiana business, policy, utility, CRE, data-center, and economic-development readers. Location: Louisiana. Channels: SEO, AEO, social sharing, embeds, feeds, AI-reader files, newsletter capture. Product proof objects: source-linked tracker, project profiles, LPSC docket tracker, compare pages, embed kit, llms.txt, openapi.json, linkset.json, citation.json, assets.json, scenes.json, shots.json, brand.json, polish.json, RSS and JSON feeds. Approved readable copy must come only from campaign manifest copy blocks. Constraints: no unsupported subscriber/readership/traffic/citation/adoption/ranking/performance/savings/rate-impact claims; preserve source confidence labels, exact public-record language, docket identifiers, and canonical URLs; no partner logos, official seals, fake AI-engine screenshots, fake analytics, testimonials, or invented source counts.\nThe visual must be clearly about this digital product and should not introduce another digital product, app, SaaS workflow, or UI category.\nFamily intent: A high-speed refreshment ad built around a centered cold product, visible condensation, giant flavor-word typography, citrus or ingredient cues, and clean cool color.\nBusiness goal: make refreshment or freshness instantly legible.\nScene: a clean studio setup with the product centered over bold capital flavor text, surrounded by truthful fruit, herb, ice, droplets, splash arcs, condensation, and blue-toned coolness cues.\nAd format: splash and condensation ad.\nHuman presence: none.\nRendering mode: high-speed commercial photography.\nChannel fit: beverage launch, summer campaign, retail display, paid social.\nDigital product proof: make the product UI, workflow state, and interface feedback the visual evidence.\nUI fidelity: use sparse, plausible labels and placeholder data only; do not invent real customer names, private data, or unsupported metrics.\nDo not drift into generic abstract SaaS imagery when UI/product proof is requested.\nFocus: coldness, flavor, immediacy, and crisp refreshment.\nDecision being supported: whether a high-sensory motion route fits the product and season.\nReusable prompt pattern: Create a cold splash flavor-word image ad for LouisianAI Source-Cited Growth Kit. Center the product sharply over a huge bold capital flavor word or headline from the exact supplied headline in the product facts, if any, with condensation, water droplets, crushed ice, splash motion, and truthful fruit or herb cues that support the approved primary benefit in the product facts. Use the supplied brand palette and material cues plus cool blue freshness accents as appropriate. Preserve label, form, and orientation exactly. Do not copy another beverage brand's identity unless that brand is the supplied subject. Add exact supplied text only. Avoid the avoid list and fidelity risks in the product facts. Product facts: Business: LouisianAI. Objective: Grow source-cited organic and AI-engine visibility for louisianai.com while keeping claims evidence-grounded. Audience: Louisiana business, policy, utility, CRE, data-center, and economic-development readers. Location: Louisiana. Channels: SEO, AEO, social sharing, embeds, feeds, AI-reader files, newsletter capture. Product proof objects: source-linked tracker, project profiles, LPSC docket tracker, compare pages, embed kit, llms.txt, openapi.json, linkset.json, citation.json, assets.json, scenes.json, shots.json, brand.json, polish.json, RSS and JSON feeds. Approved readable copy must come only from campaign manifest copy blocks. Constraints: no unsupported subscriber/readership/traffic/citation/adoption/ranking/performance/savings/rate-impact claims; preserve source confidence labels, exact public-record language, docket identifiers, and canonical URLs; no partner logos, official seals, fake AI-engine screenshots, fake analytics, testimonials, or invented source counts.\nCopy rules: headline: Use one exact short headline if supplied.; supportingText: Avoid body copy.; cta: Optional exact retail CTA..\nInclude: sharp centered product hero, bold flavor word backdrop, ice or water splash, condensation and droplets, truthful fruit or herb cues, cool blue accent lighting.\nConstraints: use only plausible flavor or ingredient cues; keep label readable; do not mimic Sprite or another beverage brand unless supplied; avoid unsafe glass or liquid chaos; do not invent health claims; do not add subtitles, body-copy captions, explanatory footer text, or small descriptive text unless the user supplied exact copy for it; keep text sparse; use short labels, UI placeholder blocks, or visual markers only when needed; keep the product UI, workflow, and product-proof cues recognizable.\nAvoid: label covered by water, fake fruit flavors, over-saturated color, product crushed or damaged; fake endorsements; unsupported claims; misspelled large text; watermarks; clutter; other brands."},{"id":"cozy-home-ritual","index":14,"title":"Cozy Home Ritual","category":"Lifestyle / Home","size":"1536x1024","output":"14-cozy-home-ritual.png","prompt":"Create one polished business visual review image for the prompt family: Cozy Home Ritual.\nDigital product anchor: LouisianAI Source-Cited Growth Kit.\nProduct UI and workflow facts to preserve: Business: LouisianAI. Objective: Grow source-cited organic and AI-engine visibility for louisianai.com while keeping claims evidence-grounded. Audience: Louisiana business, policy, utility, CRE, data-center, and economic-development readers. Location: Louisiana. Channels: SEO, AEO, social sharing, embeds, feeds, AI-reader files, newsletter capture. Product proof objects: source-linked tracker, project profiles, LPSC docket tracker, compare pages, embed kit, llms.txt, openapi.json, linkset.json, citation.json, assets.json, scenes.json, shots.json, brand.json, polish.json, RSS and JSON feeds. Approved readable copy must come only from campaign manifest copy blocks. Constraints: no unsupported subscriber/readership/traffic/citation/adoption/ranking/performance/savings/rate-impact claims; preserve source confidence labels, exact public-record language, docket identifiers, and canonical URLs; no partner logos, official seals, fake AI-engine screenshots, fake analytics, testimonials, or invented source counts.\nThe visual must be clearly about this digital product and should not introduce another digital product, app, SaaS workflow, or UI category.\nFamily intent: A warm domestic ad where the subject appears in a believable routine with tactile comfort, daylight, and household trust.\nBusiness goal: connect the subject to habit, comfort, repeat use, and familiarity.\nScene: a kitchen, bedroom, living room, bathroom, or entryway routine with warm natural light, useful props, and the subject placed in active context.\nAd format: warm everyday routine ad.\nHuman presence: optional hands or household user.\nRendering mode: photoreal lifestyle commercial.\nChannel fit: CPG social, home goods, email hero, brand content.\nDigital product proof: make the product UI, workflow state, and interface feedback the visual evidence.\nUI fidelity: use sparse, plausible labels and placeholder data only; do not invent real customer names, private data, or unsupported metrics.\nDo not drift into generic abstract SaaS imagery when UI/product proof is requested.\nFocus: habit, care, warmth, and practical desirability.\nDecision being supported: whether a home-use moment should anchor the campaign.\nReusable prompt pattern: Create a cozy home ritual image ad for LouisianAI Source-Cited Growth Kit. Place the subject in a believable household routine for the target audience described in the product facts, using warm daylight, tactile surfaces, and useful props that support the approved primary benefit in the product facts. Preserve the subject exactly and use the supplied brand palette and material cues accents naturally. Add exact supplied text only. Avoid the avoid list and fidelity risks in the product facts. Product facts: Business: LouisianAI. Objective: Grow source-cited organic and AI-engine visibility for louisianai.com while keeping claims evidence-grounded. Audience: Louisiana business, policy, utility, CRE, data-center, and economic-development readers. Location: Louisiana. Channels: SEO, AEO, social sharing, embeds, feeds, AI-reader files, newsletter capture. Product proof objects: source-linked tracker, project profiles, LPSC docket tracker, compare pages, embed kit, llms.txt, openapi.json, linkset.json, citation.json, assets.json, scenes.json, shots.json, brand.json, polish.json, RSS and JSON feeds. Approved readable copy must come only from campaign manifest copy blocks. Constraints: no unsupported subscriber/readership/traffic/citation/adoption/ranking/performance/savings/rate-impact claims; preserve source confidence labels, exact public-record language, docket identifiers, and canonical URLs; no partner logos, official seals, fake AI-engine screenshots, fake analytics, testimonials, or invented source counts.\nCopy rules: headline: Use exact supplied headline if it fits the scene.; supportingText: Avoid dense text.; cta: Small exact CTA if supplied..\nInclude: subject in routine context, warm daylight, useful household props, human hand or activity cue, quiet headline space.\nConstraints: make the routine plausible; avoid staged stock-photo smiles; do not add unsupported family or health claims; keep product visible; do not add subtitles, body-copy captions, explanatory footer text, or small descriptive text unless the user supplied exact copy for it; keep text sparse; use short labels, UI placeholder blocks, or visual markers only when needed; keep the product UI, workflow, and product-proof cues recognizable.\nAvoid: generic beige lifestyle scene, cluttered home, unsafe product use, unapproved children or pets; fake endorsements; unsupported claims; misspelled large text; watermarks; clutter; other brands."},{"id":"streetwear-drop-poster","index":15,"title":"Streetwear Drop Poster","category":"Fashion / Hype","size":"1024x1536","output":"15-streetwear-drop-poster.png","prompt":"Create one polished business visual review image for the prompt family: Streetwear Drop Poster.\nDigital product anchor: LouisianAI Source-Cited Growth Kit.\nProduct UI and workflow facts to preserve: Business: LouisianAI. Objective: Grow source-cited organic and AI-engine visibility for louisianai.com while keeping claims evidence-grounded. Audience: Louisiana business, policy, utility, CRE, data-center, and economic-development readers. Location: Louisiana. Channels: SEO, AEO, social sharing, embeds, feeds, AI-reader files, newsletter capture. Product proof objects: source-linked tracker, project profiles, LPSC docket tracker, compare pages, embed kit, llms.txt, openapi.json, linkset.json, citation.json, assets.json, scenes.json, shots.json, brand.json, polish.json, RSS and JSON feeds. Approved readable copy must come only from campaign manifest copy blocks. Constraints: no unsupported subscriber/readership/traffic/citation/adoption/ranking/performance/savings/rate-impact claims; preserve source confidence labels, exact public-record language, docket identifiers, and canonical URLs; no partner logos, official seals, fake AI-engine screenshots, fake analytics, testimonials, or invented source counts.\nThe visual must be clearly about this digital product and should not introduce another digital product, app, SaaS workflow, or UI category.\nFamily intent: A high-contrast fashion or youth-culture ad with street textures, product scale, bold type, and limited-release energy.\nBusiness goal: test scarcity, attitude, and street-level desirability without inventing false availability claims.\nScene: an urban wall, studio floor, alley, skate spot, or backstage setup with gritty texture, fashion lighting, and product-forward composition.\nAd format: limited-drop announcement.\nHuman presence: optional model or product-only.\nRendering mode: gritty fashion editorial composite.\nChannel fit: drop announcement, street poster, Instagram feed, retail launch.\nDigital product proof: make the product UI, workflow state, and interface feedback the visual evidence.\nUI fidelity: use sparse, plausible labels and placeholder data only; do not invent real customer names, private data, or unsupported metrics.\nDo not drift into generic abstract SaaS imagery when UI/product proof is requested.\nFocus: identity, drop energy, and visual memorability.\nDecision being supported: whether the campaign should use street-fashion codes.\nReusable prompt pattern: Create a streetwear drop poster image ad for LouisianAI Source-Cited Growth Kit. Use gritty urban texture, fashion lighting, bold type, and the supplied brand palette and material cues accents to communicate the approved primary benefit in the product facts or drop energy. Add only exact supplied drop copy, dates, or CTA. Preserve product form and graphics exactly. Avoid the avoid list and fidelity risks in the product facts. Product facts: Business: LouisianAI. Objective: Grow source-cited organic and AI-engine visibility for louisianai.com while keeping claims evidence-grounded. Audience: Louisiana business, policy, utility, CRE, data-center, and economic-development readers. Location: Louisiana. Channels: SEO, AEO, social sharing, embeds, feeds, AI-reader files, newsletter capture. Product proof objects: source-linked tracker, project profiles, LPSC docket tracker, compare pages, embed kit, llms.txt, openapi.json, linkset.json, citation.json, assets.json, scenes.json, shots.json, brand.json, polish.json, RSS and JSON feeds. Approved readable copy must come only from campaign manifest copy blocks. Constraints: no unsupported subscriber/readership/traffic/citation/adoption/ranking/performance/savings/rate-impact claims; preserve source confidence labels, exact public-record language, docket identifiers, and canonical URLs; no partner logos, official seals, fake AI-engine screenshots, fake analytics, testimonials, or invented source counts.\nCopy rules: headline: Use exact supplied drop name or headline only.; supportingText: Use dates or scarcity language only if supplied.; cta: Optional exact drop CTA..\nInclude: oversized product or model, street texture, bold condensed typography, date or drop placeholder, sticker or wheatpaste accents.\nConstraints: do not invent limited quantities or dates; avoid direct brand mimicry; keep product graphics readable; make typography intentional; do not add subtitles, body-copy captions, explanatory footer text, or small descriptive text unless the user supplied exact copy for it; keep text sparse; use short labels, UI placeholder blocks, or visual markers only when needed; keep the product UI, workflow, and product-proof cues recognizable.\nAvoid: fake collaboration logos, counterfeit luxury cues, unreadable graffiti, product covered by stickers; fake endorsements; unsupported claims; misspelled large text; watermarks; clutter; other brands."},{"id":"out-of-home-city-takeover","index":16,"title":"Out Of Home City Takeover","category":"OOH / Environmental","size":"1536x1024","output":"16-out-of-home-city-takeover.png","prompt":"Create one polished business visual review image for the prompt family: Out Of Home City Takeover.\nDigital product anchor: LouisianAI Source-Cited Growth Kit.\nProduct UI and workflow facts to preserve: Business: LouisianAI. Objective: Grow source-cited organic and AI-engine visibility for louisianai.com while keeping claims evidence-grounded. Audience: Louisiana business, policy, utility, CRE, data-center, and economic-development readers. Location: Louisiana. Channels: SEO, AEO, social sharing, embeds, feeds, AI-reader files, newsletter capture. Product proof objects: source-linked tracker, project profiles, LPSC docket tracker, compare pages, embed kit, llms.txt, openapi.json, linkset.json, citation.json, assets.json, scenes.json, shots.json, brand.json, polish.json, RSS and JSON feeds. Approved readable copy must come only from campaign manifest copy blocks. Constraints: no unsupported subscriber/readership/traffic/citation/adoption/ranking/performance/savings/rate-impact claims; preserve source confidence labels, exact public-record language, docket identifiers, and canonical URLs; no partner logos, official seals, fake AI-engine screenshots, fake analytics, testimonials, or invented source counts.\nThe visual must be clearly about this digital product and should not introduce another digital product, app, SaaS workflow, or UI category.\nFamily intent: A public-space ad visualization showing the campaign on billboards, transit shelters, kiosks, or building wraps with realistic scale.\nBusiness goal: test whether the ad idea has enough simplicity and scale for out-of-home placement.\nScene: a city street, transit station, airport corridor, or retail district with one or more large ad placements integrated into real architecture.\nAd format: billboard and street placement mockup.\nHuman presence: public scale context only.\nRendering mode: photoreal environmental mockup.\nChannel fit: OOH pitch, launch recap, brand film still, sales deck.\nDigital product proof: make the product UI, workflow state, and interface feedback the visual evidence.\nUI fidelity: use sparse, plausible labels and placeholder data only; do not invent real customer names, private data, or unsupported metrics.\nDo not drift into generic abstract SaaS imagery when UI/product proof is requested.\nFocus: public readability, brand scale, and campaign presence.\nDecision being supported: whether the concept can graduate to OOH planning.\nReusable prompt pattern: Create a photoreal out-of-home city takeover mockup for LouisianAI Source-Cited Growth Kit. Integrate the campaign image into billboards, transit shelters, kiosks, or building wraps in a plausible public environment. Keep the ad simple, readable, and aligned to the supplied brand palette and material cues. Use exact supplied copy only. Avoid the avoid list and fidelity risks in the product facts. Product facts: Business: LouisianAI. Objective: Grow source-cited organic and AI-engine visibility for louisianai.com while keeping claims evidence-grounded. Audience: Louisiana business, policy, utility, CRE, data-center, and economic-development readers. Location: Louisiana. Channels: SEO, AEO, social sharing, embeds, feeds, AI-reader files, newsletter capture. Product proof objects: source-linked tracker, project profiles, LPSC docket tracker, compare pages, embed kit, llms.txt, openapi.json, linkset.json, citation.json, assets.json, scenes.json, shots.json, brand.json, polish.json, RSS and JSON feeds. Approved readable copy must come only from campaign manifest copy blocks. Constraints: no unsupported subscriber/readership/traffic/citation/adoption/ranking/performance/savings/rate-impact claims; preserve source confidence labels, exact public-record language, docket identifiers, and canonical URLs; no partner logos, official seals, fake AI-engine screenshots, fake analytics, testimonials, or invented source counts.\nCopy rules: headline: Use one exact short headline only.; supportingText: Avoid long copy.; cta: Use URL or CTA only if supplied..\nInclude: large billboard or transit placement, street scale cues, simple campaign visual, safe margins, ambient pedestrians or cars.\nConstraints: do not imply real media placement; avoid real city landmarks unless supplied; keep text readable at distance; do not invent permits or partner logos; do not add subtitles, body-copy captions, explanatory footer text, or small descriptive text unless the user supplied exact copy for it; keep text sparse; use short labels, UI placeholder blocks, or visual markers only when needed; keep the product UI, workflow, and product-proof cues recognizable.\nAvoid: busy tiny text, impossible billboard geometry, fake event sponsorship, distorted ad panels; fake endorsements; unsupported claims; misspelled large text; watermarks; clutter; other brands."},{"id":"ecommerce-bundle-hero","index":17,"title":"Ecommerce Bundle Hero","category":"Ecommerce / Merchandising","size":"1536x1024","output":"17-ecommerce-bundle-hero.png","prompt":"Create one polished business visual review image for the prompt family: Ecommerce Bundle Hero.\nDigital product anchor: LouisianAI Source-Cited Growth Kit.\nProduct UI and workflow facts to preserve: Business: LouisianAI. Objective: Grow source-cited organic and AI-engine visibility for louisianai.com while keeping claims evidence-grounded. Audience: Louisiana business, policy, utility, CRE, data-center, and economic-development readers. Location: Louisiana. Channels: SEO, AEO, social sharing, embeds, feeds, AI-reader files, newsletter capture. Product proof objects: source-linked tracker, project profiles, LPSC docket tracker, compare pages, embed kit, llms.txt, openapi.json, linkset.json, citation.json, assets.json, scenes.json, shots.json, brand.json, polish.json, RSS and JSON feeds. Approved readable copy must come only from campaign manifest copy blocks. Constraints: no unsupported subscriber/readership/traffic/citation/adoption/ranking/performance/savings/rate-impact claims; preserve source confidence labels, exact public-record language, docket identifiers, and canonical URLs; no partner logos, official seals, fake AI-engine screenshots, fake analytics, testimonials, or invented source counts.\nThe visual must be clearly about this digital product and should not introduce another digital product, app, SaaS workflow, or UI category.\nFamily intent: A clean ecommerce ad showing the subject, bundle contents, scale, variants, or included items with high shopping clarity.\nBusiness goal: make the offer easy to understand at purchase point.\nScene: a bright product layout with hero item, optional bundle components, variant cues, included accessories, and clean benefit icons or placeholders.\nAd format: PDP and marketplace hero image.\nHuman presence: none.\nRendering mode: clean commercial product photography.\nChannel fit: Amazon module, Shopify PDP, retail marketplace, email commerce.\nDigital product proof: make the product UI, workflow state, and interface feedback the visual evidence.\nUI fidelity: use sparse, plausible labels and placeholder data only; do not invent real customer names, private data, or unsupported metrics.\nDo not drift into generic abstract SaaS imagery when UI/product proof is requested.\nFocus: what is included, what it looks like, and why it is worth buying.\nDecision being supported: whether ecommerce clarity should be prioritized over lifestyle storytelling.\nReusable prompt pattern: Create an ecommerce bundle hero ad for LouisianAI Source-Cited Growth Kit. Arrange the product, included items, variants, or accessories in a clean shoppable layout with the supplied brand palette and material cues, realistic shadows, and high product clarity. Use exact supplied item labels only. Preserve package, logo, and proportions exactly. Avoid the avoid list and fidelity risks in the product facts. Product facts: Business: LouisianAI. Objective: Grow source-cited organic and AI-engine visibility for louisianai.com while keeping claims evidence-grounded. Audience: Louisiana business, policy, utility, CRE, data-center, and economic-development readers. Location: Louisiana. Channels: SEO, AEO, social sharing, embeds, feeds, AI-reader files, newsletter capture. Product proof objects: source-linked tracker, project profiles, LPSC docket tracker, compare pages, embed kit, llms.txt, openapi.json, linkset.json, citation.json, assets.json, scenes.json, shots.json, brand.json, polish.json, RSS and JSON feeds. Approved readable copy must come only from campaign manifest copy blocks. Constraints: no unsupported subscriber/readership/traffic/citation/adoption/ranking/performance/savings/rate-impact claims; preserve source confidence labels, exact public-record language, docket identifiers, and canonical URLs; no partner logos, official seals, fake AI-engine screenshots, fake analytics, testimonials, or invented source counts.\nCopy rules: headline: Use exact product or offer name only.; supportingText: Use exact included-item labels only.; cta: Usually omit CTA..\nInclude: main product hero, bundle or variant layout, scale cue, simple icon placeholders, clean shadow, offer label zone.\nConstraints: do not invent bundle contents; keep product count accurate; avoid lifestyle clutter; make all items legible; do not add subtitles, body-copy captions, explanatory footer text, or small descriptive text unless the user supplied exact copy for it; keep text sparse; use short labels, UI placeholder blocks, or visual markers only when needed; keep the product UI, workflow, and product-proof cues recognizable.\nAvoid: fake accessories, impossible scale, marketplace badges, distorted packaging, made-up discounts; fake endorsements; unsupported claims; misspelled large text; watermarks; clutter; other brands."},{"id":"testimonial-proof-wall","index":18,"title":"Testimonial Proof Wall","category":"Proof / Social","size":"1536x1024","output":"18-testimonial-proof-wall.png","prompt":"Create one polished business visual review image for the prompt family: Testimonial Proof Wall.\nDigital product anchor: LouisianAI Source-Cited Growth Kit.\nProduct UI and workflow facts to preserve: Business: LouisianAI. Objective: Grow source-cited organic and AI-engine visibility for louisianai.com while keeping claims evidence-grounded. Audience: Louisiana business, policy, utility, CRE, data-center, and economic-development readers. Location: Louisiana. Channels: SEO, AEO, social sharing, embeds, feeds, AI-reader files, newsletter capture. Product proof objects: source-linked tracker, project profiles, LPSC docket tracker, compare pages, embed kit, llms.txt, openapi.json, linkset.json, citation.json, assets.json, scenes.json, shots.json, brand.json, polish.json, RSS and JSON feeds. Approved readable copy must come only from campaign manifest copy blocks. Constraints: no unsupported subscriber/readership/traffic/citation/adoption/ranking/performance/savings/rate-impact claims; preserve source confidence labels, exact public-record language, docket identifiers, and canonical URLs; no partner logos, official seals, fake AI-engine screenshots, fake analytics, testimonials, or invented source counts.\nThe visual must be clearly about this digital product and should not introduce another digital product, app, SaaS workflow, or UI category.\nFamily intent: A proof-led ad that visualizes reviews, quotes, customer logos, or outcome snippets as a structured wall without inventing evidence.\nBusiness goal: show credibility and momentum using approved proof assets.\nScene: a clean wall, dashboard, board, or editorial layout with subject hero and proof cards arranged around it.\nAd format: review and quote visualization.\nHuman presence: optional real customer portrait only if supplied.\nRendering mode: polished editorial composite.\nChannel fit: B2B social, landing social proof, retargeting, sales follow-up.\nDigital product proof: make the product UI, workflow state, and interface feedback the visual evidence.\nUI fidelity: use sparse, plausible labels and placeholder data only; do not invent real customer names, private data, or unsupported metrics.\nDo not drift into generic abstract SaaS imagery when UI/product proof is requested.\nFocus: trust, validation, and repeated positive signal.\nDecision being supported: whether proof should lead the ad instead of product beauty or lifestyle.\nReusable prompt pattern: Create a testimonial proof wall image ad for LouisianAI Source-Cited Growth Kit. Arrange approved quote cards, review snippets, customer proof, or placeholder proof modules around the subject. Use the supplied brand palette and material cues and clear hierarchy. Do not invent customers, ratings, logos, or metrics. Use exact supplied proof only. Avoid the avoid list and fidelity risks in the product facts. Product facts: Business: LouisianAI. Objective: Grow source-cited organic and AI-engine visibility for louisianai.com while keeping claims evidence-grounded. Audience: Louisiana business, policy, utility, CRE, data-center, and economic-development readers. Location: Louisiana. Channels: SEO, AEO, social sharing, embeds, feeds, AI-reader files, newsletter capture. Product proof objects: source-linked tracker, project profiles, LPSC docket tracker, compare pages, embed kit, llms.txt, openapi.json, linkset.json, citation.json, assets.json, scenes.json, shots.json, brand.json, polish.json, RSS and JSON feeds. Approved readable copy must come only from campaign manifest copy blocks. Constraints: no unsupported subscriber/readership/traffic/citation/adoption/ranking/performance/savings/rate-impact claims; preserve source confidence labels, exact public-record language, docket identifiers, and canonical URLs; no partner logos, official seals, fake AI-engine screenshots, fake analytics, testimonials, or invented source counts.\nCopy rules: headline: Use exact supplied proof headline only.; supportingText: Use only real supplied quotes, names, logos, or abstract placeholders.; cta: Use exact supplied CTA only..\nInclude: subject hero, quote cards, review placeholders, logo-safe zones, source labels, small CTA.\nConstraints: never invent endorsements; use placeholders when proof is missing; avoid fake profile photos; keep claims reviewable; do not add subtitles, body-copy captions, explanatory footer text, or small descriptive text unless the user supplied exact copy for it; keep text sparse; use short labels, UI placeholder blocks, or visual markers only when needed; keep the product UI, workflow, and product-proof cues recognizable.\nAvoid: fake five-star reviews, made-up customer logos, fabricated metrics, dense unreadable quote walls; fake endorsements; unsupported claims; misspelled large text; watermarks; clutter; other brands."},{"id":"founder-operator-desk-ad","index":19,"title":"Founder Operator Desk Ad","category":"B2B / Human Trust","size":"1536x1024","output":"19-founder-operator-desk-ad.png","prompt":"Create one polished business visual review image for the prompt family: Founder Operator Desk Ad.\nDigital product anchor: LouisianAI Source-Cited Growth Kit.\nProduct UI and workflow facts to preserve: Business: LouisianAI. Objective: Grow source-cited organic and AI-engine visibility for louisianai.com while keeping claims evidence-grounded. Audience: Louisiana business, policy, utility, CRE, data-center, and economic-development readers. Location: Louisiana. Channels: SEO, AEO, social sharing, embeds, feeds, AI-reader files, newsletter capture. Product proof objects: source-linked tracker, project profiles, LPSC docket tracker, compare pages, embed kit, llms.txt, openapi.json, linkset.json, citation.json, assets.json, scenes.json, shots.json, brand.json, polish.json, RSS and JSON feeds. Approved readable copy must come only from campaign manifest copy blocks. Constraints: no unsupported subscriber/readership/traffic/citation/adoption/ranking/performance/savings/rate-impact claims; preserve source confidence labels, exact public-record language, docket identifiers, and canonical URLs; no partner logos, official seals, fake AI-engine screenshots, fake analytics, testimonials, or invented source counts.\nThe visual must be clearly about this digital product and should not introduce another digital product, app, SaaS workflow, or UI category.\nFamily intent: An expert or operator-led ad where a credible person works with the subject in a real workspace, counter, lab, studio, or field context.\nBusiness goal: make the offer feel expert-backed, operational, and grounded in real use.\nScene: a desk, workshop, clinic, kitchen, studio, lab, or field workspace with the person mid-task and the subject clearly placed as the tool or offer.\nAd format: operator-led editorial ad.\nHuman presence: one founder, operator, clinician, expert, or employee when appropriate.\nRendering mode: photoreal editorial portrait.\nChannel fit: LinkedIn, B2B launch, newsletter, trust campaign.\nDigital product proof: make the product UI, workflow state, and interface feedback the visual evidence.\nUI fidelity: use sparse, plausible labels and placeholder data only; do not invent real customer names, private data, or unsupported metrics.\nDo not drift into generic abstract SaaS imagery when UI/product proof is requested.\nFocus: credibility, craft, and hands-on use.\nDecision being supported: whether human expertise should anchor the campaign.\nReusable prompt pattern: Create an operator-led editorial image ad for LouisianAI Source-Cited Growth Kit. Show a credible the target audience described in the product facts expert or operator using or presenting the subject in a real workspace. Use natural light, honest texture, and the supplied brand palette and material cues accents. Add exact supplied quote or headline only. Preserve the subject exactly. Avoid the avoid list and fidelity risks in the product facts. Product facts: Business: LouisianAI. Objective: Grow source-cited organic and AI-engine visibility for louisianai.com while keeping claims evidence-grounded. Audience: Louisiana business, policy, utility, CRE, data-center, and economic-development readers. Location: Louisiana. Channels: SEO, AEO, social sharing, embeds, feeds, AI-reader files, newsletter capture. Product proof objects: source-linked tracker, project profiles, LPSC docket tracker, compare pages, embed kit, llms.txt, openapi.json, linkset.json, citation.json, assets.json, scenes.json, shots.json, brand.json, polish.json, RSS and JSON feeds. Approved readable copy must come only from campaign manifest copy blocks. Constraints: no unsupported subscriber/readership/traffic/citation/adoption/ranking/performance/savings/rate-impact claims; preserve source confidence labels, exact public-record language, docket identifiers, and canonical URLs; no partner logos, official seals, fake AI-engine screenshots, fake analytics, testimonials, or invented source counts.\nCopy rules: headline: Use exact quote or headline only.; supportingText: Do not name a person unless supplied.; cta: Optional exact CTA..\nInclude: credible operator, work surface, subject in use, real tools or notes, small headline or quote zone.\nConstraints: do not invent names, credentials, or employers; avoid fake lab or medical authority; keep workspace relevant; show the subject clearly; do not add subtitles, body-copy captions, explanatory footer text, or small descriptive text unless the user supplied exact copy for it; keep text sparse; use short labels, UI placeholder blocks, or visual markers only when needed; keep the product UI, workflow, and product-proof cues recognizable.\nAvoid: stock handshake energy, staged corporate cliches, false expertise, over-polished office scenes; fake endorsements; unsupported claims; misspelled large text; watermarks; clutter; other brands."},{"id":"retro-print-classified","index":20,"title":"Retro Print Classified","category":"Retro / Print","size":"1024x1536","output":"20-retro-print-classified.png","prompt":"Create one polished business visual review image for the prompt family: Retro Print Classified.\nDigital product anchor: LouisianAI Source-Cited Growth Kit.\nProduct UI and workflow facts to preserve: Business: LouisianAI. Objective: Grow source-cited organic and AI-engine visibility for louisianai.com while keeping claims evidence-grounded. Audience: Louisiana business, policy, utility, CRE, data-center, and economic-development readers. Location: Louisiana. Channels: SEO, AEO, social sharing, embeds, feeds, AI-reader files, newsletter capture. Product proof objects: source-linked tracker, project profiles, LPSC docket tracker, compare pages, embed kit, llms.txt, openapi.json, linkset.json, citation.json, assets.json, scenes.json, shots.json, brand.json, polish.json, RSS and JSON feeds. Approved readable copy must come only from campaign manifest copy blocks. Constraints: no unsupported subscriber/readership/traffic/citation/adoption/ranking/performance/savings/rate-impact claims; preserve source confidence labels, exact public-record language, docket identifiers, and canonical URLs; no partner logos, official seals, fake AI-engine screenshots, fake analytics, testimonials, or invented source counts.\nThe visual must be clearly about this digital product and should not introduce another digital product, app, SaaS workflow, or UI category.\nFamily intent: A vintage print ad route using halftone, catalog layouts, coupons, serif type, linework, and aged paper texture while preserving modern product truth.\nBusiness goal: test whether nostalgia and print credibility can make the offer feel familiar and memorable.\nScene: a newspaper, catalog page, coupon card, or magazine spread with the subject rendered or photographed cleanly and surrounded by period-inspired layout.\nAd format: vintage newspaper or catalog ad.\nHuman presence: optional illustration-like figure.\nRendering mode: print-inspired mixed media.\nChannel fit: nostalgia campaign, poster, social static, editorial insert.\nDigital product proof: make the product UI, workflow state, and interface feedback the visual evidence.\nUI fidelity: use sparse, plausible labels and placeholder data only; do not invent real customer names, private data, or unsupported metrics.\nDo not drift into generic abstract SaaS imagery when UI/product proof is requested.\nFocus: nostalgia, clarity, and distinctive print texture.\nDecision being supported: whether a retro route offers enough differentiation for the audience.\nReusable prompt pattern: Create a retro print classified image ad for LouisianAI Source-Cited Growth Kit. Use vintage newspaper, catalog, or coupon layout cues with halftone texture, serif typography, and the supplied brand palette and material cues adapted to aged print. Preserve the product exactly and use exact supplied copy only. Avoid the avoid list and fidelity risks in the product facts. Product facts: Business: LouisianAI. Objective: Grow source-cited organic and AI-engine visibility for louisianai.com while keeping claims evidence-grounded. Audience: Louisiana business, policy, utility, CRE, data-center, and economic-development readers. Location: Louisiana. Channels: SEO, AEO, social sharing, embeds, feeds, AI-reader files, newsletter capture. Product proof objects: source-linked tracker, project profiles, LPSC docket tracker, compare pages, embed kit, llms.txt, openapi.json, linkset.json, citation.json, assets.json, scenes.json, shots.json, brand.json, polish.json, RSS and JSON feeds. Approved readable copy must come only from campaign manifest copy blocks. Constraints: no unsupported subscriber/readership/traffic/citation/adoption/ranking/performance/savings/rate-impact claims; preserve source confidence labels, exact public-record language, docket identifiers, and canonical URLs; no partner logos, official seals, fake AI-engine screenshots, fake analytics, testimonials, or invented source counts.\nCopy rules: headline: Use exact supplied headline in period-style type.; supportingText: Use placeholder body copy unless supplied.; cta: Use coupon or URL only if supplied..\nInclude: halftone texture, catalog frame, coupon or offer box, serif headline, product engraving or photo.\nConstraints: avoid offensive or exclusionary vintage stereotypes; do not add fake prices or coupon codes; keep product modern and accurate; make text intentionally sparse; do not add subtitles, body-copy captions, explanatory footer text, or small descriptive text unless the user supplied exact copy for it; keep text sparse; use short labels, UI placeholder blocks, or visual markers only when needed; keep the product UI, workflow, and product-proof cues recognizable.\nAvoid: unreadable tiny newspaper copy, fake legal terms, caricatured people, distressed product; fake endorsements; unsupported claims; misspelled large text; watermarks; clutter; other brands."},{"id":"sticker-badge-social-native","index":21,"title":"Sticker Badge Social Native","category":"Social Native / Sticker","size":"1024x1024","output":"21-sticker-badge-social-native.png","prompt":"Create one polished business visual review image for the prompt family: Sticker Badge Social Native.\nDigital product anchor: LouisianAI Source-Cited Growth Kit.\nProduct UI and workflow facts to preserve: Business: LouisianAI. Objective: Grow source-cited organic and AI-engine visibility for louisianai.com while keeping claims evidence-grounded. Audience: Louisiana business, policy, utility, CRE, data-center, and economic-development readers. Location: Louisiana. Channels: SEO, AEO, social sharing, embeds, feeds, AI-reader files, newsletter capture. Product proof objects: source-linked tracker, project profiles, LPSC docket tracker, compare pages, embed kit, llms.txt, openapi.json, linkset.json, citation.json, assets.json, scenes.json, shots.json, brand.json, polish.json, RSS and JSON feeds. Approved readable copy must come only from campaign manifest copy blocks. Constraints: no unsupported subscriber/readership/traffic/citation/adoption/ranking/performance/savings/rate-impact claims; preserve source confidence labels, exact public-record language, docket identifiers, and canonical URLs; no partner logos, official seals, fake AI-engine screenshots, fake analytics, testimonials, or invented source counts.\nThe visual must be clearly about this digital product and should not introduce another digital product, app, SaaS workflow, or UI category.\nFamily intent: A social-native layout with the subject surrounded by crisp stickers, badges, emoji-like marks, and short callouts that feel casual but controlled.\nBusiness goal: test a playful platform-native route while preserving approved copy and product fidelity.\nScene: a clean product or lifestyle image overlaid with sticker badges, reaction marks, arrows, and short labels in brand colors.\nAd format: feed-native sticker composition.\nHuman presence: optional cropped user.\nRendering mode: photoreal plus graphic sticker overlay.\nChannel fit: Instagram feed, Snap, TikTok static, creator ad.\nDigital product proof: make the product UI, workflow state, and interface feedback the visual evidence.\nUI fidelity: use sparse, plausible labels and placeholder data only; do not invent real customer names, private data, or unsupported metrics.\nDo not drift into generic abstract SaaS imagery when UI/product proof is requested.\nFocus: platform-native attention and quick benefit cues.\nDecision being supported: whether the ad should look like native creator content rather than a formal brand asset.\nReusable prompt pattern: Create a sticker-badge social-native image ad for LouisianAI Source-Cited Growth Kit. Keep the subject clear, then add crisp sticker badges, arrows, reaction marks, and short exact callouts in the supplied brand palette and material cues. Make it casual and platform-native without adding fake handles, reviews, or claims. Preserve the subject exactly. Avoid the avoid list and fidelity risks in the product facts. Product facts: Business: LouisianAI. Objective: Grow source-cited organic and AI-engine visibility for louisianai.com while keeping claims evidence-grounded. Audience: Louisiana business, policy, utility, CRE, data-center, and economic-development readers. Location: Louisiana. Channels: SEO, AEO, social sharing, embeds, feeds, AI-reader files, newsletter capture. Product proof objects: source-linked tracker, project profiles, LPSC docket tracker, compare pages, embed kit, llms.txt, openapi.json, linkset.json, citation.json, assets.json, scenes.json, shots.json, brand.json, polish.json, RSS and JSON feeds. Approved readable copy must come only from campaign manifest copy blocks. Constraints: no unsupported subscriber/readership/traffic/citation/adoption/ranking/performance/savings/rate-impact claims; preserve source confidence labels, exact public-record language, docket identifiers, and canonical URLs; no partner logos, official seals, fake AI-engine screenshots, fake analytics, testimonials, or invented source counts.\nCopy rules: headline: Use exact supplied short headline or sticker callout.; supportingText: Use no more than four short exact callouts.; cta: Optional exact CTA sticker..\nInclude: subject hero, sticker badges, arrow marks, short exact callouts, casual background, small CTA.\nConstraints: do not use copyrighted emoji or platform UI; keep stickers off product labels; limit callouts; avoid fake social metrics; do not add subtitles, body-copy captions, explanatory footer text, or small descriptive text unless the user supplied exact copy for it; keep text sparse; use short labels, UI placeholder blocks, or visual markers only when needed; keep the product UI, workflow, and product-proof cues recognizable.\nAvoid: cluttered sticker spam, unreadable labels, fake likes or comments, childish tone for serious categories; fake endorsements; unsupported claims; misspelled large text; watermarks; clutter; other brands."},{"id":"ai-generated-world-extension","index":22,"title":"World Extension Product Fantasy","category":"Surreal / World Building","size":"1536x1024","output":"22-ai-generated-world-extension.png","prompt":"Create one polished business visual review image for the prompt family: World Extension Product Fantasy.\nDigital product anchor: LouisianAI Source-Cited Growth Kit.\nProduct UI and workflow facts to preserve: Business: LouisianAI. Objective: Grow source-cited organic and AI-engine visibility for louisianai.com while keeping claims evidence-grounded. Audience: Louisiana business, policy, utility, CRE, data-center, and economic-development readers. Location: Louisiana. Channels: SEO, AEO, social sharing, embeds, feeds, AI-reader files, newsletter capture. Product proof objects: source-linked tracker, project profiles, LPSC docket tracker, compare pages, embed kit, llms.txt, openapi.json, linkset.json, citation.json, assets.json, scenes.json, shots.json, brand.json, polish.json, RSS and JSON feeds. Approved readable copy must come only from campaign manifest copy blocks. Constraints: no unsupported subscriber/readership/traffic/citation/adoption/ranking/performance/savings/rate-impact claims; preserve source confidence labels, exact public-record language, docket identifiers, and canonical URLs; no partner logos, official seals, fake AI-engine screenshots, fake analytics, testimonials, or invented source counts.\nThe visual must be clearly about this digital product and should not introduce another digital product, app, SaaS workflow, or UI category.\nFamily intent: A surreal world where the subject's material, pattern, flavor, ingredient, or feature becomes a landscape or architecture.\nBusiness goal: test whether the product can support a distinctive campaign world.\nScene: an immersive landscape, room, city, terrain, or miniature world generated from the subject's colors, material, texture, or benefit metaphor.\nAd format: immersive product world.\nHuman presence: none or tiny scale figures.\nRendering mode: photoreal surreal commercial.\nChannel fit: hero campaign, landing page, OOH, brand world exploration.\nDigital product proof: make the product UI, workflow state, and interface feedback the visual evidence.\nUI fidelity: use sparse, plausible labels and placeholder data only; do not invent real customer names, private data, or unsupported metrics.\nDo not drift into generic abstract SaaS imagery when UI/product proof is requested.\nFocus: brand world, memorability, and ownable metaphor.\nDecision being supported: whether to build a larger visual system around the subject.\nReusable prompt pattern: Create an immersive product-world image ad for LouisianAI Source-Cited Growth Kit. Transform the subject's truthful material, color, texture, ingredient, or benefit metaphor into a surreal environment while keeping the actual subject visible and accurate. Use the supplied brand palette and material cues, atmospheric depth, and copy-safe space. Add exact supplied text only. Avoid the avoid list and fidelity risks in the product facts. Product facts: Business: LouisianAI. Objective: Grow source-cited organic and AI-engine visibility for louisianai.com while keeping claims evidence-grounded. Audience: Louisiana business, policy, utility, CRE, data-center, and economic-development readers. Location: Louisiana. Channels: SEO, AEO, social sharing, embeds, feeds, AI-reader files, newsletter capture. Product proof objects: source-linked tracker, project profiles, LPSC docket tracker, compare pages, embed kit, llms.txt, openapi.json, linkset.json, citation.json, assets.json, scenes.json, shots.json, brand.json, polish.json, RSS and JSON feeds. Approved readable copy must come only from campaign manifest copy blocks. Constraints: no unsupported subscriber/readership/traffic/citation/adoption/ranking/performance/savings/rate-impact claims; preserve source confidence labels, exact public-record language, docket identifiers, and canonical URLs; no partner logos, official seals, fake AI-engine screenshots, fake analytics, testimonials, or invented source counts.\nCopy rules: headline: Use no text or one exact campaign line.; supportingText: Avoid labels.; cta: Omit CTA unless requested..\nInclude: subject as hero or landscape source, material-scale world, tiny environmental details, atmospheric lighting, copy-safe space.\nConstraints: keep the metaphor tied to real subject cues; do not replace the product with a different object; avoid impossible claims; make the world inspectable; do not add subtitles, body-copy captions, explanatory footer text, or small descriptive text unless the user supplied exact copy for it; keep text sparse; use short labels, UI placeholder blocks, or visual markers only when needed; keep the product UI, workflow, and product-proof cues recognizable.\nAvoid: abstract blob landscapes, product lost in scene, unrelated fantasy creatures, generic AI dream texture; fake endorsements; unsupported claims; misspelled large text; watermarks; clutter; other brands."},{"id":"sustainability-material-proof","index":23,"title":"Sustainability Material Proof","category":"Proof / Materials","size":"1536x1024","output":"23-sustainability-material-proof.png","prompt":"Create one polished business visual review image for the prompt family: Sustainability Material Proof.\nDigital product anchor: LouisianAI Source-Cited Growth Kit.\nProduct UI and workflow facts to preserve: Business: LouisianAI. Objective: Grow source-cited organic and AI-engine visibility for louisianai.com while keeping claims evidence-grounded. Audience: Louisiana business, policy, utility, CRE, data-center, and economic-development readers. Location: Louisiana. Channels: SEO, AEO, social sharing, embeds, feeds, AI-reader files, newsletter capture. Product proof objects: source-linked tracker, project profiles, LPSC docket tracker, compare pages, embed kit, llms.txt, openapi.json, linkset.json, citation.json, assets.json, scenes.json, shots.json, brand.json, polish.json, RSS and JSON feeds. Approved readable copy must come only from campaign manifest copy blocks. Constraints: no unsupported subscriber/readership/traffic/citation/adoption/ranking/performance/savings/rate-impact claims; preserve source confidence labels, exact public-record language, docket identifiers, and canonical URLs; no partner logos, official seals, fake AI-engine screenshots, fake analytics, testimonials, or invented source counts.\nThe visual must be clearly about this digital product and should not introduce another digital product, app, SaaS workflow, or UI category.\nFamily intent: A proof-oriented ad showing materials, sourcing, packaging, repairability, refill, or lifecycle cues without inventing environmental claims.\nBusiness goal: make responsible design or material choices tangible and reviewable.\nScene: a clean material board, sourcing table, workshop, farm, lab, or refill station with the subject and documented material cues.\nAd format: source and material story ad.\nHuman presence: optional hands or field worker if supplied.\nRendering mode: photoreal editorial proof layout.\nChannel fit: brand trust, packaging story, retail education, B2B sales.\nDigital product proof: make the product UI, workflow state, and interface feedback the visual evidence.\nUI fidelity: use sparse, plausible labels and placeholder data only; do not invent real customer names, private data, or unsupported metrics.\nDo not drift into generic abstract SaaS imagery when UI/product proof is requested.\nFocus: trust, material detail, and responsible choice.\nDecision being supported: whether sustainability or material proof should be part of the campaign.\nReusable prompt pattern: Create a sustainability material proof image ad for LouisianAI Source-Cited Growth Kit. Show the subject with truthful material, sourcing, refill, repair, packaging, or lifecycle cues from the brief. Use documentation-style composition, the supplied brand palette and material cues, and exact approved claims only. Do not invent certifications. Avoid the avoid list and fidelity risks in the product facts. Product facts: Business: LouisianAI. Objective: Grow source-cited organic and AI-engine visibility for louisianai.com while keeping claims evidence-grounded. Audience: Louisiana business, policy, utility, CRE, data-center, and economic-development readers. Location: Louisiana. Channels: SEO, AEO, social sharing, embeds, feeds, AI-reader files, newsletter capture. Product proof objects: source-linked tracker, project profiles, LPSC docket tracker, compare pages, embed kit, llms.txt, openapi.json, linkset.json, citation.json, assets.json, scenes.json, shots.json, brand.json, polish.json, RSS and JSON feeds. Approved readable copy must come only from campaign manifest copy blocks. Constraints: no unsupported subscriber/readership/traffic/citation/adoption/ranking/performance/savings/rate-impact claims; preserve source confidence labels, exact public-record language, docket identifiers, and canonical URLs; no partner logos, official seals, fake AI-engine screenshots, fake analytics, testimonials, or invented source counts.\nCopy rules: headline: Use exact approved claim only.; supportingText: Use placeholders for certifications unless supplied.; cta: Optional exact learn-more CTA..\nInclude: subject hero, material samples, source or lifecycle markers, certification placeholder, documentation-style caption.\nConstraints: do not imply carbon, recycled, organic, or ethical claims unless supplied; label unknown proof as placeholder; keep materials relevant; avoid greenwashing imagery; do not add subtitles, body-copy captions, explanatory footer text, or small descriptive text unless the user supplied exact copy for it; keep text sparse; use short labels, UI placeholder blocks, or visual markers only when needed; keep the product UI, workflow, and product-proof cues recognizable.\nAvoid: fake leaves and badges, unsupported eco claims, invented certifications, vague planet-saving slogans; fake endorsements; unsupported claims; misspelled large text; watermarks; clutter; other brands."},{"id":"event-launch-countdown","index":24,"title":"Event Launch Countdown","category":"Launch / Event","size":"1024x1536","output":"24-event-launch-countdown.png","prompt":"Create one polished business visual review image for the prompt family: Event Launch Countdown.\nDigital product anchor: LouisianAI Source-Cited Growth Kit.\nProduct UI and workflow facts to preserve: Business: LouisianAI. Objective: Grow source-cited organic and AI-engine visibility for louisianai.com while keeping claims evidence-grounded. Audience: Louisiana business, policy, utility, CRE, data-center, and economic-development readers. Location: Louisiana. Channels: SEO, AEO, social sharing, embeds, feeds, AI-reader files, newsletter capture. Product proof objects: source-linked tracker, project profiles, LPSC docket tracker, compare pages, embed kit, llms.txt, openapi.json, linkset.json, citation.json, assets.json, scenes.json, shots.json, brand.json, polish.json, RSS and JSON feeds. Approved readable copy must come only from campaign manifest copy blocks. Constraints: no unsupported subscriber/readership/traffic/citation/adoption/ranking/performance/savings/rate-impact claims; preserve source confidence labels, exact public-record language, docket identifiers, and canonical URLs; no partner logos, official seals, fake AI-engine screenshots, fake analytics, testimonials, or invented source counts.\nThe visual must be clearly about this digital product and should not introduce another digital product, app, SaaS workflow, or UI category.\nFamily intent: A launch or event ad with the subject, date zone, agenda cue, countdown energy, and clean registration CTA.\nBusiness goal: turn a release, webinar, demo, or event into a clear visual invitation.\nScene: a stage, digital backdrop, calendar-like graphic, product reveal setup, or event card with clear date and CTA zones.\nAd format: announcement and countdown ad.\nHuman presence: optional speaker or audience if supplied.\nRendering mode: polished event key visual.\nChannel fit: webinar promo, launch event, conference social, email header.\nDigital product proof: make the product UI, workflow state, and interface feedback the visual evidence.\nUI fidelity: use sparse, plausible labels and placeholder data only; do not invent real customer names, private data, or unsupported metrics.\nDo not drift into generic abstract SaaS imagery when UI/product proof is requested.\nFocus: what is happening, when, and why to act.\nDecision being supported: whether the subject needs an event-led campaign wrapper.\nReusable prompt pattern: Create an event launch countdown image ad for LouisianAI Source-Cited Growth Kit. Build a polished event key visual with exact supplied event name, date, time, agenda, and the exact supplied CTA or contact detail in the product facts, or no CTA if none is supplied. Use the supplied brand palette and material cues, clear hierarchy, and a credible reveal or stage environment. Preserve the subject exactly. Avoid the avoid list and fidelity risks in the product facts. Product facts: Business: LouisianAI. Objective: Grow source-cited organic and AI-engine visibility for louisianai.com while keeping claims evidence-grounded. Audience: Louisiana business, policy, utility, CRE, data-center, and economic-development readers. Location: Louisiana. Channels: SEO, AEO, social sharing, embeds, feeds, AI-reader files, newsletter capture. Product proof objects: source-linked tracker, project profiles, LPSC docket tracker, compare pages, embed kit, llms.txt, openapi.json, linkset.json, citation.json, assets.json, scenes.json, shots.json, brand.json, polish.json, RSS and JSON feeds. Approved readable copy must come only from campaign manifest copy blocks. Constraints: no unsupported subscriber/readership/traffic/citation/adoption/ranking/performance/savings/rate-impact claims; preserve source confidence labels, exact public-record language, docket identifiers, and canonical URLs; no partner logos, official seals, fake AI-engine screenshots, fake analytics, testimonials, or invented source counts.\nCopy rules: headline: Use exact event name only.; supportingText: Use date, time, speaker, and agenda only if supplied.; cta: Use exact registration CTA..\nInclude: subject or event hero, date and time zone, countdown or agenda cue, speaker placeholder, registration CTA.\nConstraints: do not invent event date, speaker, or venue; keep date text large and exact; avoid fake conference logos; preserve product or event identity; do not add subtitles, body-copy captions, explanatory footer text, or small descriptive text unless the user supplied exact copy for it; keep text sparse; use short labels, UI placeholder blocks, or visual markers only when needed; keep the product UI, workflow, and product-proof cues recognizable.\nAvoid: wrong calendar info, generic webinar stock art, fake speaker portraits, unreadable agenda text; fake endorsements; unsupported claims; misspelled large text; watermarks; clutter; other brands."},{"id":"cinematic-hands-demo","index":25,"title":"Cinematic Hands Demo","category":"Demo / Use Moment","size":"1536x1024","output":"25-cinematic-hands-demo.png","prompt":"Create one polished business visual review image for the prompt family: Cinematic Hands Demo.\nDigital product anchor: LouisianAI Source-Cited Growth Kit.\nProduct UI and workflow facts to preserve: Business: LouisianAI. Objective: Grow source-cited organic and AI-engine visibility for louisianai.com while keeping claims evidence-grounded. Audience: Louisiana business, policy, utility, CRE, data-center, and economic-development readers. Location: Louisiana. Channels: SEO, AEO, social sharing, embeds, feeds, AI-reader files, newsletter capture. Product proof objects: source-linked tracker, project profiles, LPSC docket tracker, compare pages, embed kit, llms.txt, openapi.json, linkset.json, citation.json, assets.json, scenes.json, shots.json, brand.json, polish.json, RSS and JSON feeds. Approved readable copy must come only from campaign manifest copy blocks. Constraints: no unsupported subscriber/readership/traffic/citation/adoption/ranking/performance/savings/rate-impact claims; preserve source confidence labels, exact public-record language, docket identifiers, and canonical URLs; no partner logos, official seals, fake AI-engine screenshots, fake analytics, testimonials, or invented source counts.\nThe visual must be clearly about this digital product and should not introduce another digital product, app, SaaS workflow, or UI category.\nFamily intent: A close-up image showing hands using, opening, applying, assembling, scanning, pouring, or demonstrating the subject.\nBusiness goal: make use and interaction concrete before video or full demo production.\nScene: a close working surface, counter, desk, bathroom, kitchen, retail counter, or field setup with hands naturally interacting with the subject.\nAd format: hands-in-use product demo.\nHuman presence: hands only or partial user.\nRendering mode: photoreal cinematic close-up.\nChannel fit: how-it-works ad, PDP module, social demo, email feature.\nDigital product proof: make the product UI, workflow state, and interface feedback the visual evidence.\nUI fidelity: use sparse, plausible labels and placeholder data only; do not invent real customer names, private data, or unsupported metrics.\nDo not drift into generic abstract SaaS imagery when UI/product proof is requested.\nFocus: how it is used and why it feels easy or satisfying.\nDecision being supported: whether a use-moment demo should anchor the ad.\nReusable prompt pattern: Create a cinematic hands-demo image ad for LouisianAI Source-Cited Growth Kit. Show natural hands using, opening, applying, assembling, or demonstrating the subject in a plausible setting for the target audience described in the product facts. Use close-up lighting, tactile detail, and the supplied brand palette and material cues accents. Preserve subject shape, labels, and usage truth. Avoid the avoid list and fidelity risks in the product facts. Product facts: Business: LouisianAI. Objective: Grow source-cited organic and AI-engine visibility for louisianai.com while keeping claims evidence-grounded. Audience: Louisiana business, policy, utility, CRE, data-center, and economic-development readers. Location: Louisiana. Channels: SEO, AEO, social sharing, embeds, feeds, AI-reader files, newsletter capture. Product proof objects: source-linked tracker, project profiles, LPSC docket tracker, compare pages, embed kit, llms.txt, openapi.json, linkset.json, citation.json, assets.json, scenes.json, shots.json, brand.json, polish.json, RSS and JSON feeds. Approved readable copy must come only from campaign manifest copy blocks. Constraints: no unsupported subscriber/readership/traffic/citation/adoption/ranking/performance/savings/rate-impact claims; preserve source confidence labels, exact public-record language, docket identifiers, and canonical URLs; no partner logos, official seals, fake AI-engine screenshots, fake analytics, testimonials, or invented source counts.\nCopy rules: headline: Use exact short headline if supplied.; supportingText: Use step labels only when supplied.; cta: Optional exact CTA..\nInclude: natural hands, subject interaction, working surface, micro-detail, step cue or arrow, small benefit label.\nConstraints: hands must be anatomically natural; use only safe and accurate interactions; do not invent use steps; keep product label visible when relevant; do not add subtitles, body-copy captions, explanatory footer text, or small descriptive text unless the user supplied exact copy for it; keep text sparse; use short labels, UI placeholder blocks, or visual markers only when needed; keep the product UI, workflow, and product-proof cues recognizable.\nAvoid: extra fingers, wrong usage, messy workspace, product obscured by hands, fake app screens; fake endorsements; unsupported claims; misspelled large text; watermarks; clutter; other brands."}]}