executing-plans
executing-plans
Use when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available
local-inferenceRoutes InfiniteYou-FLUX self-contained identity-preserving image generation through the bundled runtime helper, model variants, control images, LoRA options, and CUDA memory settings.
Independent GitHub snapshot · Automated classification · Original documentation governs
Use this sub-skill when a task asks how to run, adapt, debug, or validate local InfiniteYou-FLUX image generation from an identity image and text prompt. The bundled helper uses this skill's runtime/pipelines/ implementation by default, so normal generation does not require the original repository checkout.
InfUFluxPipeline signatures and parameter semantics.aes_stage2 and sim_stage1 model variants.--cpu-offload, --quantize-8bit, or both to reduce peak VRAM.InfUFluxPipeline.--cpu-offload is not CPU-only execution.python scripts/run_infinite_you_flux.py --dry-run \
--id-image path/to/id.jpg \
--prompt "A person, portrait, cinematic" \
--model-dir models/InfiniteYou \
--base-model-path models/FLUX.1-dev \
--cpu-offload --quantize-8bit
python scripts/run_infinite_you_flux.py --check-only \
--id-image path/to/id.jpg \
--prompt "A person, portrait, cinematic" \
--model-dir models/InfiniteYou \
--base-model-path models/FLUX.1-dev
--dry-run or --check-only.A good local-inference answer should name the exact generation inputs, model variant, CUDA/memory strategy, model path/access assumptions, whether downloads are allowed, and validation signal. It should avoid telling the user to open or run source-repo scripts directly; use the bundled helper or describe an equivalent API call against the bundled runtime.