agentleFS
Wang-CankunWang-Cankun/cankun-skills/skills/art-poster-mondo/SKILL.md

art-poster-mondo

Skill2 starsChanged 32 days agoMITView on GitHub

Research, art-direct, create, and critique original alternate movie, television, game, and pop-culture posters using the curatorial and screen-print production principles associated with Mondo: deep source knowledge, a fresh conceptual hook, artist-to-property fit, integrated typography, collectible-object craft, variants, and rigorous review. Use when a user mentions Mondo, Mondo式/Mondo风格海报, alternative movie posters, collectible screenprints, licensed pop-culture key art, or wants a poster brief, concept routes, generation prompt, critique, or print plan in this tradition.

The file

Show its rules and text

We split this skill into the rules it gives an agent

16 rules. About 0 are common, 16 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈16

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Treat “Mondo style” as a curatorial system, not a single surface look.

    line 14
  2. Distinctive:

    Read references/mondo-research.md before explaining Mondo’s capability, citing its history, or using named works as evidence.

    line 18
  3. Distinctive:

    Read references/visual-casebook.md before comparing named posters, selecting a visual archetype, or explaining how composition, typography, …

    line 19
  4. Distinctive:

    Read references/concept-and-critique.md before developing concepts, writing generation prompts, or evaluating a poster.

    line 20
  5. Distinctive:

    Read references/print-production.md when the output must be printable, separated for screen printing, or specified as a regular/variant …

    line 21
  6. Distinctive:

    Do not force every section into a simple request.

    line 34
  7. Distinctive:

    Ask only for missing information that would materially change the concept.

    line 39
  8. Distinctive:

    Create at least three routes that differ in idea and structure, not merely palette:

    line 52
  9. Distinctive:

    Use a limited palette deliberately.

    line 79
  10. Distinctive:

    Use texture to describe material and mood.

    line 81
  11. Distinctive:

    Treat foil, metallic, fluorescent, glow, varnish, or alternate paper as narrative tools.

    line 82
  12. Distinctive:

    Use an image-generation or image-editing tool when the user asks for artwork, a visual, or poster variants.

    line 86
  13. Distinctive:

    Keep small typography, billing blocks, dates, and legal marks out of the generated raster when exact text matters.

    line 89
  14. Distinctive:

    Add exact typography in a deterministic layout step whenever tools and output format permit.

    line 90
  15. Distinctive:

    no category below half its available points.

    line 101
  16. Distinctive:

    no false affiliation or unsupported licensing claim.

    line 105

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Art Poster — Mondo

Treat “Mondo style” as a curatorial system, not a single surface look. Preserve the source’s essence, find a fresh point of view, match the visual language to the property, and design the physical print as part of the idea.

Load the relevant references

  • Read references/mondo-research.md before explaining Mondo’s capability, citing its history, or using named works as evidence.
  • Read references/visual-casebook.md before comparing named posters, selecting a visual archetype, or explaining how composition, typography, and variants differ across releases.
  • Read references/concept-and-critique.md before developing concepts, writing generation prompts, or evaluating a poster.
  • Read references/print-production.md when the output must be printable, separated for screen printing, or specified as a regular/variant edition.

Route the request

Choose only the route the user needs:

  • Research: distinguish sourced facts, visual observations, and your inference; cite current URLs.
  • Brief: produce a source map, audience/use case, rights status, production target, and one-sentence design challenge.
  • Concepts: produce at least three genuinely different visual engines, then recommend one.
  • Create: develop or generate the selected route, keeping typography and production constraints explicit.
  • Critique: diagnose the existing work with the rubric, then prescribe the smallest high-leverage changes.
  • Print plan: specify dimensions, color separations, paper/ink intent, proofing, and delivery package.

Do not force every section into a simple request.

