agentleFS
WiseWong6WiseWong6/wise-skills/blue-poster/SKILL.md

blue-poster

Skill10 starsChanged 3 months agoMITView on GitHub

Turn one source image into a finished 3:4 Minimal Blue Poster with semantic style selection, a default full-design composition, an optional upper-photo/lower-design 1:1 split, and an 11-style local reference catalog. Use when Codex should create a blue poster, Layer Study poster, cyanotype or moire architectural print, compare optical print styles, or generate a full-design or split 1:1 variant from a supplied image.

The file

We split this skill into the rules it gives an agent

12 rules. About 0 are common, 7 are distinctive, and 5 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈7

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 5

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  • could be automatic: a setting could enforce it
  1. Distinctive:

    If the current host has no built-in image-generation capability, or that capability fails, stop and report the blocking reason.

    line 15
  2. Distinctive:

    Treat style reference images as browse-only.

    line 16
  3. Distinctive:

    Do not merge stereo frames or invent depth semantics.

    line 23
  4. Very specific:

    If the user names S01–S11, honor it.

    line 29
  5. Distinctive:

    Read prompt-full-design.md and the selected block in style-programs.md.

    line 30
  6. Very specific:

    Call the selected host-native image generator once with the original source as the only image input.

    line 32
  7. Very specific:

    Run python3 scripts/validate_output.py <image> --mode full.

    line 35
  8. Distinctive:

    After delivery, ask whether the user wants:

    line 39
  9. Distinctive:

    Read prompt-split-1x1.md, insert exactly one style block, and make one fresh call with the selected host-native image generator.

    line 48
  10. Very specific:

    Default an alternate Sxx choice to full-design mode.

    line 54
  11. Distinctive:

    Use style-selection.md for semantic guidance and style-programs.md only after a style is chosen.

    line 61
  12. Very specific:

    Keep R-S08-B labeled aesthetic-only: it is 2:3 and is not a valid delivery reference.

    line 62

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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

Blue Poster

Generate each final poster from the original source image in one image-generation call. Default to a complete full-design poster. Never create a base image and then add effects in a second content-generation stage.

Required tool policy

  • Detect the host environment before generation and use only an image-generation capability built into that host.
  • In Codex, use only the Codex host built-in image_gen.imagegen tool. Never invoke, install, or fall back to a third-party image skill, Ark, Doubao, Gemini, a local model, CLI, or API workflow.
  • Outside Codex, use the current model or platform's own built-in image-generation capability when it is available, such as GPT's native image generation in ChatGPT or Doubao's native image generation in Doubao. Do not call another provider's API, CLI, local model, or third-party image skill as a fallback.
  • If the current host has no built-in image-generation capability, or that capability fails, stop and report the blocking reason.
  • Treat style reference images as browse-only. Never pass them to image generation.

MPO source normalization

  • .mpo is an accepted source container. MPO is normalized before generation; it is not a new poster output mode.
  • Inspect frames with python3 scripts/extract_mpo.py <source.mpo> --list.
  • Unless the user chooses another frame, extract frame 0, the primary JPEG, and use that normalized JPEG as the only image input to the selected host-native image generator.
  • Do not merge stereo frames or invent depth semantics. If the user asks for left/right or multi-view treatment, clarify the selected frame before generation.
  • This local extraction step only unwraps the source container. It does not generate, alter, crop or stylize image content.

Generate the default full poster

  1. Require one source image. If it is a local file, inspect it with view_image before generation.
  2. If the user names S01–S11, honor it. Otherwise read style-selection.md, analyze the source semantics, and select exactly one style.
  3. Read prompt-full-design.md and the selected block in style-programs.md.
  4. Replace {{EFFECT_PROGRAM}} with exactly one complete style block. Do not leave placeholders or merge multiple styles.
  5. Call the selected host-native image generator once with the original source as the only image input. In Codex, this means image_gen.imagegen. State that the source is a semantic and structural source, not a style reference.
  6. Save the selected image under the caller's current workspace at outputs/blue-poster/<source>-full-Sxx-vN.png, unless the user supplied another destination. Never overwrite an existing file.
  7. Save the exact final prompt beside it as <source>-full-Sxx-vN.prompt.md.
  8. Run python3 scripts/validate_output.py <image> --mode full. If it fails, retry once from the original source with the same style and a stronger native 3:4 instruction. Never stretch or crop to hide a ratio failure. If the retry fails, report it as unaccepted.
  9. Perform only a lightweight check on the returned image: the subject remains recognizable, the whole page is designed, no photographic window remains, and the full-mode carrier contract is visible—3–6 active regions, no more than two clusters, no isolated small rectangle, a continuous subject corridor and at least 40% quiet paper. Do not start a browser or create extra screenshots.
  10. Report the selected style ID and name, one concrete selection reason, image path, prompt path, validation result, and catalog path.

After delivery, ask whether the user wants:

  • the same style as an upper-photo/lower-design 1:1 split; and
  • to browse or try another style from references/style-catalog.html.

Generate a split 1:1 variant

  1. Reuse the original source image, not the previously generated full poster.
  2. Reuse the selected style unless the user requests another Sxx.
  3. Read prompt-split-1x1.md, insert exactly one style block, and make one fresh call with the selected host-native image generator.
  4. Save as <source>-split-Sxx-vN.png with a matching .prompt.md sidecar.
  5. Run python3 scripts/validate_output.py <image> --mode split. Check that the only horizontal boundary is visually at the midpoint and that the lower half follows the carrier contract—3–6 active regions, no more than two clusters, no isolated small rectangle, a continuous subject corridor and at least 40% quiet paper. Do not claim pixel-level boundary verification from dimensions alone.

Generate an alternate style

  • Default an alternate Sxx choice to full-design mode.
  • Generate a split alternate only when the user explicitly requests it.
  • Return to the original source for every alternate; never chain generated posters as new inputs.

Browse styles

  • Direct the user to the absolute path of style-catalog.html. The catalog is divided into 1:1 split and Tokyo Tower · full design references; Tokyo Tower cards must use full-design images.
  • Use style-selection.md for semantic guidance and style-programs.md only after a style is chosen.
  • Keep R-S08-B labeled aesthetic-only: it is 2:3 and is not a valid delivery reference.

Output acceptance

  • Require an exact 3:4 pixel ratio.
  • Require one recognizable subject and coherent environment.
  • Reject empty cards, unrelated collage fragments, regular UI grids, mockups, logos, watermarks, and meaningless text.
  • For full mode, reject every photographic-looking area, split composition, result with more than six visibly bounded effect regions, evenly scattered panels, isolated small rectangles, or repeated framing across the primary subject.
  • For split mode, require one midpoint boundary, faithful photography above, complete design translation below, and reject more than six visibly bounded effect regions, evenly scattered panels, isolated small rectangles, or repeated framing across the lower-half subject.

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.