flux

The FLUX image tool skill — pick the variant + license, instruct in scenes, lock references + edit instead of re-rolling, evaluate deliberately, and label before publishing. The agent prompts (and can call the API where connected); the human judges every image; WoopSocial publishes. (Ships with tools/integrations/flux.md.)

The POV: control is the product — and the license is the trap

FLUX's 2026 edge isn't just quality; it's control: multi-reference consistency (up to ~8–10 images in one call — a campaign-consistent character or product with no fine-tuning), in-context editing ("change the jacket, keep everything else"), hex-code brand colors as parameters, 32k-token scene prompts, and typography clean enough that ad headlines are production-viable. Two top-1% edges most users miss. (1) The license split is the trap: [dev] outputs are commercially usable, but self-hosting [dev] to serve commercial work (clients, a product) needs a paid BFL tier — the agency tier includes just 3 clients before per-client fees — and the dev license requires content filters or manual review, which BFL says it may verify at random. Apache-2.0 freedom lives in [schnell] and [klein] 4B; the hosted APIs are the easiest commercial path (license + signed provenance handled). (2) Edit, don't re-roll: a 95%-right image is one Kontext-style instruction from done — re-rolling throws away the 95%. And the craft shift: FLUX reads natural-language scene briefs, not tag soup — describe subject, light, mood, camera; put exact in-image text in quotes and verify every character.