Ground the source

  1. Identify the title/property, version or year, intended audience, format, language, deadline, spoiler tolerance, and whether the piece is official, licensed, internal, or an unofficial concept.
  2. Ask only for missing information that would materially change the concept. Proceed with clearly labeled assumptions when the gap is non-blocking.
  3. Rewatch, reread, inspect supplied assets, or research reliable sources when accuracy matters. Browse for current releases, current brand facts, licensing claims, or unfamiliar properties.
  4. Build a compact source map:
    • emotional thesis;
    • central conflict or transformation;
    • iconic imagery already overused;
    • underused object, location, gesture, or motif;
    • visual grammar of the world;
    • mandatory billing, logos, likenesses, and prohibited elements.
  5. State the “poster argument” in one sentence. Make it an interpretation, not a plot summary.

Develop divergent concepts

Create at least three routes that differ in idea and structure, not merely palette:

  1. Reduction: encode the premise in one symbol, silhouette, impossible object, or negative-space reveal.
  2. World: make an environment, architecture, prop, or quiet scene carry the threat or emotion.
  3. Energy: build a controlled ensemble, confrontation, motion system, or maximal narrative field.

Replace a route when it does not suit the property. Consider typographic, portrait, archival, diagrammatic, or culturally rooted approaches instead.

For each route, provide:

  • concept name and poster argument;
  • one-sentence viewer experience at 3 m, 1 m, and 30 cm;
  • focal image, hierarchy, crop, and negative-space plan;
  • palette and proposed spot-color count;
  • typography role and title placement;
  • two or three source-specific details;
  • print/process opportunity;
  • originality, rights, likeness, and production risks.

Select a route only after comparing the candidates against the rubric in references/concept-and-critique.md.

Art-direct the selected route

  • Make the film or property recognizable through meaning, not through a checklist of faces.
  • Preserve one dominant read. Let secondary details reward close viewing without weakening the silhouette.
  • Integrate the title into the composition early. Reserve stable space for credits and legal copy.
  • Choose an era or visual tradition because it belongs to the subject, not because “retro” feels collectible.
  • Use a limited palette deliberately. Reuse inks across focal, secondary, and border elements.
  • Match technique to story: clean geometry for systems, expressive drawing for bodily energy, environmental detail for atmosphere, and restrained portraiture for intimacy.
  • Use texture to describe material and mood. Do not use distress as a generic vintage filter.
  • Treat foil, metallic, fluorescent, glow, varnish, or alternate paper as narrative tools. Remove any finish that functions only as a premium signal.

Create visual output

Use an image-generation or image-editing tool when the user asks for artwork, a visual, or poster variants.

  1. Generate the illustration base with the composition, palette, lighting, negative space, and print texture specified.
  2. Keep small typography, billing blocks, dates, and legal marks out of the generated raster when exact text matters.
  3. Add exact typography in a deterministic layout step whenever tools and output format permit; otherwise provide a placement-ready text plan and clearly flag placeholder text.
  4. Inspect the result at thumbnail size and at full size. Correct silhouette, hierarchy, anatomy, unwanted text, source errors, and accidental tangencies before polishing.
  5. Show no more than the useful number of variants. Explain the conceptual difference between them.

Never place Mondo’s name or logo on the work, imply Mondo participation, or describe an unofficial concept as licensed. Do not copy a specific Mondo poster’s composition. Do not imitate the exact style of a named living artist; translate high-level traits into an original visual system instead.

Review and revise

Score the work with the 100-point rubric in references/concept-and-critique.md. Require:

  • a total of at least 80;
  • no category below half its available points;
  • a clearly identifiable fresh angle;
  • legible title and stable hierarchy;
  • a plausible print or output plan;
  • no false affiliation or unsupported licensing claim.

Show all eight rubric categories whenever reporting a numeric total, and verify the arithmetic. If a compact comparison omits categories, label it qualitative and do not present a normalized total.

Lead critique with the concept diagnosis. Separate idea problems from execution problems. Recommend at most five prioritized changes, then rescore the proposed revision.

Deliver concise, usable outputs

For a concept request, deliver:

  1. a five-line brief;
  2. three route cards;
  3. a comparison and recommendation;
  4. one production-aware generation or illustration prompt for the chosen route;
  5. the key risks and next decision.

For a finished-poster request, also deliver:

  • final dimensions and crop;
  • typography copy deck;
  • palette/ink plan;
  • regular versus variant logic, if requested;
  • proofing checklist;
  • a clear “original concept, not affiliated with Mondo” note when relevant.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.