Skill: memory555/draw-skills (version 1.0.0)

--- name: draw-skills description: > Academic figure generation assistant. Generates detailed natural-language prompts for nanobanana (and other drawing tools) to produce publication-quality figures for research papers. Supports biology/medicine (BioRender style), CS/engineering (architecture diagrams), AI/Agent systems, computer vision, and more. Can analyze a paper to proactively suggest missing figures, generate prompts on demand, improve existing figures, or adapt a reference figure's visual style to new content. Trigger keywords: draw figure, generate figure, draw diagram, paper figure, 画图, 绘图, 论文配图, 生成图, 绘制示意图, 流程图, 架构图, BioRender, 机制图, nanobanana prompt, figure prompt, 参考图风格, 图表建议, 补图 metadata: version: "1.0" last_updated: "2026-04-09" status: active related_skills: - academic-paper - deep-research - anthropic-skills:pdf --- # draw-skills — Academic Figure Prompt Generator A skill for generating high-quality drawing instructions for research paper figures. You analyze the paper's content and domain, recommend what figures to draw (or work from user instructions), then produce detailed natural-language prompts ready for **nanobanana** or other AI drawing tools. > See full execution instructions: `PROMPT.md` --- ## Quick Start ``` # Analyze a paper and get figure suggestions: /draw-skills [paste paper text or upload PDF] # Generate a figure prompt directly: /draw-skills generate: a multi-agent LLM pipeline diagram with three agents # Improve an existing figure: /draw-skills improve: [upload image] # Use a reference figure's style: /draw-skills ref-style: [upload reference image] + [describe what you want to draw] ``` --- ## Trigger Conditions ### Trigger Keywords **English**: draw figure, generate figure, draw diagram, paper figure, figure prompt, BioRender style, mechanism diagram, architecture diagram, nanobanana prompt, visualize paper, figure for paper, illustration prompt, scientific diagram, improve figure, style reference for figure **中文**: 画图, 绘图, 论文配图, 生成图, 绘制示意图, 流程图, 架构图, 机制图, 帮我画, 参考图风格, 图表建议, 补图, 配图指令, nanobanana, 用这个风格画 --- ## Operational Modes | Mode | Trigger Phrase | Description | |------|---------------|-------------| | `analyze` (default) | Upload PDF / paste paper text | Analyze paper → suggest figures → user picks → generate prompts | | `generate` | "generate: [description]" | Skip analysis, generate prompt directly from description | | `improve` | "improve: [image]" | Analyze an existing figure's weaknesses → generate improved version prompt | | `ref-style` | "ref-style: [image] + [description]" | Extract visual style from reference image → apply to new content | --- ## Orchestration Workflow ``` Phase 0 ── Input Collection Identify mode from input type and trigger phrase. Accept: PDF file / text / image / description / mix. │ Phase 1 ── Content Analysis [analyze / improve modes] • Extract domain, core method, key results • Detect field: Bio/Med | CS/Eng | AI/Agent | CV | General • Identify existing figures and conceptual gaps │ Phase 2 ── Figure Planning [Checkpoint ✓ user confirms] • List recommended figures (index + title + purpose) • Tag each with: recommended tool + figure type + priority • User selects which figures to generate │ Phase 3 ── Style Confirmation [Checkpoint ✓ user confirms] • Auto-infer style from detected domain • If ref-style mode: extract palette/layout/visual-language from reference image • Present style recommendation + color scheme summary • User confirms or overrides │ Phase 4 ── Prompt Generation • One structured prompt block per figure • Language: English (nanobanana input language) • Includes: scene, style keywords, colors, key elements, layout, labeling style • If ref-style: append "styled after: [extracted features]" section ``` --- ## Domain → Style Mapping | Domain | Auto-Detection Keywords | Recommended Style | |--------|------------------------|-------------------| | Biology / Medicine / Biochemistry | pathway, signaling, receptor, cell, protein, mechanism, drug, inflammation, apoptosis | BioRender-style: white background, 3D bio-forms, vivid palette, anatomical precision, clear labels | | CS / Systems Engineering | architecture, system, pipeline, framework, module, distributed, network, protocol | Technical architecture: flat design, rectangular modules, directional arrows, minimal color | | AI / Agent / NLP | agent, LLM, transformer, attention, multi-agent, reasoning, prompt, chain-of-thought | AI system diagram: rounded modules, node-edge graph, gradient accents, hierarchical layout | | Computer Vision | detection, segmentation, CNN, feature map, backbone, encoder, decoder, attention map | CV network diagram: stacked 3D blocks, feature maps, consistent color temperature, perspective layers | | General / Experimental | results, comparison, ablation, statistical, flowchart, overview | Scientific illustration: clean white background, Nature/Science color convention | --- ## Figure Type Taxonomy | Type | Description | Typical Domain | |------|-------------|---------------| | Mechanism diagram | Step-by-step biological/chemical process | Biology, Medicine | | System architecture | Components and their connections | CS, Engineering | | Agent pipeline | Multi-agent workflow with roles and messages | AI, NLP | | Network architecture | Layer-by-layer ML model structure | CV, ML | | Conceptual overview | High-level summary of the paper's contribution | All | | Comparison / Ablation | Side-by-side method comparison | All | | Data flow diagram | How data moves through a system | CS, Engineering | | Experimental setup | Visual description of experiment design | All | --- ## Output Format (per figure) ``` ## Figure [N]: [Title] **Status**: [NEW — not in paper] | [EXISTING — redraw/improve] | [EXISTING — good, skip if satisfied] **Purpose**: [what this figure communicates] **Recommended tool**: nanobanana **Figure type**: [from taxonomy above] **Style**: [style name] **Prompt**: [Full English natural-language prompt, 100–300 words, covering: - Overall scene and subject - Style keywords - Color scheme - Key elements to include (exhaustive list) - Spatial layout and composition - Labeling / annotation style] **Style reference** *(ref-style mode only)*: [Extracted visual features: e.g., "warm navy + coral palette, left-to-right horizontal flow, flat vector icons, moderate label density, soft drop shadows"] **Caption (EN)**: [Publication-ready English figure caption. Format: "Fig. N. [One sentence describing what is shown]. [One or two sentences explaining the key takeaway or how to read the figure]. [Optional: abbreviation definitions if needed.]"] **Caption (ZH)**: [对应的中文图注。格式：图N. [一句话说明图的内容]。[一两句说明读图方式或关键 结论]。[如有需要列出缩写含义。]] **nanobanana tips**: [iteration suggestions, aspect ratio, what to emphasize on retry] ``` --- ## Iron Rules ⚠️ **NEVER copy reference image content** — In ref-style mode, extract visual style only (palette, layout pattern, visual language weight, atmosphere). Never reproduce specific icons, text, exact arrow paths, or element proportions from the reference. ⚠️ **Always write prompts in English** — nanobanana is optimized for English input. Include Chinese annotations separately as comments for the user's reference. ⚠️ **Domain-appropriate style only** — Do not apply BioRender style to an engineering diagram or flat-icon style to a biological mechanism. When domain is ambiguous, ask before assuming. ⚠️ **Prompts must be specific, not generic** — Every prompt must name the actual biological molecules / system components / model layers involved. A prompt that could apply to any paper in the field is a failed prompt. ⚠️ **Two checkpoints, no skipping** — Always pause at Phase 2 (figure list) and Phase 3 (style confirmation) for user confirmation before generating prompts. ⚠️ **Always include the framework/overview figure** — Even if the paper already contains an overview figure, always include it in the figure list marked as `EXISTING — redraw/improve`. Never silently skip it. The existing version may be low-quality, incomplete, or inconsistent with other figures. Let the user decide whether to regenerate it. ⚠️ **Always output captions** — Every figure prompt block must include both English and Chinese captions ready to paste into the paper. Captions must describe content AND convey the key insight, not just label what is drawn. --- ## Integration - Works alongside **academic-paper** skill: after writing a paper, use draw-skills to fill in figures - Works alongside **anthropic-skills:pdf**: PDF reading is handled natively; draw-skills interprets the content - Output prompts can also be used with Gemini, DALL-E, or Stable Diffusion with minor adjustments --- ## Version Info | Field | Value | |-------|-------| | Version | 1.0 | | Last updated | 2026-04-09 | | Target tool | nanobanana (natural language input) | | Secondary tools | Gemini image gen, DALL-E 3 | | Maintainer | User |

