agentsclimarketplace

Process evolution infographic

Skill lori-super/process-evolution-infographic

Codex Skill that turns any topic into a museum-grade process-evolution infographic prompt.

Install
npx -y skills add lori-super/process-evolution-infographic

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Use when the user gives a topic, concept, object, product category, history/civilization subject, species, brand, industry, or abstract idea and wants a process evolution infographic, timeline poster, 发展脉络/演化路径/形态变迁/谱系展开 prompt - builds a high-end theme-specific image prompt with stages, representative visuals, color, typography, and layout.

SKILL.md

7.1 KB, ~1.4k tokens by cl100k_base, as published. Nobody here has run it

Process Evolution Infographic

Overview

Turn a single theme into a high-end process-evolution infographic poster prompt. The output should read like a complete image-generation brief for a knowledge-rich poster, not a generic illustration, PPT timeline, or decorative collage.

Default to the user's input language for all visible title, labels, annotations, and stage text unless the user specifies otherwise.

Workflow

  1. Identify the theme, any requested language, aspect ratio, dark/light mode, era range, style constraints, or target model.
  2. Infer the best progression logic before designing the poster. Do not force every topic into the same timeline shape.
  3. Build 5-12 stages with a clear start, end, ordering logic, stage names, time labels when useful, representative visual objects, and one concise knowledge point per stage.
  4. Choose a spatialized process structure: stepped platforms, diagonal route, stratified layers, lineage branches, exhibition plinths, version shelves, artifact cases, geological strata, or another form that fits the theme.
  5. Create a theme-specific design system: color roles, typography mood, label system, annotation style, object rendering style, density, and reading path.
  6. Write the final image prompt as a production-ready poster brief. Include enough factual and visual detail for the image model to compose a complete infographic.

If the topic depends on current facts, disputed dates, living people, company/product status, or other information likely to change, verify the facts before finalizing the stage map.

Progression Logic

Theme typePrimary structureVisual emphasis
History, civilization, dynasty, institutionEra sequence, key periods, artifacts, representative people or sitesTimelines, archaeological display, archive labels, cultural material evidence
Product, tool, object, consumer categoryChanges in shape, material, mechanism, manufacturing, use, aesthetics, and social roleVersion plinths, exploded silhouettes, material swatches, industrial/product design cues
Biology, nature, species, food, body systemsEvolution chain, branching taxonomy, lifecycle, morphology, habitat, functional adaptationSpecimen plates, anatomical callouts, fossil or natural-science display logic
Abstract idea, belief, medium, industryCognitive phases, institutional changes, media shifts, social context, conceptual breakthroughsDiagrammatic layers, nodes, evidence fragments, symbolic but concrete visual anchors
Brand, fashion, lifestyle, visual cultureGenerations, style eras, audience shifts, material and identity changesEditorial layout, refined object styling, restrained luxury or trend-aware cues

Prompt Requirements

The final prompt must include:

  • A direct main title based on the user's theme, plus a subtitle describing the progression logic.
  • A vertical infographic poster by default, unless the user requests another format.
  • A strong ordered layout with a clear reading path from origin to endpoint.
  • 5-12 stages, each with stage title, time/phase label where appropriate, representative object, and concise explanation.
  • Visual objects that make stage differences obvious; every stage should have at least one recognizable visual anchor.
  • A complete color system tied to the topic, including background, structure, title, body text, stage labels, time labels, accents, and connector/annotation colors.
  • Typography guidance that matches the topic: historical, industrial, editorial, scientific, futuristic, cultural, or another justified mood.
  • Integrated image/text behavior: labels, lead lines, plaques, annotations, numbers, and objects should belong to the same visual system.
  • Quality constraints: high information organization, professional museum/editorial/visual-encyclopedia design, readable labels, clear hierarchy, refined texture, no clutter.

Design Rules

  • Treat the poster as a spatialized process, not a flat line with notes attached.
  • Make the structure highly organized: viewers should first see the title, then the overall path, then each stage object, then details.
  • Let the theme drive form, color, and typography. Do not default to one beige/brown museum template.
  • Use dark mode only when the theme benefits from it, such as technology, space, future systems, deep sea, night, digital industry, or biological anatomy; otherwise choose light or neutral systems when they better support reading.
  • Keep copy short but knowledge-dense. Each annotation should express a real stage feature, breakthrough, function, material change, social role, or aesthetic shift.
  • Use restrained innovation in typography: asymmetric title rhythm, large years or numbers as structure, embedded labels, exhibit tags, caption strips, or path-following text when it improves the poster.
  • Make the final prompt specific enough that changing the topic would change the whole visual system, not just the words.

Avoid

  • Ordinary PPT timelines, generic infographic templates, cheap encyclopedia layouts, or pure illustration without information structure.
  • Reusing the same palette, especially fixed warm beige/brown, unless the topic genuinely calls for it.
  • Decorative patterns, icons, arrows, or filler unrelated to the theme.
  • Excessive text, overcrowded stages, unreadable labels, chaotic connectors, or unclear progression direction.
  • Overly cartoonish, flashy, social-media-filtered, low-trust, or stock-poster aesthetics.
  • Separating image and text into two unrelated systems.

Output Shape

When the user asks for a prompt, output the prompt directly. Use compact sections only if they help the user edit the result:

主题:
海报定位:
构图路径:
阶段内容:
代表性视觉对象:
配色系统:
字体与排版:
图文融合:
质量与禁忌:

For image models that prefer paragraph prompts, turn the same information into one polished paragraph plus a short negative prompt.

Example

User topic: 青铜酒器的演变

A good response should infer a stable historical sequence, such as early ritual vessel forms, Shang decorative maturity, Western Zhou ritual standardization, Spring-Autumn/Warring States regional variation, and later museum/archival interpretation. It should assign representative objects such as jue, gu, zun, you, and hu; use an archaeological exhibition structure; choose bronze patina, mineral green, bone-paper, ink-black, and restrained red seal accents only because the topic supports them; and write concise stage labels rather than long exposition.

Reference

For the original long-form Chinese prompt that this skill was derived from, read references/source-prompt.md only when exact wording or stricter style inheritance is needed.

Gives 0 of the 12 instructions most design systems skills give in ~1.4k tokens

Counted across 528 of the 534 authors here whose files we hold, read 2026-08-06

  • create a custom theme if neededin 54 of 528, across 10 files
  • read the corresponding theme filein 54 of 528, across 10 files
  • ask which theme to applyin 53 of 528, across 9 files
  • show the theme showcasein 53 of 528, across 9 files
  • maintain visual identity across all slidesin 50 of 528, across 6 files
  • apply the specified colors and fontsin 47 of 528, across 3 files
  • get explicit confirmationin 45 of 528, across 1 file
  • Generate a design system before codingin 19 of 528, across 6 files
  • Maintain at least 4.5:1 color contrast ratioin 19 of 528, across 8 files
  • Describe component shapes, colors, shadows, and interaction statesin 18 of 528, across 4 files
  • Check Python installation and install if missingin 17 of 528, across 4 files
  • Default to html-tailwind if stack is unspecifiedin 17 of 528, across 4 files

Said here and by no other author read

  • infer the progression logic before designing
  • build 5-12 stages with clear ordering and visual anchors
  • choose a spatialized process structure fitting the theme
  • write the final image prompt as a poster brief
  • verify current or disputed facts before finalizing
  • include a complete theme-specific color system

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.