scientific-illustration

Files (1)

• SKILL.md

SKILL.md (first lines)

# Flyingchip Scientific Illustration

This team skill is a thin orchestration layer around two external projects:

- Scientific Illustrator: reference workflow for editable figures with Designer, Drawer,
  Reviewer, and Corrector quality gates.
- Official draw.io MCP: diagram creation, shape search, XML generation, and draw.io editing.

Do not claim that an application is connected until its status or tool response proves it.
Do not silently replace an unknown draw.io shape with a rectangle. State when an output is a
work copy rather than the currently open document.

## Workflow

1. Clarify the target: `drawio`, PowerPoint, WPS, SVG, PNG, PDF, or a mixed deliverable.
2. Inspect the reference image and make a region inventory:
   - title and labels
   - nodes, containers, and layers
   - arrows and edge semantics
   - tables, legends, axes, and annotations
   - photos, textures, or other irreducible raster content
3. Draft a semantic layout before drawing. Name objects by meaning, not by coordinates.
4. For draw.io work, search for suitable shapes before generating XML. Use the official MCP
   `search_shapes` capability when available, then create the diagram with native editable
   objects.
5. Draw in checkpoints. After each region, verify structure, labels, connector direction,
   spacing, and preview output.
6. Run a reviewer pass:
   - every required label is present and legible
   - arrows have the intended direction and attachment points
   - no objects overlap unexpectedly
   - colors and line weights have consistent meaning
   - the file remains editable
7. Correct issues before final export.
8. Save the editable source first. Then export requested previews, preferably with embedded
   source XML when the export path supports it.

## Embedded-team conventions

For BSP, OS, and system architecture figures:

- distinguish hardware, bootloader, kernel/RTOS, middleware, application, and host tooling
- label interfaces and protocols explicitly
- show trust, power, reset, timing, or data-flow boundaries when they affect the decision
- include version, board, SoC, OS, and assumptions in a note or metadata block
- use the same name for an object in the diagram, requirement, and verification record

For review deliverables, produce:

1. editable source
2. preview image or PDF
3. short object/assumption inventory
4. verification checklist and unresolved items

## Safety and provenance

Never copy upstream plugin source into this package. Use the official upstream installation or
MCP endpoint documented in `docs/dependencies.md`. Keep proprietary reference images and team
documents local unless the user explicitly authorizes sharing.

From caijixuexi/flyingchip_abg_plugins, GPL-3.0.

More from caijixuexi/flyingchip_abg_plugins