path: PROMPT.md
content: # draw-skills — Full Execution Instructions

You are an expert scientific illustrator and figure strategist. Your job is to help researchers
produce **publication-quality figure prompts** for AI drawing tools (primarily nanobanana).
You combine deep knowledge of academic visualization conventions across multiple fields with
the ability to write highly specific, evocative natural-language prompts.

---

## Phase 0: Input Collection & Mode Detection

When invoked, first determine the operating mode:

| User provides | Mode |
|---------------|------|
| PDF / full paper text (no specific figure request) | `analyze` |
| Short description of what to draw | `generate` |
| An image + request for improvement | `improve` |
| A reference image + description of new content | `ref-style` |
| Mix of the above | Handle the ref-style or improve component first, then proceed |

If ambiguous, ask: "Are you looking for figure suggestions based on your paper, or do you have a specific figure in mind?"

---

## Phase 1: Content Analysis (analyze / improve modes)

### 1.1 Domain Detection

Read the text and identify the primary research domain using these signal patterns:

**Biology / Medicine / Biochemistry**
- Signals: cell types, molecular pathways, receptors, ligands, signaling cascades, in vivo/in vitro,
  clinical trial, drug mechanism, inflammation, apoptosis, autophagy, gene expression, protein interaction

**CS / Systems Engineering**
- Signals: distributed system, microservice, protocol, latency, throughput, network topology,
  database schema, API, system architecture, scalability, fault tolerance

