agentleFS
kiku-jwkiku-jw/codex-skills/illustration-prompt/SKILL.md

illustration-prompt

Skill0 starsChanged 4 months agoMITView on GitHub

Turn a vague image request into a generator-ready illustration prompt for Midjourney, DALL-E, Flux, Stable Diffusion, or similar tools. Use when the user needs visual direction, prompt structure, or reference-aware image prompting rather than image generation code.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Do not use when: the user already has a finished prompt or wants direct generation without prompt design.

    line 10
  2. Very specific:

    If references are present, summarize what should be borrowed and what should not.

    line 18
  3. Very specific:

    Default to no text in the image unless the user explicitly asks for text.

    line 25

≈ “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

Illustration Prompt

Metadata

  • Trigger when: the real work is turning a visual idea plus references into a high-quality prompt.
  • Do not use when: the user already has a finished prompt or wants direct generation without prompt design.

Skill Purpose

Translate vague visual intent into a concrete, reference-aware prompt that a generator can follow without leaning on hand-wavy adjective soup.

Instructions

  1. Lock the brief in this order: placement/context, style family, detail density, references, scene, palette/mood, and format. Collapse questions that the conversation already answered; do not re-interview for sport.
  2. If references are present, summarize what should be borrowed and what should not. Read ~/.codex/skills/illustration-prompt/references/reference-analysis.md when you need the reference-reading checklist and ~/.codex/skills/illustration-prompt/references/prompt-template.md for the 8-block prompt structure.
  3. Return one structured prompt in English plus a short filename and only the minimal model-specific tweak when it materially changes the result. If the user wants actual generation afterward, hand off to whatever image-generation tool is available in the current environment.

Non-Negotiable Acceptance Criteria

  • References and explicit scene constraints outrank decorative adjectives.
  • Conflicting references are called out instead of blended into fake coherence.
  • Perspective, composition, palette, material cues, and count-sensitive objects are concrete when they matter.
  • Default to no text in the image unless the user explicitly asks for text.

Output

  • A short kebab-case filename.
  • One structured English prompt using the 8-block format.
  • An optional short generator note only when a model-specific tweak genuinely matters.

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.