mcpbeat Sign in

Scientific Schematics Agent Skill

Designing scientific schematics, diagrams, and graphical abstracts. Covers tool selection (BioRender, Inkscape, Affinity, PowerPoint), design principles for pathway diagrams, mechanism schematics, experimental workflows, and journal graphical abstracts. Includes composition, icon sourcing, color for biological entities, and accessibility. Use when creating illustrative (not data-driven) scientific figures.

4k tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
294
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/jaechang-hits/SciAgent-Skills --skill scientific-schematics

The instruction itself

14 sections, as written by the author

Scientific Schematics

Overview

Scientific schematics are illustrative figures that communicate biological mechanisms, experimental designs, or conceptual frameworks — as distinct from data-driven figures (graphs, heatmaps). A well-designed schematic makes a manuscript's key concept immediately comprehensible to a broad scientific audience, while a poorly designed one confuses reviewers and reduces the paper's impact. This guide covers the design decisions, tool selection, composition principles, and accessibility standards specific to biological schematics in peer-reviewed publications.

Key Concepts

1. Schematic Types and Their Purpose

Not all schematics serve the same function. Choosing the wrong type leads to overloaded or underspecified figures.

| Type | Purpose | Key Elements | Examples |

|------|---------|-------------|---------|

| Mechanism diagram | Show step-by-step molecular events | Proteins, DNA, membranes, arrows indicating causality | CRISPR cleavage, signaling cascade, transcription factor binding |

| Pathway diagram | Show relationships in a network | Nodes (proteins/metabolites), edges (activation/inhibition), direction | MAPK signaling, metabolic flux, gene regulatory network |

| Experimental workflow | Show experimental protocol as a figure | Numbered steps, icons for equipment/samples, time arrows | Single-cell sequencing pipeline, drug treatment protocol |

| Graphical abstract | 1-panel summary of entire paper | 2–4 key findings, minimal text, journal-specified dimensions | Cell, Nature, PNAS graphical abstracts |

| Structural diagram | Show molecular structure/conformation | Ribbon structure, surface representation, active site | Protein domain schematic, ligand binding pocket |

Decision rule: If the reader needs to understand *what happened* step-by-step, use a workflow. If they need to understand *why* (cause and effect), use a mechanism/pathway diagram. If they need a 30-second paper summary, use a graphical abstract.

2. Tool Comparison

| Tool | Best For | Learning Curve | Cost | File Output |

|------|---------|---------------|------|-------------|

| BioRender | Quick biological schematics; built-in icon library | Low | Subscription (~$99/month academic; free for draft) | PNG, SVG, PDF (license required for publication) |

| Inkscape | Full vector editing; open-source | Medium–High | Free | SVG, PDF, PNG, EMF |

| Affinity Designer | Professional vector + raster hybrid | Medium | ~$55 one-time | SVG, PDF, AFDESIGN |

| Adobe Illustrator | Industry standard; full features | High | ~$55/month | SVG, PDF, AI, EPS |

| PowerPoint / Keynote | Quick drafts; non-scientists | Low | Included in MS/Apple | PNG (low resolution), PDF |

| draw.io / Lucidchart | Flowcharts, pathway diagrams | Low | Free/subscription | SVG, PNG, XML |

| ChimeraX / PyMOL | Molecular structure renders | Medium | Free (academic) | PNG, TIFF, movie |

Key difference: BioRender provides curated biological icons (cells, proteins, instruments) that are publication-quality and royalty-free under the publication license. For complex custom graphics, Inkscape (free) or Affinity Designer (paid) offer more flexibility.

3. Color Usage in Biological Schematics

Color in biological schematics carries semantic meaning and must be used consistently.

Conventional biological color assignments:

  • DNA: double helix colored in blue/navy or gray
  • mRNA: orange or yellow
  • Protein: varying; use consistent color per protein family across all figures in a paper
  • Cell nucleus: light gray or blue fill
  • Cell membrane: tan/beige bilayer
  • Mitochondria: orange
  • Lysosomes: red/purple

Signal direction conventions:

  • Arrows: activation (→ solid arrowhead), inhibition (⊣ flat bar), indirect (- - →)
  • Color coding arrows: green = activating, red = inhibiting, gray = neutral/context

