skills/imagegen/SKILL.md
Use this skill when the user asks to generate, create, or edit images — concept art, product shots, icons, logos, textures, illustrations, or batch variants. Covers generation from text prompts and editing existing images (background removal/replacement, inpainting, style transfer, object removal). MUST use when the user says "generate an image," "create an icon," "make me a picture," "I need a hero image," "swap/remove the background," "edit this photo," "make it look like [style]," "batch of icons," "placeholder art," or describes needing any visual asset casually. Also triggers on: game assets (sprites, textures, UI icons), website visuals (hero images, blog headers), product photo edits, logo generation, infographics, or any request to produce an image from a description. Runs the bundled CLI (scripts/image_gen.py) and requires GEMINI_API_KEY or GOOGLE_API_KEY.
npx skillsauth add cuozg/oh-my-skills imagegenInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Generate or edit images using Google Gemini Imagen API. Defaults: imagen-4.0-generate-001 (generate), imagen-3.0-capability-001 (edit). Use bundled CLI scripts/image_gen.py.
tmp/imagegen/ (one job per line), run once, delete afterreferences/prompt-augmentation.md (don't invent new requirements)python <skill-dir>/scripts/image_gen.py <command> <args>| Use case | Ratio |
|----------|-------|
| App icon, avatar, logo, texture | 1:1 |
| Website hero, banner, cinematic | 16:9 |
| Mobile wallpaper, story, portrait | 9:16 |
| Blog header, product card | 4:3 |
| Infographic, poster | 3:4 |
python "<skill-dir>/scripts/image_gen.py" <command> <args>
# Or via run_skill_script:
run_skill_script(skill="imagegen", script="scripts/image_gen.py", arguments=["generate", "--prompt", "...", "--dry-run"])
--person-generation ALLOW_ADULT if appropriate.Always diagnose which part caused the issue — don't re-run same prompt.
GEMINI_API_KEY or GOOGLE_API_KEY for generationGOOGLE_CLOUD_PROJECT + GOOGLE_CLOUD_LOCATION + ADC.env from: --env-file → <project>/.env.local → <project>/.env → ~/.env.local → ~/.env.env file--force when re-running to overwrite previous attemptgoogle-genai) — never raw HTTPtmp/imagegen/ · Final output: output/imagegen/references/prompt-augmentation.md — taxonomy, spec template, augmentation rulesreferences/cli.md — commands, flags, recipesreferences/image-api.md — API params, models, edit reference imagesreferences/prompting.md — prompting principles, iteration patternsreferences/sample-prompts-*.md — copy/paste prompts by category (generate, edit, website, game, asset-types)tools
Generate Unity raster image assets through Unity MCP: game sprites, item art, backgrounds, UI icons, portraits, concept images, transparent cutouts, image edits, upscales, background removal, and Unity scene or Game View screenshots. Use when a Unity project needs image files imported under Assets or screenshots captured from the editor. Do not use for meshes, audio, animation, materials, gameplay code, UI Toolkit layout, or generic non-Unity image generation.
tools
Create Unity technical solution documents from user requirements, feature ideas, bug goals, specs, or codebase problems. Use when the user asks for a technical approach, architecture, implementation strategy, solution options, feasibility analysis, system design, or "how should we build/fix this" for Unity runtime, Editor, tools, assets, data, UI, WebGL, SDKs, or production pipelines.
tools
Orchestrate Unity Editor via MCP (Model Context Protocol) tools and resources. Use when working with Unity projects through MCP for Unity - creating/modifying GameObjects, editing scripts, managing scenes, running tests, or any Unity Editor automation. Provides best practices, tool schemas, and workflow patterns for effective Unity-MCP integration.
development
Convert a spec document into an implementation TODO list in the same spec folder. U se when the user says goal-todo, todo from spec, generate tasks from spec, turn this spec into todos, create implementation checklist, extract tasks, or asks to read a Docs/Specs design doc and produce what must be implemented. Includes UI/UX review and codebase investigation before writing the checklist. Do not use for implementing the tasks, creating new goal files, writing test cases, or verifying completed work.