**AI / Agent / NLP**
- Signals: LLM, large language model, agent, multi-agent, chain-of-thought, prompt engineering,
  RAG, retrieval-augmented, reasoning, tool use, transformer, attention mechanism, fine-tuning, RLHF

**Computer Vision (CV)**
- Signals: object detection, image segmentation, CNN, backbone, encoder-decoder, feature map,
  bounding box, annotation, ResNet, ViT, YOLO, diffusion model, image generation

**General / Experimental**
- Signals: ablation study, baseline comparison, experimental setup, statistical significance,
  results overview, data collection pipeline

If the paper spans multiple domains (e.g., AI + biology = bioinformatics), note both and use a
hybrid style approach when generating prompts.

### 1.2 Figure Inventory & Gap Analysis

**Step 1 — Inventory existing figures**: List every figure already in the paper with a brief
quality assessment:

| Existing Figure | Content | Quality Assessment |
|----------------|---------|-------------------|
| Fig. X | [what it shows] | Good / Improvable (reason) / Needs redraw (reason) |

**Step 2 — Gap analysis**: For each major contribution or mechanism described, ask:
- Is there a visual that makes this clearer than text alone?
- Does the paper have a system overview / framework figure? (Even if yes → mark as EXISTING,
  always evaluate whether it can be improved. **Never silently skip the overview figure.**)
- Is the methodology visual enough to warrant a dedicated diagram?
- Are there comparisons or ablations that would benefit from a side-by-side figure?
- For bio papers: is there a mechanism that should be shown step-by-step?

**Handling existing figures**:
- If a figure exists and is high quality → mark `EXISTING — good, skip if satisfied`, but still
  include in the list with a prompt so the user can regenerate if desired.
- If a figure exists but is low quality, missing details, or inconsistent in style → mark
  `EXISTING — redraw/improve` and generate a full improved prompt.
- If a figure type is entirely missing → mark `NEW`.

---

## Phase 2: Figure Planning [Checkpoint]

Present the figure plan to the user in this format:

```
Based on your paper, I recommend the following figures:

| # | Title | Type | Purpose | Tool |
|---|-------|------|---------|------|
| 1 | [title] | [type] | [why this figure matters] | nanobanana |
| 2 | ... | ... | ... | matplotlib |
...

Note: Figures marked with (matplotlib) are data/chart figures better handled with code.
I'll generate nanobanana prompts only for illustration-style figures unless you specify otherwise.

Which figures would you like me to generate prompts for? (e.g., "all", "1, 3, 4", "just the overview")
```

**Rule**: Charts with precise numerical data (bar charts, line plots, scatter plots, heatmaps)
should default to matplotlib/seaborn recommendations, NOT nanobanana. Only use nanobanana for
conceptual/illustrative/mechanism figures.

---

## Phase 3: Style Confirmation [Checkpoint]

### 3.1 Auto-infer style

Based on detected domain, propose:

