claude/ai-resources-plugin/skills/nano-banana-prompt/SKILL.md
Create a high-quality image generation prompt for Google's Nano Banana 2 (NB2) model on Gemini.
npx skillsauth add amhuppert/my-ai-resources nano-banana-promptInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Generate optimized prompts for Google's Nano Banana 2 (Gemini 3.1 Flash Image) model. Transform user concepts into detailed, well-structured prompts that leverage NB2's strengths: natural language understanding, thinking mode, text rendering, character consistency, and image search grounding.
<user-request> $ARGUMENTS </user-request>Extract from the user's request:
If the request is too vague to produce a quality prompt (e.g., just "a cat"), use AskUserQuestion to clarify intent. Ask about style preference, mood, and intended use — but only ask what's genuinely ambiguous. A request like "a cyberpunk cityscape at night" has enough to work with.
Read references/prompting-guide.md for style vocabulary, composition terms, lighting terms, and prompt formula templates. Then construct the prompt following these core principles:
Build prompts using natural language sentences, not comma-separated keyword tags. NB2 is a reasoning model — brief it like a creative director, not a search engine.
Assemble these elements in order:
Append a thinking mode recommendation based on prompt complexity:
| Complexity | Thinking Mode | When to Use | |---|---|---| | Simple | Minimal (default) | Single subject, clear style, no text | | Moderate | High | Multi-element scenes, text rendering, specific composition | | Complex | Dynamic | Infographics, multi-character consistency, data visualization |
Present the output in this format:
## Nano Banana 2 Prompt
**Prompt:**
> [The full optimized prompt text]
**Recommended Settings:**
- **Thinking mode:** [Minimal / High / Dynamic]
- **Aspect ratio:** [ratio, e.g., 16:9, 1:1, 9:16]
- **Resolution:** [1K / 2K / 4K based on use case]
**Tips:**
- [1-3 specific tips for iterating on this particular prompt]
references/prompting-guide.md — Comprehensive Nano Banana 2 prompting reference including style vocabulary, composition terms, lighting terms, text rendering patterns, editing workflows, and example prompt formulastools
Use when picking or vetting a keyboard shortcut on macOS. Triggers include "what hotkey should I use for X", "is `<combo>` available", "does this shortcut conflict", "recommend a keybinding for…", "check `<combo>` against my setup", "pick a hotkey for…", or any mention of choosing/binding/changing a shortcut in WezTerm, tmux, Zed, Chrome, Claude Code, or macOS. Determines whether a proposed combo collides with OS-reserved bindings, app defaults, or the user's customizations, and recommends ergonomic alternatives when needed.
development
Detect and remove dead code with knip. Use when the user asks to "run knip", "find unused files", "find unused exports", "find unused dependencies", "clean up dead code", "remove dead code", "set up knip", "configure knip", "knip.json", "knip false positive", "knip CI", or mentions a `knip` config, dependency bloat, bundle bloat from unused imports, or tree-shaking unused exports. Covers the configuration-first workflow, confidence-gated deletion, framework-specific gotchas (Next.js 15+, Tailwind, Storybook, Jest, Bun's test runner and `bun build --compile`), monorepos, CI integration, and performance tuning.
tools
This skill should be used when the user asks to "set up react-scan", "install react-scan", "diagnose React re-renders", "find unnecessary renders", "find unstable props", "automate React render checks with Playwright", "react-scan + playwright", "measure component renders programmatically", "check why a React component is slow", or mentions React rendering issues, slow React interactions, render counts, or component-level perf attribution. Covers install across Next.js/Vite/Remix/script-tag/browser-extension, the lite headless API for CI, and the canonical render-attribution → fix → validate loop driven through Playwright.
documentation
This skill should be used when integrating source material into a knowledge base, including when the user asks to "integrate this document into the knowledge base", "add this transcript to the memory bank", "ingest this document", "update the knowledge base", "analyze a new source document", or "sync current-state docs with this source".