Accessibility:

  • Never use red–green encoding alone; add shape cues (✓/✗, solid/dashed)
  • Test with CVD simulator before submission
  • Use at least 3:1 contrast ratio for text on colored backgrounds

4. Composition and Layout Principles

Visual hierarchy: The most important element should be the largest and most central. Support elements (labels, arrows, scale bars) should be visually subordinate.

Element spacing: Maintain consistent padding between grouped elements. Crowded diagrams cause readers to misread association between elements.

Arrow semantics: Every arrow must convey exactly one relationship. Do not use arrows interchangeably for "leads to," "causes," "physically binds," and "is required for" — use distinct arrow styles for each.

Text minimalism: Labels should be noun phrases only (not full sentences). Move explanatory text to the figure caption, not into the diagram itself.

Decision Framework

What is this schematic trying to communicate?
│
├── A sequence of experimental steps
│   └── → Workflow diagram
│       ├── Numbered panels or numbered arrows
│       ├── Icons for equipment (instrument, pipette, plate, animal)
│       └── Time axis or step axis
│
├── How a molecule works mechanistically
│   └── → Mechanism diagram
│       ├── Protein shapes (surface or cartoon)
│       ├── Conformational change arrows
│       └── Before/after state panels
│
├── How multiple components interact in a network
│   └── → Pathway diagram
│       ├── Nodes = proteins/metabolites (circles, rectangles)
│       ├── Edges = arrows (activation = →, inhibition = ⊣)
│       └── Compartment boxes (nucleus, cytoplasm, extracellular)
│
├── A single-panel paper summary
│   └── → Graphical abstract
│       ├── Check journal specifications (size, text policy)
│       ├── Show: question → approach → key finding → implication
│       └── Minimal text; max 3–4 panels
│
└── A 3D molecular structure
    └── → Structural diagram
        ├── Use ChimeraX, PyMOL, or RCSB PDB viewer for render
        ├── Annotate active site/binding pocket
        └── Add scale bar (Å or nm)

| Scenario | Tool | Format | Key Consideration |

|---------|------|--------|-------------------|

| First-author manuscript, fast turnaround | BioRender | PDF/SVG | Requires publication license for final submission |

| Lab with ongoing schematic needs | Inkscape + master template | SVG | Reusable elements; free; no vendor lock-in |

| Graphical abstract for Cell/Nature | BioRender or Illustrator | PNG at journal spec | Check exact pixel dimensions and text policy |

| Molecular mechanism with protein structure | ChimeraX + Inkscape | PNG render + SVG annotation | Use PDB structure; annotate key residues |

| Pathway diagram with many nodes | draw.io / Cytoscape | SVG/PDF | Auto-layout for networks with >20 nodes |

Best Practices

  • Start with a sketch before opening any tool: Draw the schematic on paper first. Determine what elements are needed, their hierarchy, and the spatial relationships. Opening software first leads to layout decisions driven by tool constraints, not by communication goals.
  • Define a consistent visual vocabulary before drawing the first panel: Assign colors, shapes, and arrow styles to each biological entity type at the project level. Document these assignments in a legend or lab style guide. Inconsistency across figures in a paper signals carelessness and confuses reviewers.
  • Use the journal's graphical abstract template: Every high-impact journal (Cell, Nature, PNAS, PLOS) publishes exact dimensions, resolution requirements, and font rules for graphical abstracts. Download the template before starting — resizing after the fact destroys aspect ratios and makes text too small.
  • Export at publication resolution from the vector source: Always export final figures from the original vector file (SVG, AI, AFDESIGN) at the target DPI, never by screenshot or screen capture. Screenshots are raster at screen resolution (~72 dpi); journals require 300–600 dpi.
  • Label arrows and connections in captions, not in the diagram: Arrow labels ("activates," "phosphorylates," "recruits") add clutter and reduce diagram readability. Move these relationships to the figure caption using panel reference labels (A, B, C). The diagram should be self-explanatory to someone who reads the caption.
  • Group related elements visually using proximity, enclosure, and color: Elements that belong together conceptually should be spatially close, share a background color, or be enclosed in a bounding box. Do not use arbitrary spatial arrangements — viewers interpret proximity as association.
  • Version-control your source files: Store original editable source files (.svg, .afdesign, .ai, .brd) in version-controlled storage alongside the manuscript. Journals frequently request revised figures during revision, and re-creating from a PNG is extremely time-consuming.