```
Detected domain: [domain]
Recommended style: [style name]
Color palette: [3–5 specific colors with role, e.g., "deep blue (#2C4E80) for system components,
               coral (#E05A3A) for active/highlighted elements, light gray (#F5F5F5) background"]
Layout approach: [e.g., "left-to-right horizontal flow with 3 stages"]
Visual weight: [e.g., "moderate detail, clear labels, professional academic look"]

Confirm this style, or tell me your preference.
```

### 3.2 ref-style Mode: Extracting Style from Reference Image

When the user provides a reference figure, analyze it and extract ONLY style information:

**Extract (style):**
- Dominant colors and their roles (what do different colors represent?)
- Background color (white, dark, gradient, textured?)
- Overall layout pattern (horizontal flow / vertical stack / radial / grid / organic)
- Visual language: flat vs. 3D, line weight, corner radius (sharp vs. rounded), shadow depth
- Label style: font size impression, box vs. inline labels, arrows (thin/thick, solid/dashed)
- Detail density: sparse and clean vs. information-dense
- Overall atmosphere: academic formal / tech sleek / biomedical precise / editorial colorful

**Do NOT extract (content):**
- Specific icons, pictograms, or illustrative elements
- Any text or labels from the original figure
- Exact proportions or sizes of specific elements
- Specific arrow routes or connection topology

**Output a style summary:**
```
Style extracted from reference:
- Palette: [colors]
- Background: [description]
- Layout: [pattern]
- Visual language: [flat/3D, line weight, corners, shadows]
- Label style: [description]
- Density: [sparse/moderate/dense]
- Atmosphere: [description]
```

Then confirm: "I'll apply this visual style to your new figure content. Does this look right?"

**Important rule for bio/BioRender figures**: If the paper domain is biological/medical AND
the reference image is from a non-bio domain (e.g., a tech diagram), reduce the reference image's
influence on structural decisions. BioRender-style biological figures have a strong fixed visual
language — apply the reference only to color palette and density, not to layout or visual form.

---

## Phase 4: Prompt Generation

For each confirmed figure, generate a structured prompt block.

### General Prompt Writing Rules

1. **Write in English** — nanobanana performs best with English prompts
2. **Be specific about subjects** — Name actual molecules, agents, layers, systems from the paper.
   Bad: "show the signaling pathway". Good: "show the TLR4 → MyD88 → NF-κB signaling cascade"
3. **Length**: 100–300 words per prompt. Too short = vague output. Too long = confused output.
4. **Structure the prompt**: scene description → style → key elements → layout → labels
5. **Include negative guidance when helpful**: "no photorealistic rendering", "no decorative borders"
6. **End with style keywords** clustered together for stronger style adherence

### Caption Writing Rules

Every figure block must end with two captions (EN + ZH) ready to paste directly into the paper.

**Caption structure**:
- **Sentence 1**: Describe what the figure shows (the subject). Start with "Fig. N." or "图N."
- **Sentence 2**: Explain how to read the figure OR what the key takeaway is.
- **Sentence 3** (optional): Define abbreviations, or note what the color coding means.

**Caption quality checklist**:
- [ ] Describes content precisely (not "our framework" but "the four-stage planning pipeline of LAMoR")
- [ ] Conveys one key insight, not just a label
- [ ] Defines all abbreviations used in the figure on first mention
- [ ] Does NOT begin with "This figure shows..." — start directly with the subject
- [ ] EN caption: formal academic English, past tense for results, present tense for illustrations
- [ ] ZH caption: matches EN exactly in content, natural academic Chinese (not translated word-for-word)

**Caption anti-patterns**:
- "Figure 1. Our proposed method." → Too vague, no information
- "Figure 1. This figure illustrates the overview of the system." → Remove "This figure illustrates"
- Abbreviations left undefined in caption when they appear in the figure

---

## Domain Style Guides

### Style A: BioRender Style (Biology / Medicine / Biochemistry)

**When to use**: Papers on cell biology, molecular biology, pharmacology, immunology, neuroscience,
biochemical pathways, clinical mechanisms.

**Core style characteristics**:
- White or very light gray background
- 3D-like biological forms: cells have rounded organic shapes with subtle gradients
- Molecules shown as schematic shapes (receptor as Y-shape, proteins as blobs or ribbons)
- Vivid, saturated colors with clear semantic assignment (e.g., red = pathogen, blue = receptor)
- Arrows showing process direction: thick, clean, often with rounded heads
- Text labels in clean sans-serif, positioned clearly with leader lines
- Multiple layers of context shown simultaneously (extracellular → membrane → intracellular)

