illustration
Skill18 starsChanged 7 months agoMITView on GitHub
Generate an in-product illustration (empty state, onboarding, hero, spot art) that obeys a brand bundle. Uses IP-Adapter / LoRA / Recraft style_id / Flux.2 brand refs for consistency across a set; validates palette ΔE2000 and style adherence.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- codeonym-oss/design-skillstheir own version, first seen Oct 20, 2026
- codeonym-org/codeonym-arch-designtheir own version, first seen Sep 25, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- codeonym-org/codeonym-arch-design★ 0same name
- codeonym-oss/design-skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository30 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- .cursor/rules/prompt-enhancer.mdcCursor rule
- .cursor/rules/prompt-to-asset.mdcCursor rule
- app-iconSkill
- asset-enhancerSkill
- asset-validation-debugSkill
- brand-consistencySkill
- faviconSkill
- illustrationSkill
- logoSkill
- og-imageSkill
- svg-authoringSkill
- t2i-prompt-dialectSkill
- transparent-bgSkill
- ui-mockup-promptSkill
- vectorizeSkill
- app-iconSkill
- asset-enhancerSkill
- asset-validation-debugSkill
- brand-consistencySkill
- faviconSkill
- logoSkill
- og-imageSkill
- svg-authoringSkill
- t2i-prompt-dialectSkill
- transparent-bgSkill
- ui-mockup-promptSkill
- vectorizeSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 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.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 71
After 3–4 accepted illustrations, train a LoRA for even tighter lock on 20+ asset sets.
≈ “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.
Files
Illustration generation
The consistency problem
A single illustration is easy. A set of twelve in the same style is the hard problem. Research 10 + 15: prompt words drift; reference images do not. Any illustration skill must inject a brand style reference at every call.
Routing
| Model | Brand lock mechanism | Best for |
| Flux Pro / Flux.2 | reference_images[] (up to 8 in Flux.2) + brand LoRA | Photoreal, stylized 3D, brand illustration sets |
| SDXL + brand LoRA | trained LoRA (6d recipe, ~5k steps on 20 images) | Bespoke brand style, open-weight |
| Recraft V3 | style_id (brand magic) | Flat vector, editorial illustration |
| Ideogram 3 | style codes | Loose "same vibe" — not strict lock |
| Midjourney v6/v7 | --sref / --cref / --mref | Concept work; no API, community wrappers only |
gpt-image-1 | input_image[] | Edit / composite flows |
First illustration in a set is human-gated. Once approved, its style becomes the reference injected into all subsequent generations.
Brand bundle injection
illustration prompt =
[SUBJECT + SCENE from brief]
+ [style anchor: "in the style of the provided reference images"]
+ [palette: exact hex list from brand]
+ [do_not list as positive anchors: "flat matte surfaces" not "no glossy plastic"]
+ [typography reminder: "no text, no labels"]
+ [technical constraints: aspect, resolution, composition]
+ reference_images[]: [style_ref_01.png, style_ref_02.png, (prior approved illustration).png]
+ LoRA handle / style_id / --srefPrompt scaffold
An illustration of [SUBJECT: concrete noun phrase] in a [SCENE: clear action/context].
Composition: [centered | rule-of-thirds | off-center-left]. Subject occupies ~60% of frame.
Style: in the style of the provided reference images. Flat vector with soft gradients.
Line weight consistent with references.
Palette strictly limited to: [#hex, #hex, #hex, #hex, #hex].
Materials: matte surfaces, soft ambient lighting, no rim lights, no lens flare.
No text, no labels, no UI elements.
[aspect ratio]. 2048x1280 resolution.Drop quality modifiers on Flux (no masterpiece, 8k — hurts adherence). Keep them on SD.
Post-processing
- Background removal only if asset is spot art (use BiRefNet for soft edges).
- Palette validation: K-means 8-color in LAB, ΔE2000 against brand palette, regenerate if max ΔE > 10.
- Composition validation: VLM rubric check against style references.
- Resize to target sizes (sharp premultiplied-alpha resize).
Full-set propagation
Workflow for generating N illustrations:
- Generate illustration #1 with the brand bundle and the brief.
- Human gates: accept / regenerate / tweak.
- On accept: add illustration #1 to the style reference set.
- Subsequent illustrations pull the whole augmented reference set → style locks progressively tighter.
- After 3–4 accepted illustrations, train a LoRA for even tighter lock on 20+ asset sets.
Output
illustrations/
├── empty-state-projects.png
├── empty-state-tasks.png
├── onboarding-welcome.png
└── meta.json # includes provenance + "set coherence score" across the batchDoes 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
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.