Common Pitfalls

  • Using inconsistent arrow styles across a figure
  • *What goes wrong*: Solid arrows and dashed arrows mixed arbitrarily make readers unsure whether dashed means "indirect," "hypothetical," or merely a stylistic choice.
  • *How to avoid*: Define an arrow legend: solid arrow = direct activation, dashed = indirect, flat bar = inhibition. Use this consistently in every panel of every figure in the paper.
  • Overloading a single panel with too many elements
  • *What goes wrong*: Pathway diagrams with 20+ nodes and 30+ arrows cannot be read in a journal figure at 170 mm width. Reviewers ask for simplification; revisions are time-consuming.
  • *How to avoid*: Limit mechanism panels to ≤8 elements. Move complex pathway context to supplementary figures. Focus the main-text schematic on the core novel finding.
  • Using BioRender without purchasing the publication license
  • *What goes wrong*: BioRender figures created under the free or draft license cannot be published. Submitting without proper licensing violates BioRender's terms of service and risks manuscript rejection.
  • *How to avoid*: Purchase the publication license before creating the final figure version. BioRender generates a citation string that must be included in the figure legend.
  • Text inside the schematic at 6 pt or smaller at print size
  • *What goes wrong*: Labels inside pathway nodes or protein icons become illegible at publication dimensions (85 mm single-column). Reviewers flag this; revision requires recreating the entire figure.
  • *How to avoid*: Work at print size from the start. In Inkscape: set canvas to 85 mm × target height. Minimum label size: 7 pt at 100% print scale.
  • Red–green arrow encoding for activation–inhibition without shape cues
  • *What goes wrong*: ~8% of male readers have red–green color vision deficiency and cannot distinguish activation (green) from inhibition (red) arrows.
  • *How to avoid*: Use distinct arrow shapes: → for activation, ⊣ for inhibition. Color is redundant encoding, not the only cue.
  • Copying schematic elements from published papers without redrawing
  • *What goes wrong*: Reproducing figures from published papers without permission violates copyright. This applies to diagrams and icons, not just photographs.
  • *How to avoid*: Use BioRender's licensed icon library, Reactome's freely licensed pathway diagrams (CC-BY), or Bioicons (free, open icons). Always redraw; never screenshot.
  • Missing scale bars in structural diagrams
  • *What goes wrong*: Protein structure renderings without scale bars prevent readers from assessing relative sizes of domains, ligands, or interfaces.
  • *How to avoid*: Add a scale bar (e.g., "10 Å" or "2 nm") using ChimeraX's scalebar command or annotate in Inkscape after export.

Workflow

  • Define the message — write one sentence stating what the schematic must communicate
  • Sketch on paper — rough layout, element list, arrow types
  • Choose tool — BioRender for icon-heavy biology; Inkscape for custom vectors; ChimeraX for structures
  • Set canvas to print dimensions — match journal column width before placing any element
  • Build in layers — background → structural elements (membranes, organelles) → protein/molecule icons → arrows → labels
  • Apply visual vocabulary — consistent colors, arrow styles, fonts per lab style guide
  • Run accessibility check — CVD simulation; test grayscale version
  • Export from vector source — PDF or TIFF at target DPI (≥300 dpi raster, vector for line art)
  • Archive source file — commit .svg/.afdesign/.brd to version control alongside manuscript

Protocol Guidelines

  • BioRender publication workflow: Create figure → File → Publish Figure → Generate Attribution → copy citation string into figure legend. The attribution reads: "Created with BioRender.com" with a unique agreement ID. Without this, the figure cannot be legally published.
  • Inkscape CMYK-safe workflow: Inkscape does not natively support CMYK. For CMYK journals: design in RGB → export to PDF → convert using Ghostscript (gs -sDEVICE=pdfwrite -dUseCIEColor). Verify colors after conversion.
  • ChimeraX protein structure render: open 6YYTgraphics silhouettes truelighting softsaveimage figure.png width 2400 height 2400 → annotate in Inkscape.
  • Multi-panel figure assembly in Inkscape: Use Inkscape extensions → Grids → set column guides at journal column widths. Import each panel as a linked SVG to enable per-panel updates without recreating the composite.