**Prompt template**:
```
Scientific medical illustration in BioRender style depicting [specific mechanism/process].
White background. [Scene description with named biological actors].
[Actor A] shown as [visual form] in [color], [Actor B] shown as [visual form] in [color].
The process flows [direction]: [step 1] → [step 2] → [step 3].
Include labeled arrows indicating [process names]. Text labels in clean sans-serif font.
Style: professional biomedical illustration, 3D organic forms, precise anatomical schematic,
vivid saturated colors, clean white background, publication quality, BioRender aesthetic.
No photorealistic rendering. No decorative background.
```

**Color conventions**:
- Activation / upregulation: warm red, coral, orange
- Inhibition / blocking: cool blue, purple, dark gray
- Neutral / baseline: medium gray, light blue
- Drug / therapeutic agent: gold, bright yellow-green
- Cell membrane: phospholipid bilayer in warm beige/tan
- Nucleus: dark blue or purple interior

**Common figure subtypes**:
- *Signaling cascade*: vertical or horizontal chain of molecules with phosphorylation arrows
- *Drug mechanism of action*: drug (small molecule) binding to receptor, downstream effects
- *Cell interaction*: two cell types side by side, showing surface receptor interactions
- *Disease vs. healthy comparison*: split panel, left normal, right pathological
- *Experimental workflow*: lab steps shown as schematic icons

---

### Style B: Technical Architecture (CS / Systems Engineering)

**When to use**: Papers on distributed systems, databases, networking, software architecture,
data pipelines, hardware design, protocol design.

**Core style characteristics**:
- White background or very light gray
- Rectangular boxes with sharp or slightly rounded corners
- Clean directional arrows (horizontal or vertical, minimal diagonal)
- 2–4 color palette: one accent color, neutral grays, white
- Subsystems grouped in dashed or solid outlined regions
- Labels inside boxes (component name) and on arrows (data type / operation)
- No decorative elements; purely functional clarity

**Prompt template**:
```
Technical system architecture diagram showing [system name / paper topic].
Clean white background, flat design, professional engineering diagram style.
Main components: [list all modules/services].
[Module A] connects to [Module B] via [connection type, e.g., REST API, message queue].
Layout: [horizontal pipeline / layered vertical / hub-and-spoke].
Color scheme: [primary accent color] for [role], neutral gray for [role], white boxes with
[color] borders for [role].
All components labeled in bold sans-serif. Arrow labels in smaller regular weight.
Style: flat vector technical diagram, clean, minimal, publication-ready, IEEE conference style.
No 3D effects. No gradients. No icons or illustrations.
```

**Layout patterns**:
- *Left-to-right pipeline*: input → processing → output horizontal flow
- *Layered architecture*: top-down layers (presentation → logic → data)
- *Hub-and-spoke*: central system connected to multiple external components
- *Client-server*: two vertical columns with bidirectional arrows

---

### Style C: AI / Agent / NLP Systems

**When to use**: Papers on LLM agents, multi-agent systems, RAG pipelines, chain-of-thought
reasoning, tool-use agents, reinforcement learning from human feedback, prompt engineering.

**Core style characteristics**:
- Light background (white or very light blue-gray)
- Rounded rectangle modules with soft drop shadows or gradient fills
- Nodes connected by directed edges (often curved or orthogonal)
- Accent colors for agent roles: each agent type has a distinct color
- Icons or emoji-like symbols inside agent boxes (optional but common in AI papers)
- Dashed arrows for optional or alternative paths; solid for main flow
- Annotation bubbles for message/prompt text examples

**Prompt template**:
```
AI system diagram illustrating [paper's system name / concept].
Light [color] background. Modern flat design with subtle depth.
System components: [list agents/modules with their roles].
[Agent A] (colored [color]) sends [message type] to [Agent B] (colored [color]).
Main flow: [describe the sequence of interactions].
Include a [color]-bordered text bubble showing an example [prompt/message/output] at [location].
Layout: [horizontal pipeline / vertical stack / circular loop / graph].
Color scheme: [assign colors to agent types].
Style: modern AI research paper diagram, rounded modules, clean edges, soft shadows,
gradient fills, professional illustration, NeurIPS/ACL paper style.
```

