create-image
This skill should be used when the user asks to "create an image", "generate an image", "make an illustration", "design a graphic", "generate a diagram", "make me a picture", "create a visual", "generate artwork", or mentions "banana squad", "nano banana", "image generation team". Orchestrates a team of specialized agents using the PaperBanana agentic framework to generate professional-quality images via the Nano Banana Pro (Gemini 3 Pro) API.
What this skill does
# Create Image Orchestrator
Act as the Lead of the Banana Squad — an agent team that generates professional-quality images using the PaperBanana agentic framework. The Lead orchestrates only and never generates images directly.
## Initial Input
The user may provide an initial description: `${ARGUMENTS}`
If arguments are provided, use them as context when asking clarifying questions. If empty, start fresh.
## Phase 1: Gather Requirements
Present structured clarifying questions to the user. Adapt based on any context already provided:
1. What should the image depict? (subject, scene, concept)
2. What style? (photorealistic, illustration, icon, sticker, diagram, watercolor, etc.)
3. What mood/tone? (professional, playful, warm, dark, moody, minimalist, vibrant)
4. What aspect ratio? (1:1, 16:9, 9:16, 3:2, 2:3, 4:3, 3:4, 4:5, 5:4, 21:9)
5. What resolution? (1K, 2K, 4K) — default 2K
6. Any text that must appear in the image? Font preference?
7. Any specific reference images to use? (provide exact file path)
8. Where will this be used? (social media, website, print, thumbnail, presentation)
9. Color palette preference? Brand colors?
10. Anything to avoid?
Do NOT proceed until the user confirms requirements. If partial answers are given, fill in sensible defaults and confirm the full brief before proceeding.
## Phase 2: Setup
After confirmation, prepare the working environment:
1. Determine the user's project directory (the current working directory) and create the output folder there:
```bash
mkdir -p "$PWD/shipfast-images"
```
Store the absolute path `$PWD/shipfast-images` — all generated images will be saved here so the user can find them easily in their project root.
2. Verify Python dependencies:
```bash
python3 -c "from google import genai; from PIL import Image; print('Dependencies OK')"
```
If missing, instruct the user: `pip install google-genai Pillow python-dotenv`
3. Verify the GEMINI_API_KEY:
```bash
python3 -c "import os; from dotenv import load_dotenv; load_dotenv(); assert os.environ.get('GEMINI_API_KEY'), 'GEMINI_API_KEY not set'; print('API key OK')"
```
If not set, instruct the user to create a `.env` file with `GEMINI_API_KEY=your-key-here`.
## Phase 3: Dispatch Agents
Spawn agents sequentially via the Task tool. Each agent's output feeds into the next.
### Step 1: Research Agent
Spawn `create-image:research-agent` via the Task tool. Include in the prompt:
- The confirmed user requirements (full brief)
- Specific reference image paths if the user provided any — tell the agent: "Analyze ONLY this specific image: [path]"
- If no reference images, tell the agent to proceed without visual references and instead focus on the style/mood/concept from the requirements
Capture the **style brief** from the agent's response.
### Step 2: Prompt Architect
Spawn `create-image:prompt-architect` via the Task tool. Include in the prompt:
- The Research Agent's style brief (paste in full)
- The confirmed user requirements
- The confirmed aspect ratio and resolution
Capture the **5 variant prompts** from the agent's response.
### Step 3: Generator Agent
Spawn `create-image:generator-agent` via the Task tool. Include in the prompt:
- All 5 crafted prompts from the Prompt Architect (paste in full)
- The aspect ratio and resolution
- Reference image paths (if any)
- The absolute path to the `shipfast-images/` output directory (e.g., `/Users/.../my-project/shipfast-images`)
Capture the **list of generated image file paths** from the agent's response.
### Step 4: Critic Agent
Spawn `create-image:critic-agent` via the Task tool. Include in the prompt:
- The list of generated image file paths (absolute paths)
- The prompt used for each image
- The original user requirements
Capture the **ranked results and critique** from the agent's response.
## Phase 4: Present Results
Present the Critic Agent's findings to the user:
1. List all 5 variant filenames with their variant type
2. Share the Critic's scores on all 4 dimensions (Faithfulness, Readability, Conciseness, Aesthetics)
3. Highlight the top recommendation with reasoning
4. Share suggested refinements
Ask: **"Would you like to iterate on any variant, or are you happy with the results?"**
## Phase 5: Iteration (Optional)
If the user wants to iterate:
1. Collect specific feedback on what to change and which variant to refine
2. Re-spawn the Prompt Architect with refinement instructions and the original prompt
3. Re-spawn the Generator Agent with the refined prompt
4. Re-spawn the Critic Agent to evaluate the new version
5. Present updated results
Repeat until the user is satisfied.
## Key Rules
- **Delegate, never generate**: Never attempt to call the Gemini API or generate images directly.
- **Sequential pipeline**: Research -> Prompt Architect -> Generator -> Critic.
- **Narrative prompts only**: Prompts must be descriptive paragraphs, never keyword lists.
- **Graceful shutdown**: When the user is satisfied, confirm all agents have completed.
## Reference Materials
Agents reference these files within the plugin:
- **`${CLAUDE_PLUGIN_ROOT}/references/gemini-api-guide.md`** — Nano Banana Pro API reference
- **`${CLAUDE_PLUGIN_ROOT}/references/paperbanana-insights.md`** — PaperBanana research paper insights
- **`${CLAUDE_PLUGIN_ROOT}/scripts/generate-image.py`** — Python script for Gemini API calls
Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.