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.
npx skills add https://github.com/jaechang-hits/SciAgent-Skills --skill scientific-schematics
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.
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.
| 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.
Color in biological schematics carries semantic meaning and must be used consistently.
Conventional biological color assignments:
Signal direction conventions:
Accessibility:
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.
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 |
.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.scalebar command or annotate in Inkscape after export..svg/.afdesign/.brd to version control alongside manuscriptgs -sDEVICE=pdfwrite -dUseCIEColor). Verify colors after conversion.open 6YYT → graphics silhouettes true → lighting soft → saveimage figure.png width 2400 height 2400 → annotate in Inkscape.scientific-visualization — data-driven figures (graphs, heatmaps) as distinct from illustrative schematicsscientific-manuscript-writing — figure legend writing and integration of schematics into paperslatex-research-posters — assembling schematics into poster layoutsMobile-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.
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.
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.
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.
>- 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).
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.
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.
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.
Take jaechang-hits/scientific-schematics from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
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.