nano-banana-2

작성자: runcomfy-com

Google Nano Banana 2(Gemini 계열 플래시 등급 텍스트-투-이미지)로 RunComfy에서 이미지를 생성합니다. 이 스킬은 모델의 문서화된 프롬프트 패턴과 함께 제공되어, 동일 모델에 대한 단순 프롬프팅보다 더 정교한 출력을 얻을 수 있습니다. Nano Banana 2의 강점(빠른 반복, 이미지 내 타이포그래피 렌더링, 예측 가능한 프레임 구성, 선택적 웹 기반 컨텍스트), 해상도 등급별 가격, 안전 허용 범위 다이얼, 그리고 Nano Banana Pro / GPT Image 2 / Flux 2 / Seedream으로 전환해야 하는 경우를 문서화합니다.

npx skills add https://github.com/runcomfy-com/skills --skill nano-banana-2

Nano Banana 2 — Pro Pack on RunComfy

runcomfy.com · Model page · GitHub

Google Nano Banana 2 — the flash-tier text-to-image model in the Gemini family — hosted on the RunComfy Model API. Optimized for ideation, social-thumbnail batches, and rapid drafts with strong in-image typography.

npx skills add agentspace-so/runcomfy-skills --skill nano-banana-2 -g

When to pick this model (vs siblings)

Nano Banana 2 is the flash-tier of the Google image-gen line. Pick it when iteration speed and predictable framing matter more than maximum detail.

You wantUse
Rapid drafts, social thumbnails, batch variantsNano Banana 2
In-image typography with predictable renderingNano Banana 2
Web-grounded image (current events / real entities)Nano Banana 2 + enable_web_search
Image edit (preserve subject, swap background)Nano Banana Edit (sibling skill)
Heavy stylization, painterly lookFlux 2
Maximum prompt adherence + multilingual textGPT Image 2
2K–4K hero shots, max realismSeedream 5
Hyperrealistic portraitNano Banana Pro

If the user said "Nano Banana" / "nano-banana-2" / "Gemini image" explicitly, route here regardless. If they said "Nano Banana" without specifying 2 vs Pro, default to Pro for portraits and 2 for everything else.

Prerequisites

  1. RunComfy CLInpm i -g @runcomfy/cli
  2. RunComfy accountruncomfy login opens a browser device-code flow.
  3. CI / containers — set RUNCOMFY_TOKEN=<token> instead of runcomfy login.

Endpoints + input schema

google/nano-banana-2/text-to-image

FieldTypeRequiredDefaultNotes
promptstringyesSubject-first description.
num_imagesintno11–4. Use 4 for ideation rounds.
seedintno0Reuse for reproducibility.
aspect_ratioenumnoautoauto, 21:9, 16:9, 3:2, 4:3, 5:4, 1:1, 4:5, 3:4, 2:3, 9:16.
resolutionenumno1K0.5K (drafts), 1K (default), 2K (final), 4K (max).
output_formatenumnopngpng, jpeg, webp.
safety_toleranceintno41 (strict) – 6 (permissive).
limit_generationsboolnotrueLimit each prompt round to one generation.
enable_web_searchboolnofalseAdds web grounding (extra cost + latency).

For image edit (preserve subject + apply changes), see the sibling nano-banana-edit skill.

How to invoke

Default draft (1K, square, png):

runcomfy run google/nano-banana-2/text-to-image \
  --input '{"prompt": "<user prompt>"}' \
  --output-dir <absolute/path>

Vertical 4-up batch for ideation:

runcomfy run google/nano-banana-2/text-to-image \
  --input '{
    "prompt": "<user prompt>",
    "num_images": 4,
    "aspect_ratio": "9:16",
    "resolution": "0.5K"
  }' \
  --output-dir <absolute/path>

Final at 2K with seed lock:

runcomfy run google/nano-banana-2/text-to-image \
  --input '{
    "prompt": "<user prompt>",
    "resolution": "2K",
    "aspect_ratio": "16:9",
    "seed": 42
  }' \
  --output-dir <absolute/path>

Web-grounded (current event / real entity):

runcomfy run google/nano-banana-2/text-to-image \
  --input '{
    "prompt": "<prompt referencing a real-world event from this week>",
    "enable_web_search": true
  }' \
  --output-dir <absolute/path>

Prompting — what actually works

Subject-first declarative grammar. "A cinematic close-up portrait of an American woman standing under neon lights in rainy Tokyo, shallow depth of field, reflective wet streets, ultra-detailed, realistic skin texture" — primary subject, then action, environment, style, camera. Front-load subject; trail with directives.

