ModelScope Cover

Goal

Create a clean 16:9 raster cover that feels native to ModelScope, remains readable in small cards, and communicates one clear content idea. Prefer precise layout, large type, and authentic brand assets over decorative complexity.

Workflow

1. Gather source context.

   • Inspect any provided URL, text, README, article, screenshots, app description, or logo.
   • Identify the content type: Gallery (灵感流), Learn articles (研习社), Studio (创空间).
   • Extract the core message: project name, domain, main capability, audience, and one concrete outcome.

2. Decide language and copy.

   • Use the language requested by the user.
   • If not specified, match the source title or target audience.
   • Keep official product, model, dataset, and organization names unchanged.
   • Use one dominant title and at most one short subtitle or tag line.
   • Prefer content-specific nouns and outcomes over generic promotional claims.

3. Choose the visual system.

   • Start from ModelScope brand cues: white or near-white base, brand purple, cyan/teal accents, dark indigo text, generous whitespace.
   • If the user provides brand assets or logo files, use those exact files. Composite logos deterministically after image generation when fidelity matters.
   • If no official asset is provided, avoid inventing or recreating a logo from memory.
   • Use the source material to choose a simple visual metaphor: app layout, notebook workspace, model card, dataset grid, pipeline, evaluation chart, or demo interface.

4. Generate or compose the cover.

   • Produce an exact 16:9 raster image, usually 1920x1080.
   • When text, logo fidelity, or UI containment matters, prefer deterministic compositing with a script or image editor over relying entirely on image generation.
   • Keep interface mockups simplified: show large layout blocks, icon-like shapes, and a few readable labels instead of small code, dense screenshots, or tiny UI details.
   • Use visual assets when they clarify the product or task, but simplify them enough to survive card-size viewing.

5. Verify and iterate.

   • Check readability at small-card scale.
   • Confirm every visible word fits its container with comfortable padding.
   • Confirm logo shape, colors, lettering, and proportions are preserved.
   • Confirm panels, pills, labels, icons, and screenshots do not overflow parent containers unless the floating effect is intentional and visually clear.
   • Regenerate or simplify when the result depends on tiny details, low contrast, or busy texture.

Design Rules

• Use a 16:9 aspect ratio.
• Make the title the dominant element.
• Keep the smallest meaningful text large enough to read in a small card; for 1920x1080 covers, use roughly 56 px or larger for minor labels, and much larger for primary copy.
• Limit visible text to the title, one short subtitle, and only a few large labels or process words when needed.
• Keep important content away from edges with roughly 6-8% margins.
• Prefer white, off-white, or very light purple backgrounds with strong brand-purple structure and cyan/teal accents.
• Avoid one-note palettes, muddy gradients, dense textures, tiny screenshots, micro-patterns, and intricate linework.
• Use high contrast between text and background.
• Use rounded cards and panels sparingly; keep them simple, aligned, and roomy.
• Do not place cards inside cards unless it is clearly representing an interface layout.
• Avoid long URLs, paragraphs, fine print, dense bullet lists, and small decorative captions.

Brand And Logo Rules

• Prefer provided ModelScope logo files over generated logos.
• Preserve the exact logo geometry, colors, lettering, and aspect ratio.
• Place the logo on a calm, high-contrast background with breathing room.
• Do not put strong gradients, busy shapes, or decorative elements directly behind the logo.
• When the cover should feel more branded, use the brand palette before adding extra decoration.

Layout Guidance

• For split covers, reserve the simpler side for the title and logo, and use the other side for a simplified visual scene.
• For app, notebook, or demo covers, represent the interface as a few large zones: navigation, main canvas, result/output, or action bar.
• For model or dataset covers, prefer one strong conceptual panel or grid over a collage.
• For tutorials or workflows, use 2-4 large action words only when they add clarity.
• Align repeated panels and labels on consistent centerlines or baselines.
• Keep all labels, chips, icons, and screenshots inside their parent boundaries with clear padding.

Prompt Pattern

When using an image-generation tool, include:

Create a 16:9 ModelScope cover image for [content type/project].
Language: [requested/source language].
Main title: [short title].
Subtitle/tagline: [optional short phrase].
Visual concept: [simple content-specific scene or metaphor].
Brand system: white or light-purple base, ModelScope purple, cyan/teal accents, dark indigo text.
Style: elegant, clean, modern, high contrast, readable in small cards.
Text constraints: very large title, few words, no small captions, no paragraphs.
Logo constraints: [use provided logo exactly / no logo / reserve clean logo area].
Composition: generous margins, simple hierarchy, simplified interface/layout blocks, not cluttered.
Containment: all panels, labels, icons, and chips stay inside their parent shapes with comfortable padding.
Output: exact 16:9 raster cover.

Handling Common Inputs

• Link only: inspect the page, infer language and content type, then derive a concise title and visual direction.
• Long article: reduce it to one title-level idea plus one optional subtitle.
• Studio app or demo: emphasize what the user can do and the primary interactive result.
• Notebook or tutorial: emphasize the task, method, or learning outcome; show the workspace layout rather than dense code.
• Model or dataset: emphasize the domain, task, and output artifact.
• Logo provided: composite the exact logo after generation if needed.
• Screenshot provided: use it as context unless the user explicitly wants a screenshot-based cover; simplify tiny UI details.

Final Delivery

Return the generated cover file or image. Briefly mention the chosen title/subtitle, whether a provided logo was used, and any assumption about language or branding.