Image Studio — actionable resource checklist (E4c)

Image

In E4b the required-resources list was read-only — a static amber reminder of assets you'd have to add later. In E4c that same checklist becomes actionable: every missing resource can be generated on-platform (Higgsfield), composed into a DIY prompt, uploaded, or picked from the library — each row a real GenerationResource node. Accent #7c3aed marks the engine. Light app theme · clickable. No caching — refresh for latest.

E4b — read-only
Assets you'll add in the Studio
  • ▸logo — your brand mark (placed bottom-right)
  • ▸product — the actual Summer Splash bottle

A static warning. It tells you what's missing — but the only way to resolve it is to leave, find the asset, come back, and upload by hand.

E4c — actionable
Required resources 0 of 2 ready
Logo
Your brand mark · placed bottom-right
Needed
Product
The actual Summer Splash bottle
Needed

The same two assets — now each resolves in place: ⚡ generate on-platform, ✦ compose a DIY prompt, upload, or pick from the library. Recursion stays flat.

What changed in E4c. The required-resources checklist — read-only in E4b — is now actionable. Each missing resource carries a per-row mode toggle (⚡ on-platform via the Higgsfield connector vs ✦ prompt / DIY) plus actions to upload or pick from the library. On-platform mode mounts an inline per-resource generator (ProviderModelPicker → compose & guide → refine-with-history → candidates → “Use this”). Recursion stays flat: a generated resource fills its own node — it never spawns its own nested checklist. Provider-key boundary: per-resource Generate resolves creds via resolveMediaProviderKey (the Higgsfield connector) and spends a media credit; only TEXT compose & refine ride the free platform key.
Pages — Summer Splash · Hero Image example
01
Checklist states
The actionable checklist end-to-end: every row state side by side — have (with use-guide), needed, and generating — across both per-row modes (⚡ on-platform and ✦ DIY). This is the shape that replaces the amber reqbox.
Flagship Open
02
Per-resource generate
A needed row expanded into the inline on-platform generator: Higgsfield-only ProviderModelPicker, composed prompt + guide, refine-with-history, AssetPicker refs, candidate grid — then “Use this” fills the node.
Open
03
DIY & manual
The ✦ prompt / DIY arm: a composed prompt + guide + Copy, then Upload-back or Pick — no Generate button. The only arm for the manual google-flow hand-off and BYOK ElevenLabs voice.
Open
04
Generate a reference (Image)
The greenfield path: a missing image reference goes from empty → upload or generate on-platform → filled node. Shows the before/after of a single resource resolving end-to-end.
Open
05
Flat recursion
The key invariant, made visible: generating a resource fills its own node and stops — it does not open a fresh required-resources checklist inside itself. One level, always.
Open
The seam. These pages keep the studio shadcn chrome (cards, candidate grid) hosting the gua-* engine — but the read-only .reqbox is replaced by an actionable .reschecklist. Each row is a GenerationResource: role · status · per-row mode toggle · actions. Start at Checklist states for the full picture.