Exact text quoting for in-image typography. "The label reads 'AURA' in clean bold sans-serif, centered, white on black" — quote the literal characters. Specify placement and font style. Don't say "with the brand name on it" and hope.

Consistent seeds for refinement. Lock seed when iterating a single prompt across small variants — keeps composition stable.

Web-grounding, sparingly. Turn on enable_web_search only when the prompt names current events / real entities. Adds latency + cost; off by default.

Don't conflict styles. "minimalist + ornate + retro + cyberpunk" cancels. Pick 1–2 anchors.

Anti-patterns:

  • Trying to verbally describe a stable subject identity — use the edit endpoint with image refs instead.
  • Asking for resolutions outside the 4 tiers → 422.
  • Aspect ratios outside the 11 supported values → 422.
  • Non-quoted in-image text → unpredictable rendering.

Where it shines

Use caseWhy Nano Banana 2
Marketing draft thumbnails (batch of 4)Fast iteration at 0.5K, then promote winner to 2K
Social-platform-nativeWide aspect ratio support including 9:16, 4:5, 21:9
In-image typography for posters / cardsPredictable text rendering when characters are quoted
Web-grounded current-event imageryenable_web_search integrates fresh info
Reproducible variant testingStrong seed + consistent framing

Sample prompts (verified to produce strong results)

Cinematic portrait (page example):

A cinematic close-up portrait of an American woman standing under neon
lights in rainy Tokyo, shallow depth of field, reflective wet streets,
ultra-detailed, realistic skin texture

Brand-asset card with quoted text:

A minimalist 16:9 product card: a matte black ceramic mug centered on a
soft warm-grey paper background, rim highlight from upper-left, the
headline "Brewed Quietly" in clean bold sans-serif top-right, balanced
negative space below, e-commerce ready, clean studio lighting

Vertical platform-native:

A 9:16 vertical hero for a wellness brand: a single ceramic teacup on a
linen runner, soft morning side-light, the words "Slow Down" in
hand-drawn serif large at the top, gentle steam rising, neutral color
palette, uncluttered

Limitations

  • Still images only. No video on this endpoint.
  • Max 4 outputs per request.
  • Web search adds latency + cost — only enable on demand.
  • 2K / 4K cost more — default to 1K unless user asked for higher.
  • For image edit, use the /edit endpoint — not this one.

Exit codes

codemeaning
0success
64bad CLI args
65bad input JSON / schema mismatch
69upstream 5xx
75retryable: timeout / 429
77not signed in or token rejected

Full reference: docs.runcomfy.com/cli/troubleshooting.

How it works

The skill invokes runcomfy run google/nano-banana-2/text-to-image with a JSON body matching the schema. The CLI POSTs to https://model-api.runcomfy.net/v1/models/google/nano-banana-2/text-to-image, polls the request, fetches the result, and downloads any .runcomfy.net/.runcomfy.com URL into --output-dir. Ctrl-C cancels the remote request before exit.

Security & Privacy

  • Token storage: runcomfy login writes the API token to ~/.config/runcomfy/token.json with mode 0600 (owner-only read/write). Set RUNCOMFY_TOKEN env var to bypass the file entirely in CI / containers.
  • Input boundary: the user prompt is passed as a JSON string to the CLI via --input. The CLI does NOT shell-expand the prompt; it transmits the JSON body directly to the Model API over HTTPS. No shell injection surface from prompt content.
  • Third-party content: image / mask / video URLs you pass are fetched by the RunComfy model server, not by the CLI on your machine. Treat external URLs as untrusted; image-based prompt injection is a known risk for any image-edit / video-edit model.
  • Outbound endpoints: only model-api.runcomfy.net (request submission) and *.runcomfy.net / *.runcomfy.com (download whitelist for generated outputs). No telemetry, no callbacks.
  • Generated-file size cap: the CLI aborts any single download > 2 GiB to prevent disk-fill from a malicious or runaway model output.

runcomfy-com의 다른 스킬

