Skip to content

iart-ai/generative-illustration-skills / skills/generative-illustration

generative-illustration

Verified

This skill should be used when the user asks to "make an animated illustration", "animate an illustration", "make a generative motion piece" / "动态平面", "turn AI-generated art into something that moves", "make a poetic or ambient motion piece / motion poem", "make a visual metaphor", or "combine AI-generated visuals with code-driven motion". Covers generating isolated illustration assets with AI, compositing them as sprites, frame-accurate deterministic rendering, and the craft of expressive, concept-driven motion. NOT for data charts (use chart-animation), pure text (use kinetic-typography), or 3D/particles (use webgl-animation).

FileKindSize
SKILL.mdskill md9.3 KB
references/asset-pipeline.mdmarkdown3.2 KB
references/craft.mdmarkdown2.6 KB
references/render-harness.mdmarkdown3.3 KB

references/craft.md

View on GitHub
# Craft — what makes a piece good, not just moving

## The first rule: the visual comes from the concept — never default to one device

The motion vocabulary must be derived from *this idea*. **Reusing one device — "a thing grows up from the ground" — across unrelated concepts is the #1 way these go stale.** If you reach for "something grows" a second time, stop and ask what the concept actually looks like.

| Concept | Native visual (✓) | Lazy default (✗) |
|---|---|---|
| Prompting / iteration | a garden: prompts fall, most wither, one blooms | (here a plant is right — the concept is botanical) |
| **Compounding** | a dot **doubling** until it floods the screen + a live counter | a tree growing |
| **The blank page / cursor** | a lonely blinking cursor → first word → text **floods** the page | a sprout growing from the word |
| Overload / focus | tabs/windows multiplying into noise, then all but one close | — |

## Rhythm: resolve → a beat of stillness → reflect

The closing line is a *looking-back* statement; it only lands after the action stops. Let the motion finish, hold a beat, **then** reveal the slogan. Never overlap the conclusion with things still moving (it reads as "the story isn't over yet").

## Restraint

Motion needs fewer elements than static design — too many and it's noisy in motion. Keep only the core. (流白: "只留核心要素,避免用力过猛.")

## Causality

Tie cause → effect literally: an input lands → something happens *at that spot*. Loosely-related parallel events read as random noise. (Prompt Garden: each falling prompt lands and grows a plant at that exact point.)

## Spotlight the hero

When one element matters, dim the rest and lift it — a halo, a scale, a color shift.

## Easing

Never linear on anything a viewer reads. Ease the *value*, not just opacity. Match the curve to the idea: ease-in (slow→explosive) for compounding; a count-up settling for a number; overshoot for a small pop.

## Semantics — don't self-sabotage

If the piece depicts failure/withering, do **not** label it with your own product's features (it reads as "our product fails at its core jobs"). Use neutral or process language. (We changed falling "prompts" from product feature names — "logo reveal", "bar chart" — to iteration words — "warmer", "again", "almost" — and made the one that blooms say "yes.")

## Text content

Plain, concrete, lowercase-casual or quiet-serif depending on tone. The line should feel earned, not slapped on. Two-beat structure works well: a setup during the action, a payoff after it resolves.
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: 472kUpdated 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: 323kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 323kUpdated 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: 323kUpdated Claude CodeCodexVerifiedInstall