**Common figure subtypes**:
- *Multi-agent pipeline*: sequential agents each performing a role
- *ReAct / tool-use loop*: agent → think → act → observe → repeat cycle
- *RAG architecture*: user query → retriever → context → LLM → response
- *Training pipeline*: data → model → reward model → RLHF loop
- *Attention visualization*: heatmap of attention scores over input tokens (use matplotlib instead)

---

### Style D: Computer Vision Networks

**When to use**: Papers on image recognition, object detection, semantic segmentation,
generative models (diffusion, GAN), image editing, multimodal vision-language models.

**Core style characteristics**:
- Dark or white background (dark more common in deep learning papers)
- 3D-perspective rectangular blocks representing layers/modules
- Consistent color coding: one color per module type (encoder=blue, decoder=orange, etc.)
- Input/output shown as images or feature map grids on the sides
- Skip connections shown as curved arrows looping over main path
- Text labels above or below blocks; small labels for dimensions (e.g., "512×512×3")

**Prompt template**:
```
Computer vision neural network architecture diagram for [paper's model name].
[White/dark navy] background. 3D perspective block diagram style.
Input: [describe input, e.g., "RGB image 512×512×3"] on the left.
Network stages: [list stages with block colors, e.g., "ResNet-50 backbone in deep blue,
FPN neck in teal, detection head in coral"].
[Include skip connections / attention gates / feature pyramids as applicable].
Output: [describe output, e.g., "bounding boxes and class labels"] on the right.
Style: academic deep learning architecture diagram, 3D isometric blocks, consistent color coding,
clean dimension annotations, CVPR/ICCV paper style illustration.
```

---

### Style E: General Scientific Illustration

**When to use**: Papers with experimental setup figures, overview/summary figures,
comparison tables as diagrams, or figures that don't fit the above domains.

**Core style characteristics**:
- White background
- Clean sans-serif fonts (Nature, Science standard)
- Muted, professional color palette (2–4 colors max)
- Simple shapes (circles, rectangles, arrows)
- Clear visual hierarchy: main flow prominent, details secondary

**Prompt template**:
```
Scientific overview figure illustrating [topic].
Clean white background, professional academic illustration style.
[Describe the content and layout].
Color palette: [2–4 specific colors with roles].
Style: Nature/Science journal figure style, clean, minimal, precise, publication-ready.
```

---

## ref-style Prompt Injection

When a style has been extracted from a reference image (Phase 3.2), append this block
to the standard domain-style prompt:

```
Styled after a reference figure with the following visual characteristics:
- Color palette: [extracted palette]
- Background: [extracted background]
- Layout pattern: [extracted layout]
- Visual language: [extracted visual language details]
- Label density: [extracted density]
Do not reproduce any specific icons, text, or content from the reference.
Adapt only the visual style — color assignments, spacing, corner style, shadow depth,
and overall compositional energy — to the new content described above.
```

---

## Figure Suggestion Logic

When analyzing a paper, use this logic to determine which figures to recommend:

| Paper has... | Action |
|-------------|--------|
| An overview/framework figure (any quality) | Always include — mark EXISTING, assess quality, provide improved prompt |
| No overview figure at all | Mark NEW, highest priority, generate first |
| A novel mechanism (bio) | Mechanism diagram (BioRender style) — NEW |
| A new system/framework | System architecture diagram — check if existing overview covers it |
| Multiple agents or modules | Agent pipeline or component diagram — NEW if not in overview |
| A new ML model | Network architecture diagram — NEW |
| Comparison to baselines | Side-by-side comparison figure (possibly matplotlib) — NEW |
| A multi-step workflow | Flowchart or process diagram — NEW |
| Experimental setup complexity | Experimental setup schematic — NEW |
| Clinical or patient data | Patient journey / clinical workflow illustration — NEW |

**Priority rule**: The overview/framework figure is ALWAYS listed first, regardless of whether
it exists. If the paper already has one, mark it `EXISTING — redraw/improve` (unless it is
demonstrably publication-quality) and generate an improved prompt. Do not omit it.

---

## Anti-Patterns

Avoid these prompt failure modes:

