Image design
Skill vikynofebriputra-creator/Orkas-Awesome-AgentSkills/creation/skills/image-design
Access a curated library of high-quality agents and modular skills for Orkas and other agent frameworks to accelerate task automation and development.From the repository description
npx -y skills add vikynofebriputra-creator/Orkas-Awesome-AgentSkills --skill image-designAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 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.
SKILL.md
5.8 KB, ~1.1k tokens by cl100k_base, as published. Nobody here has run it
Image Design
When to Use
Use this skill when the user wants to create or edit visual assets and needs a clear plan before execution:
- Posters, covers, banners, avatars, product images, social cards, icons, visual concepts, or image series.
- Prompt writing, style exploration, aspect-ratio selection, composition planning, and visual acceptance criteria.
- Model or tool selection across built-in image tools, Dreamina, Nano Banana / Gemini, ComfyUI, or other providers.
- Reference-image planning for style transfer, character consistency, product consistency, multi-image fusion, or series generation.
- Edit planning for inpainting, outpainting, background removal, restoration, relighting, upscaling, style transfer, or local post-processing.
Do not use this skill to claim that an image was actually generated or edited. If no executable image tool/provider is available, return only the brief, prompt, workflow, and acceptance checklist.
Workflow
- Clarify the visual job:
- final use case, audience, platform, required format, aspect ratio, brand constraints, text needs, source/reference images, and deadline.
- whether the user expects execution now or only a prompt/design plan.
- Convert the request into a creative brief:
- purpose, target viewer, subject, visual hierarchy, mood, style, composition, color, lighting, materials, and constraints.
- Choose the path:
- generate from text when the desired image does not exist yet.
- edit from an existing image when preserving identity, product, layout, or reference detail matters.
- use local deterministic processing for resize, crop, format conversion, compression, EXIF stripping, DPI, or watermarking.
- use review-only when the user asks whether an existing result is good enough.
- Route to an executable provider only when available:
- built-in image generation/editing tool when available in the current session.
dreaminafor Jimeng/Dreamina image or video generation through an already logged-in CLI.nano-bananafor Gemini / Imagen-style generation or editing when credentials and upload consent are available.comfyuionly after its local install/model/workflow safety has been reviewed.
- Write structured prompts:
- SUBJECT, CONTEXT, COMPOSITION, STYLE, LIGHTING, TEXT, TECHNICAL, CONSTRAINTS.
- Keep text inside generated images short. For long text, recommend post-production layout.
- For reference images:
- confirm usage rights and privacy.
- state what each reference should preserve and what may change.
- warn when provider reference-image count, upload policy, or consistency limits are unknown.
- For editing:
- choose the edit type, identify the protected area and edit area, define mask/selection needs, and preserve the original file.
- use non-destructive output paths and stepwise intermediate outputs for multi-step edits.
- End with a review plan:
- prompt adherence, technical quality, composition, target-platform fit, text correctness, safety/copyright/privacy risks, and next iteration.
Return Format
Return a concise plan:
## Visual Task
...
## Creative Brief
- Use case:
- Audience:
- Subject:
- Style:
- Composition:
- Aspect ratio / size:
- Constraints:
## Prompt
...
## Execution Path
- Recommended tool/provider:
- Why:
- Fallback:
- Requires user confirmation:
## Acceptance Checklist
-
## Limits
-
If execution happened through another tool, include output paths and what was actually verified. If execution did not happen, say so explicitly.
References
references/model-routing.md: provider and fallback decision rules.references/prompt-style-library.md: prompt structure, style patterns, and use-case templates.references/reference-edit-planning.md: reference-image consistency and edit workflow patterns.
External Dependencies
- Image generation or editing requires an available executable tool/provider. This skill alone is planning-only.
- Provider names, model IDs, prices, and availability change over time; important production work needs current provider documentation checked before execution.
- Reference images may be uploaded to third-party providers only after user consent.
Limits and Known Issues
- Do not guarantee exact text rendering, logo fidelity, face identity, product geometry, or character consistency.
- Do not bypass provider safety rules.
- Do not use private, copyrighted, branded, or personal reference images without user authorization.
- Do not promise commercial rights; identify licensing or review needs.
Examples
User: "帮我做一张小红书封面,主题是 AI 写作效率。"
Handling: create a 3:4 social cover brief, propose 2-3 styles, write a short-text prompt with title area and visual hierarchy, choose an available provider, and include a checklist for text readability and platform fit.
User: "按这张角色图做三张不同场景的系列图。"
Handling: identify the reference image as the character anchor, define fixed visual rules, write scene-specific prompts, warn about face drift, and require review after each generated result.
What ships with it: 3 files
4.6 KB alongside SKILL.md
references/
- model-routing.md1.7 KB
- prompt-style-library.md1.5 KB
- reference-edit-planning.md1.4 KB
Gives 0 of the 12 instructions most design frontend skills give in ~1.1k tokens
Counted across 1,169 of the 1,878 authors here whose files we hold, read 2026-08-07
- Use CSS variables for color consistencyin 72 of 1169, across 23 files
- Commit to one bold aesthetic direction before codingin 72 of 1169, across 27 files
- Match implementation complexity to the aesthetic visionin 70 of 1169, across 20 files
- Add atmospheric background effects and texturesin 57 of 1169, across 9 files
- Use unexpected spatial compositions and layoutsin 56 of 1169, across 8 files
- Implement real working codein 55 of 1169, across 7 files
- Vary themes and aesthetics across different designsin 48 of 1169, across 7 files
- Launch chromium in headless modein 47 of 1169, across 4 files
- Close the browser when donein 47 of 1169, across 4 files
- Run provided scripts with help flag firstin 47 of 1169, across 4 files
- Wait for network idle statein 47 of 1169, across 4 files
- Use descriptive selectors for elementsin 47 of 1169, across 4 files
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.