Further Reading

  • scientific-visualization — data-driven figures (graphs, heatmaps) as distinct from illustrative schematics
  • scientific-manuscript-writing — figure legend writing and integration of schematics into papers
  • latex-research-posters — assembling schematics into poster layouts

Other skills for the same job

different authors, same section of the catalogue
Mobile Design
by ComeOnOliver
×2

Mobile-first design and engineering doctrine for iOS and Android apps. Covers touch interaction, performance, platform conventions, offline behavior, and mobile-specific decision-making. Teaches principles and constraints, not fixed layouts. Use for React Native, Flutter, or native mobile apps.

72k tokens scripts
Experimental Design
by K-Dense-AI
×1

Design experiments and studies BEFORE data is collected — choosing a design, randomizing, blocking, and laying out treatment combinations so results are interpretable. Use whenever someone is planning a study, asks how to assign subjects/samples to groups, mentions randomization, blocking, stratification, controls, factorial or fractional-factorial designs, design of experiments (DOE), screening many factors, response-surface optimization, crossover or repeated-measures or split-plot designs, cluster/group randomization, Latin squares, plate layouts, batch/run-order effects, replication vs. pseudoreplication, or sequential/adaptive/group-sequential designs. Trigger even for informal phrasings like "how should I set up this experiment", "how do I avoid confounding", "what's the best way to test these 6 factors", or "assign these mice to conditions". For computing the sample size or power once the design is chosen, use statistical-power; for analyzing data already collected, use statistical-analysis.

14k tokens scripts
Architect
by ComeOnOliver
×1

Design systems, plan implementations, review architecture decisions - Use when you need to plan a complex feature, design system architecture, or make high-level technical decisions.

2k tokens
Analyze Feature Requests
by phuryn

Analyze and prioritize a list of feature requests by theme, strategic alignment, impact, effort, and risk. Use when reviewing customer feature requests, triaging a backlog, or making prioritization decisions.

568 tokens
Gke Networking
by google
vendor

>- Plans, configures, and manages core GKE cluster networking. Covers private clusters, VPC-native configurations, DNS, node egress, Dataplane V2, and IP planning. Use when designing GKE networking layouts, configuring private clusters, setting up Dataplane V2, planning GKE IP ranges, or managing VPC- native cluster modes. Don't use for application ingress, load balancing, or service networking (use gke-service-networking instead).

1k tokens
Azldev Add Component
by microsoft
vendor

Read this before adding or importing a component; follow the workflow instead of guessing. Explains how to add a new component to an azldev distro, covering inspecting the upstream spec, the inline-versus-dedicated-file decision, and validating with render, diff-sources, and build. Triggers include add component, new package, import package, create comp.toml, new component.

998 tokens
Open Knowledge Pack Plain Notes
by inkeep

How to work in a Plain Notes project (the `plain-notes` starter pack): a flat notes/ folder plus a daily/ journal. The 'I just want to write' layout. Read when the project has these folders, OR when asked to jot a note, capture a quick thought, or write today's journal entry. Carries the linking habit and daily-entry behavior so templates and folder descriptions stay minimal. Complements the platform `open-knowledge` skill; does not replace it.

498 tokens
Open Knowledge Pack Worldbuilding
by inkeep

How to work in a Worldbuilding project (the `worldbuilding` starter pack): a fiction encyclopedia of characters, settings, themes, factions, and lore. Read when the project has these folders, OR when asked to add a character, setting, faction, or piece of lore, or to check the world for internal consistency. Carries the auto-stub and consistency behaviors so that guidance does not live inside template bodies or folder descriptions. Complements the platform `open-knowledge` skill; does not replace it.

758 tokens

How to use it

Copy the folder

Take jaechang-hits/scientific-schematics from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.