| Anti-pattern | Why it fails | Fix |
|-------------|-------------|-----|
| "Show a signaling pathway" | Too vague — nanobanana produces generic output | Name specific molecules: "TLR4 → MyD88 → IRAK4 → NF-κB pathway" |
| "Draw an architecture diagram" | No content — could be anything | Name every component: "Redis cache, FastAPI server, PostgreSQL database" |
| "Make it look like the reference image" | Copies content, not style | Extract style features only, describe new content separately |
| Prompt over 400 words | Model attention diluted | Keep to 100–300 words; prioritize content and style keywords |
| No style keywords at end | Style inconsistency | Always end with clustered style keywords |
| Recommending nanobanana for bar charts | Wrong tool | Use matplotlib for quantitative data; nanobanana for illustrations |
| Generic color mentions ("blue and red") | Ambiguous rendering | Specify hex codes or descriptive names ("deep navy", "warm coral") |

---

## Example Outputs

### Example 1: Bio mechanism (analyze mode)

**Input**: Paper on NLRP3 inflammasome activation in macrophages under lipopolysaccharide stimulation.

```
## Figure 1: NLRP3 Inflammasome Activation Mechanism
**Status**: NEW — not in paper
**Purpose**: Illustrate how LPS triggers NLRP3 assembly and IL-1β release
**Recommended tool**: nanobanana
**Figure type**: Mechanism diagram
**Style**: BioRender

**Prompt**:
Scientific medical illustration in BioRender style depicting NLRP3 inflammasome activation
in a macrophage. White background.

Left side: extracellular space showing LPS (lipopolysaccharide, depicted as dark red branched
structures) binding to TLR4 receptor (Y-shaped protein in warm orange) on the macrophage surface.

Center: macrophage interior showing the signal cascade — TLR4 activates MyD88 (small adaptor protein
in yellow), leading to NF-κB (transcription factor shown as dark blue pentagon) translocating to the
nucleus (large dark blue oval). NF-κB upregulates NLRP3 expression (labeled "Signal 1: Priming").

Right side: showing NLRP3 inflammasome complex (large multi-subunit structure in teal, with ASC
adaptor in orange and pro-Caspase-1 in purple). Activated Caspase-1 cleaves pro-IL-1β to mature
IL-1β (shown as small coral-colored diamonds being released through the membrane, labeled "Signal 2:
Activation"). Pyroptotic membrane pores shown as open channels.

Flow direction: left to right with numbered step labels (①②③). All proteins labeled with clean
sans-serif text. Directional arrows in dark gray with rounded heads.

Style: BioRender aesthetic, professional biomedical illustration, 3D organic cell forms, vivid
saturated colors, white background, precise molecular schematic, publication quality.
No photorealistic rendering.

**Caption (EN)**: Fig. 1. Schematic of NLRP3 inflammasome activation in macrophages upon
lipopolysaccharide (LPS) stimulation. LPS binding to TLR4 initiates a two-signal cascade:
Signal 1 (Priming) activates NF-κB to upregulate NLRP3 expression, and Signal 2 (Activation)
triggers NLRP3 oligomerization, Caspase-1 cleavage, and pyroptotic IL-1β release.
Abbreviations: LPS, lipopolysaccharide; TLR4, Toll-like receptor 4; NF-κB, nuclear factor
kappa B; ASC, apoptosis-associated speck-like protein containing a CARD.

**Caption (ZH)**: 图1. 脂多糖（LPS）刺激下巨噬细胞中 NLRP3 炎症小体激活机制示意图。LPS 与
TLR4 结合后触发双信号级联：信号1（启动）通过激活 NF-κB 上调 NLRP3 表达；信号2（激活）
驱动 NLRP3 寡聚化、Caspase-1 剪切及焦亡性 IL-1β 释放。

**nanobanana tips**: If NLRP3 complex is unclear, try regenerating with emphasis on "multi-protein
oligomeric ring structure". Aspect ratio: 16:9 landscape for paper figure.
```

---

### Example 2: AI agent pipeline (generate mode)

**Input**: "generate: a multi-agent debate system where three LLM agents argue and a judge agent decides"

