Skip to content

Latest commit

 

History

History
183 lines (149 loc) · 13.2 KB

16-documents-publishing-information.md

File metadata and controls

183 lines (149 loc) · 13.2 KB

Documents, Publishing, and Information-System Prompts

Eight original, production-oriented Qwen Image 3.0 prompt recipes. Replace bracketed variables and place final on-image copy in Text (verbatim).

DOC-01 — three-page presentation board showing cover, contents page and chapter opener

Use it for: create a credible publication system for a fictional report titled [REPORT TITLE]

Target language: English (en)
Localization directive: Convert every user-editable variable and non-English quoted example into natural English before rendering. Preserve deliberately multilingual copy only when the recipe explicitly requires it. Keep authorized brand and product identifiers unchanged.
Typography QA: Use correct English spelling, punctuation, capitalization, and natural phrase-based line breaks. Treat non-English Text (verbatim) content as source copy to localize unless the recipe is explicitly multilingual. Do not add filler text.
Use case: business-publishing
Asset type: three-page presentation board showing cover, contents page and chapter opener
Goal: create a credible publication system for a fictional report titled [REPORT TITLE]
Audience: [PROFESSIONAL AUDIENCE]
Design system: 12-column grid, disciplined baseline, one display serif and one neutral sans, consistent folio and running header
Cover: title, subtitle, organization name and date with one original abstract data motif
Contents: exactly six chapter titles with page numbers supplied by user
Chapter opener: chapter number, title, 50-word abstract and one verified chart placeholder
Text (verbatim): [FINAL APPROVED COPY FOR ALL THREE PAGES]
Constraints: exact page count shown; text belongs to correct page; no lorem ipsum; no invented statistics, citations, seals or ISBN
Avoid: tiny unreadable body text, random charts, fake institutional logos, decorative clutter, watermark

DOC-02 — A4 two-sided quick-start sheet

Use it for: teach a first-time user to assemble and safely start authorized [DEVICE]

Target language: English (en)
Localization directive: Convert every user-editable variable and non-English quoted example into natural English before rendering. Preserve deliberately multilingual copy only when the recipe explicitly requires it. Keep authorized brand and product identifiers unchanged.
Typography QA: Use correct English spelling, punctuation, capitalization, and natural phrase-based line breaks. Treat non-English Text (verbatim) content as source copy to localize unless the recipe is explicitly multilingual. Do not add filler text.
Use case: product-documentation
Asset type: A4 two-sided quick-start sheet
Goal: teach a first-time user to assemble and safely start authorized [DEVICE]
Device lock: exact supplied product geometry, part names, connector positions and controls
Structure: package contents, six numbered setup steps, two safety callouts, first-use checklist and support block
Illustration: clean technical line art with limited spot color; same viewing angle unless rotation is necessary
Text (verbatim): [APPROVED INSTRUCTIONS AND WARNINGS]
Mapping: each number points to the correct part and action; warning symbols only where supplied or standards-approved
Typography: large step numbers, short action headings, body readable at printed A4 size
Constraints: exactly six steps; correct order; no invented button, warranty, certification or support URL; human technical review required
Avoid: exploded parts not in product, ambiguous arrows, decorative pseudo-text, unsafe hand position, watermark

DOC-03 — presentation board with one wall label, three object labels and one accessibility label

Use it for: design an inclusive label family for fictional exhibition [EXHIBITION]

Target language: English (en)
Localization directive: Convert every user-editable variable and non-English quoted example into natural English before rendering. Preserve deliberately multilingual copy only when the recipe explicitly requires it. Keep authorized brand and product identifiers unchanged.
Typography QA: Use correct English spelling, punctuation, capitalization, and natural phrase-based line breaks. Treat non-English Text (verbatim) content as source copy to localize unless the recipe is explicitly multilingual. Do not add filler text.
Use case: exhibition-design
Asset type: presentation board with one wall label, three object labels and one accessibility label
Goal: design an inclusive label family for fictional exhibition [EXHIBITION]
Information hierarchy: exhibition title, 80-word introduction, object title, creator, date, materials, 45-word interpretation and source credit
Design system: high-contrast type, generous line spacing, consistent left edge, tactile color band and optional braille-zone placeholder
Object images: three supplied authorized objects, neutral cutouts at consistent scale
Text (verbatim): [FINAL CURATORIAL COPY]
Accessibility: minimum visual text size appropriate to viewing distance; no text over images; do not fabricate braille dots
Constraints: three object labels; metadata maps to correct object; no invented provenance; source credits exact
Avoid: luxury-brand styling, pseudo-braille, illegible gray text, decorative labels, watermark

DOC-04 — six-card 4×6 inch recipe series shown in a 3×2 grid

Use it for: create a coherent card family for [SIX VERIFIED RECIPES]

Target language: English (en)
Localization directive: Convert every user-editable variable and non-English quoted example into natural English before rendering. Preserve deliberately multilingual copy only when the recipe explicitly requires it. Keep authorized brand and product identifiers unchanged.
Typography QA: Use correct English spelling, punctuation, capitalization, and natural phrase-based line breaks. Treat non-English Text (verbatim) content as source copy to localize unless the recipe is explicitly multilingual. Do not add filler text.
Use case: food-publishing
Asset type: six-card 4×6 inch recipe series shown in a 3×2 grid
Goal: create a coherent card family for [SIX VERIFIED RECIPES]
Shared system: same grid, typographic scale, ingredient column, method column, serving badge and footer
Card variation: one distinctive ingredient illustration and one accent color per recipe
Content: title, servings, preparation time, exact ingredient quantities and exactly five method steps per card
Text (verbatim): [COMPLETE VERIFIED RECIPE COPY]
Photography/illustration: one modest finished-dish image per card, visually matching listed ingredients
Constraints: six cards; no omitted units; no invented allergens or nutrition facts; quantities and steps human-checked
Avoid: mismatched dish, tiny ingredients, extra garnish claims, random handwritten text, watermark