video-inpainting
runcomfy-com
Region edits across video frames on RunComfy via the `runcomfy` CLI — remove an object that appears across many frames, clean up wires or watermarks, replace a region with matching motion. Routes across Wan 2-7 edit-video (default, prompt-driven region edits with spatial language), Lucy Edit Restyle (identity-stable region-aware restyle), and Seedream 4-0 edit-sequential (when treating the clip as a frame stack). Picks the right route based on whether the change is prose-driven,...
videocreativemedia
runcomfy-cli
runcomfy-com
Run any model on RunComfy from the command line. The `runcomfy` CLI is one binary, one auth, hundreds of model endpoints — image generation, image edit, video generation, image-to-video, lip-sync, face swap, video edit, inpainting, outpainting, extend, ControlNet, relight, upscale, LoRA training and more. Submit a request, poll for status, download the output. This skill teaches the agent how to install, authenticate, discover model schemas, invoke models, stream / poll / no-wait, script in...
creativemediaapi
image-to-video
runcomfy-com
We need to translate the given text from English to Korean. The text describes a skill called "image-to-video" but the instruction says not to include the name unless it appears in the source text. The name "image-to-video" does appear in the source? Actually the source text starts with "Animate any still image on RunComfy — this skill is a smart router..." The name "image-to-video" is not explicitly in the source text; it's given as the directory item type name. So we should not include it. The instruction says: "Do not include the name unless it appears in the source text." It does not appear. So we translate only the text inside <text>. We need to preserve product names, protocol names, URLs, numbers, technical terms. So "RunComfy", "HappyHorse 1.0 I2V", "Arena #1", "Wan 2.7", "audio_url", "Seedance 2.0 Pro" should remain as is. Also "i2v" is a
creativevideomedia
flux-2-klein
runcomfy-com
RunComfy에서 Flux 2 Klein(Black Forest Labs의 Flux 2 경량 고속 변형)으로 이미지를 생성합니다. 모델의 문서화된 프롬프트 패턴이 함께 제공되어, 동일 모델에 단순 프롬프트를 입력하는 것보다 더 정교한 결과를 얻을 수 있습니다. Flux 2 Klein의 장점(서브초 지연 시간, 다중 참조 브랜드 스타일링, 선언적 주제 우선 프롬프트), 단계 수 전략(빠른 반복 시 4~8단계, 정교화 시 약 25단계), 9B 대 4B 변형 간의 장단점, 그리고 Flux 2 Pro로 전환해야 하는 경우 등을 설명합니다.
creativeimageresearch
ai-avatar-video
runcomfy-com
Create AI avatar, talking-head, and lip-sync videos on RunComfy via the `runcomfy` CLI. Routes across ByteDance OmniHuman (audio-driven full-body avatar), Wan-AI Wan 2-7 (audio-driven mouth sync via `audio_url` on a portrait), HappyHorse 1.0 (Arena #1 t2v / i2v with in-pass audio), and Seedance v2 Pro (multi-modal cinematic with reference audio + reference subject). Picks the right model for the user's actual intent — UGC voiceover, virtual presenter, dubbed product demo, lip-synced...
videocreativemedia
nano-banana-edit
runcomfy-com
Google Nano Banana 2(이미지 간 이미지 편
creativeimageapi
wan-2-7
runcomfy-com
We need to translate the given text from English to Korean, preserving the name "wan-2-7" and other technical terms. The instruction says to translate only the text inside <text>, and not to include the name unless it appears in the source text. The name "wan-2-7" appears in the source text, so we keep it as is. Also preserve "RunComfy", "Wan-AI", "HappyHorse 1.0", "Seedance 2.0", "Kling", "LTX 2", "runcomfy run wan-ai/wan-2-7/text-to-video", "CLI", and URLs or technical terms. The text describes generating text-to-video with Wan 2.7, its strengths, schema, routing alternatives, and trigger phrases. We need to output only the translated text, no extra commentary or labels. The target language is Korean. Let's translate carefully: "Generate text-to-video with Wan 2.7 (Wan-AI's flagship motion model) on
creativevideomedia
lipsync
runcomfy-com
We need to translate the given text into Korean, preserving the specified names: lipsync, RunComfy, runcomfy, ByteDance OmniHuman, Sync Labs sync v2 / Pro, Kling lipsync, Creatify lipsync. Also preserve URLs, numbers, technical terms. Do not add any extra commentary or labels. The text is a description of an agent skill. Translate only the text inside <text>. The name "lipsync" appears in the first line as "Lip-sync" but we preserve it as "lipsync" (the name to preserve). Actually the instruction says "Name to preserve: lipsync" so we should keep that exact casing? The source has "Lip-sync" but we should preserve the name as given? The instruction says "preserve product names, protocol names, URLs, numbers, and technical terms." And "Name to preserve: lipsync" - likely we should keep it as "lipsync" even if source has hyphen? But the source says "Lip-sync" - I think we should keep
creativevideomedia