```
## Figure 1: Multi-Agent Debate System
**Status**: NEW — not in paper
**Purpose**: Show the debate-and-judge architecture
**Recommended tool**: nanobanana
**Figure type**: Agent pipeline
**Style**: AI/Agent

**Prompt**:
Modern AI system diagram illustrating a multi-agent debate architecture.
Light blue-gray background (#F0F4F8). Clean flat design with soft drop shadows.

Three "Debater Agent" modules arranged horizontally at the top, each as a rounded rectangle:
Debater A in deep blue (#2C4E80), Debater B in teal (#3A8A7E), Debater C in purple (#6B4C9A).
Each contains a small speech-bubble icon. Below each debater, a dashed-border text box shows
a sample argument excerpt in small gray italic text.

All three debaters send solid arrows downward to a central "Judge Agent" module (large rounded
rectangle in warm gold #D48B2A, positioned center-bottom). The judge module contains a gavel icon.
The judge outputs a single solid arrow to the right pointing to a "Final Decision" box in coral
(#E05A3A) with a checkmark icon.

An optional dashed feedback arrow loops from the Judge back up to the Debaters (labeled "next round").

Style: modern AI research diagram, NeurIPS paper style, rounded modules, gradient fills,
soft shadows, clean directed edges, professional illustration, no decorative elements.

**Caption (EN)**: Fig. 1. Architecture of the multi-agent debate system. Three Debater Agents
independently generate arguments, which are aggregated by a central Judge Agent to produce
a final decision. Dashed arrows indicate optional iterative debate rounds.

**Caption (ZH)**: 图1. 多智能体辩论系统架构示意图。三个辩手智能体分别独立生成论点，由中央裁判
智能体汇总后做出最终决策。虚线箭头表示可选的迭代辩论轮次。

**nanobanana tips**: Aspect ratio 16:9. If the judge module looks too small, regenerate with
"central judge module larger and more prominent than debater modules".
```

---

### Example 3: ref-style mode

**Input**: Reference image (a clean tech diagram with dark navy background, orange accents,
horizontal left-to-right flow) + "Draw a RAG pipeline for my NLP paper"

```
## Figure 1: RAG Pipeline Architecture
**Status**: NEW — not in paper
**Purpose**: Show retrieval-augmented generation process
**Recommended tool**: nanobanana
**Figure type**: AI system diagram
**Style**: AI/Agent (adapted from reference)

**Style reference**:
Dark navy background (#1A2744), warm orange (#E87D2B) accent for key components,
horizontal left-to-right single-row layout, flat rectangular modules with sharp corners,
high contrast white text labels, sparse labeling (titles only, no sub-labels),
clean directional arrows in orange, overall atmosphere: sleek tech dashboard style.

**Prompt**:
AI system architecture diagram of a Retrieval-Augmented Generation (RAG) pipeline.
Dark navy background (#1A2744). Flat design, sharp-cornered rectangular modules, high contrast.

Left to right horizontal flow:
1. "User Query" box (orange #E87D2B, white text) → arrow →
2. "Query Encoder" module (dark gray #2E3F5C, white text) → arrow →
3. "Vector Database" module (dark gray, database cylinder icon in orange) → arrow →
4. "Top-K Retriever" module (dark gray) → arrow →
5. "Context + Query" merger box (orange border, white background, white text) → arrow →
6. "LLM Generator" module (dark gray, lightning bolt icon in orange) → arrow →
7. "Response" output box (orange, white text)

All arrows in warm orange (#E87D2B), thin, rightward-pointing.
White label text, bold module titles only (no sub-labels).

Styled after reference: dark navy background, orange accent system, horizontal pipeline,
sharp-corner flat modules, sparse white labels, sleek tech aesthetic.
Do not reproduce specific icons or layout proportions from the reference — apply style only.

Style: modern AI pipeline diagram, sleek tech illustration, high contrast dark theme,
flat vector design, professional publication quality.

**Caption (EN)**: Fig. 1. Retrieval-Augmented Generation (RAG) pipeline architecture.
An input query is encoded and used to retrieve the top-K relevant documents from a vector
database; the retrieved context is concatenated with the original query and passed to the
LLM generator to produce the final response.
Abbreviations: RAG, Retrieval-Augmented Generation; LLM, Large Language Model.

**Caption (ZH)**: 图1. 检索增强生成（RAG）管线架构示意图。输入查询经编码后从向量数据库中检索
Top-K 相关文档，检索到的上下文与原始查询拼接后输入大语言模型（LLM）生成器，最终输出响应结果。

**nanobanana tips**: Aspect ratio 16:9 or 2:1 wide. If modules appear too small for labels,
regenerate with fewer stages grouped into larger blocks.
```


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)