DOC-05 — A5 portrait eight-page program overview shown as cover plus four key spreads

Use it for: organize a fictional one-day research conference with a readable schedule and speaker system

Target language: English (en)
Localization directive: Convert every user-editable variable and non-English quoted example into natural English before rendering. Preserve deliberately multilingual copy only when the recipe explicitly requires it. Keep authorized brand and product identifiers unchanged.
Typography QA: Use correct English spelling, punctuation, capitalization, and natural phrase-based line breaks. Treat non-English Text (verbatim) content as source copy to localize unless the recipe is explicitly multilingual. Do not add filler text.
Use case: event-publishing
Asset type: A5 portrait eight-page program overview shown as cover plus four key spreads
Goal: organize a fictional one-day research conference with a readable schedule and speaker system
Pages: cover, welcome, timetable, two track pages, speaker index, venue map and notes
Schedule data: use only supplied times, session titles, rooms, speakers and breaks
Design system: two track colors, clear time axis, speaker headshots only when authorized, consistent session codes
Text (verbatim): [APPROVED EVENT COPY]
Map: simplified venue plan based only on supplied layout; accessible entrances and facilities clearly marked
Constraints: no schedule collisions introduced; every session appears once; correct speaker-session mapping; no fake sponsors
Avoid: unreadable microtype, invented credentials, decorative timetable, impossible venue route, watermark

DOC-06 — wallet-size information card plus enlarged accessibility version

Use it for: visualize a clinician-approved medication schedule without giving new medical advice

Target language: English (en)
Localization directive: Convert every user-editable variable and non-English quoted example into natural English before rendering. Preserve deliberately multilingual copy only when the recipe explicitly requires it. Keep authorized brand and product identifiers unchanged.
Typography QA: Use correct English spelling, punctuation, capitalization, and natural phrase-based line breaks. Treat non-English Text (verbatim) content as source copy to localize unless the recipe is explicitly multilingual. Do not add filler text.
Use case: health-communication
Asset type: wallet-size information card plus enlarged accessibility version
Goal: visualize a clinician-approved medication schedule without giving new medical advice
Input data: use only supplied medication names, dose, time, food instruction and caution text
Structure: morning, midday, evening and bedtime columns; one row per medication; check boxes for seven days
Icons: simple sun, meal and moon cues as secondary support, never as the only encoding
Typography: large plain-language text, high contrast, units never separated from numbers
Text (verbatim): [CLINICIAN-APPROVED COPY]
Constraints: exact spelling and dosage; no inferred instruction, interaction or claim; include "Follow your clinician’s instructions" if supplied
Avoid: pill appearance as identity cue, invented medical logo, red-green-only coding, decorative script, watermark

DOC-07 — broadsheet newspaper front-page concept

Use it for: arrange supplied fictional or licensed newsroom content into a credible hierarchy

Target language: English (en)
Localization directive: Convert every user-editable variable and non-English quoted example into natural English before rendering. Preserve deliberately multilingual copy only when the recipe explicitly requires it. Keep authorized brand and product identifiers unchanged.
Typography QA: Use correct English spelling, punctuation, capitalization, and natural phrase-based line breaks. Treat non-English Text (verbatim) content as source copy to localize unless the recipe is explicitly multilingual. Do not add filler text.
Use case: editorial-publishing
Asset type: broadsheet newspaper front-page concept
Goal: arrange supplied fictional or licensed newsroom content into a credible hierarchy
Grid: six columns, masthead, lead story, two secondary stories, one briefing rail, one photo caption and footer index
Content mapping: each supplied headline, deck, byline, excerpt and image stays with its correct story
Style: contemporary public-interest newspaper, restrained rules, strong typographic contrast, real paper texture
Text (verbatim): [COMPLETE APPROVED FRONT-PAGE COPY]
Images: supplied authorized news images only; natural crops; captions and credits exact
Constraints: no fabricated reporting, quote, date, price or location; no lorem ipsum; readable at full-page zoom
Avoid: tabloid sensationalism unless requested, repeated article, random columns, fake QR code, watermark

DOC-08 — nine-card 3×3 deck preview plus one enlarged card back

Use it for: teach [KNOWLEDGE DOMAIN] through a reusable collectible-card system

Target language: English (en)
Localization directive: Convert every user-editable variable and non-English quoted example into natural English before rendering. Preserve deliberately multilingual copy only when the recipe explicitly requires it. Keep authorized brand and product identifiers unchanged.
Typography QA: Use correct English spelling, punctuation, capitalization, and natural phrase-based line breaks. Treat non-English Text (verbatim) content as source copy to localize unless the recipe is explicitly multilingual. Do not add filler text.
Use case: educational-card-system
Asset type: nine-card 3×3 deck preview plus one enlarged card back
Goal: teach [KNOWLEDGE DOMAIN] through a reusable collectible-card system
Card schema: category, title, key illustration, three verified facts, difficulty marker and cross-reference ID
Set content: exactly nine supplied topics, one topic per card, balanced across three categories
Design system: shared frame and type hierarchy; category color plus shape so meaning does not depend on color alone
Illustration: consistent editorial style, scientifically or historically accurate where applicable
Text (verbatim): [APPROVED CARD COPY]
Constraints: nine unique cards; facts map to correct illustration; IDs unique; no invented rarity, score or citation
Avoid: trading-card franchise resemblance, tiny text, duplicated card, random statistics, watermark

Back to the English prompt index.