Skip to content

Cassiiopeia/projectops / skills/pro-image

pro-image

Verified

Make image assets (backgrounds, characters, icons, illustrations, items) that fit the project's own style: you write the prompt from a per-repo harness, Codex or Antigravity draws it, the CLI fixes size and transparency. Use for 'make an image', 'draw', 'generate an icon'.

Image: assets that look like this project

When to use

  • "Make a background / character / icon / illustration / item for this screen", "draw it", "regenerate the art", "several expressions of this character", in any language
  • "What style fits this project?", "show me a few styles"
  • Use it on your own whenever a task needs a new raster image (an empty state, a store graphic, a game scene). Do not draw such images with SVG or code unless every provider failed.
SituationSkill
A new image assetthis one
Screen layout mockups to compare in the browserpro-ui-design (it can place images made here)
Moving a Figma design into codepro-figma

Talk to the user in their language. Apply the absolute rules in ../references/common-rules.md.

You write the brief and the prompt and judge every result. The CLI only runs the image tool, collects the file, fixes format, size and transparency, and records history.

What the user sees

The user should see a short line while it works ("making 2 background candidates, about 3 minutes") and then the finished image. Do not narrate background removal, resizing, retries or prompt edits; do not show raw or failed images. If something cannot be met (a tool is missing, the same requirement failed twice), say it in one line with the best result.

Goal → command

Every command is PYTHONIOENCODING=utf-8 python3 ~/.projectops/bin/projectops_cli.py image <command> (Windows: python). Output is always JSON with ok, code, summary, next.

GoalCommandDetails
Which tools are ready, in what orderprovidersreferences/providers.md
This repo's art memory (style, characters, references)harness [--init] [--character <id> ...]references/harness.md
The guide for a kind of image + its approved promptskind <background|character-sheet|sprite|icon|illustration|item|...>references/kinds/
Generate one image, finished to specrun --name <stem> --prompt <file> --size WxH [--alpha] [--ref <img> ...] [--provider <name>] [--kind <kind>]below
Several candidates side by side, numberedboard <img> ... --out <png>references/style-explore.md
Remove a background from any imageremove-bg <img> --out <png> [--key-color "#00FF00"] [--mode flood|global]
Fit an image to a sizefit <img> --out <png> --size WxH [--mode cover|contain]
Check size and transparencycheck <img> [--size WxH] [--alpha]
Record the user's decision · read past onesrecord --name <stem> --status approved|rejected [--placed-at <path>] [--note "..."] · history

Quick path

A one-off picture ("just make me a cat image", a throwaway test, no app placement): skip the harness and style explore. Write a short English prompt with size and background, run, Read the result, show it. Ask nothing unless the size or the background is truly unknown. Use the full flow below when the image goes into an app.

Flow

  1. Tools. providers. On ask_priority, ask the user once which ready tools to use and in what order, and save image.priority (references/providers.md). Default order: codex > antigravity > claude-vector.
  2. Harness. harness. On no_style: if the app already has art, --init and fill STYLE.md from it; if not, or the user wants to see options, run the style explore (references/style-explore.md) and let them pick.
  3. Brief. Read the screen that will use the image, then write the numbered brief: purpose and placement, final size, background (opaque or --alpha), style anchor, subject, composition and empty zones, light, consistency anchors, must-nots (references/prompting.md §1). Ask the user only what the code cannot tell you.
  4. Prompt. kind <kind>, then write the prompt in English in the order of references/prompting.md §2, reusing what worked in approved_examples. Save it to a file in your scratch folder.
  5. Run. run ... in the background (each run takes 1-5 minutes; run several one after another, not at once). The CLI appends the output rules, converts to PNG, removes a fake or keyed background, fits the size and checks it.
  6. Judge. Open image.path (the .final.png) with Read and check every brief line. problems lists spec failures. A transparent image can look like it has a dark glow when read directly; judge it on board <img> --out <png> (gray backdrop) instead. Retry a failed content line once with that line stronger; on provider failures follow next.
  7. Show. Show only the finished image (or one board for several). Ask for approval with your agent's choice prompt (AskUserQuestion in Claude Code; a numbered list elsewhere) when there is a choice. If a pro-ui-design session is open, place the candidates there instead.
  8. Place and remember. Convert to the app's format and put it where the brief said; record --status approved --placed-at <path>. Turn any lasting feedback into a line in STYLE.md or characters/<id>.md.

Codes

codeMeaningDo
okFinished and matches size and transparencyJudge the content yourself
spec_mismatchFinished but problems lists a size or alpha missFix with fit / remove-bg, or run again
ask_priorityNo saved tool orderAsk once, save image.priority
no_styleNo STYLE.md in this repoFill it or run the style explore
not_subscriptionCodex is signed in with an API keyAsk the user to codex login with ChatGPT, or use the next tool
provider_missing · image_unavailable · timeout · no_imageThe tool could not deliverNext provider in priority (references/providers.md)
quota_exhaustedThe tool's image quota is used up (quota.reset_in)Follow next: short wait → retry once, long → next provider now, and tell the user when it resets
agent_drawsThe chosen provider is claude-vectorDraw SVG yourself, render it, check
postprocess_failedConversion or resizing failedraw_image is kept; install Pillow (pip install pillow) or ImageMagick

Shared references

DocumentRead when
../references/common-rules.mdAlways, at start: absolute rules, confirmation gates, issue state, push
../references/agent-conduct.mdWhen a tool is missing or you are about to say it cannot be done
../references/config-rules.mdWhen reading or writing ~/.projectops/config/config.json

Customize

Your own language, tone and rules apply: see ../references/preferences.md. Read them once at the start with SKILL_ID=pro-image. Keys for this skill: the common language, tone, rules only. Behavior is under config (image section: priority, providers, harness_dir, require_subscription); project art memory is the repo harness (references/harness.md). Preferences change presentation only; approval gates and secret protection stay in force.

Never

  • Never use an API-key login for Codex unless the user set image.require_subscription: false.
  • Never commit candidates. They stay in ~/.projectops/image/<owner__repo>/runs/; only the approved, converted file goes into the app, and only small approved references go into docs/image-harness/refs/.
  • Never put text, logos or brand marks of real companies into generated images.
  • Never use art the project does not own as a reference (another game's characters, a stock photo). References shape the output; use the app's own approved art.
  • Generated images follow the drawing tool's terms (OpenAI for Codex, Google for Antigravity). When the asset is for a commercial release, tell the user once which tool made it so they can check those terms.
  • Never replace an approved asset without showing the new one first.
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 469kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 321kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 321kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 321kUpdated Claude CodeCodexVerifiedInstall