SHALINS428/Codex-drawio-skill / skill/drawio
drawio
VerifiedUse when the user asks to create, edit, rebuild, or refine editable diagrams in `.drawio` / diagrams.net format, especially for academic figures such as system architecture diagrams, technical roadmaps, workflow diagrams, method pipelines, module relationship diagrams, and experiment flowcharts. Use this skill when the user wants publication-ready outputs with both an editable source file and a PNG export, or when an existing figure image needs to be rebuilt into a clean editable academic-style diagram.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 9.8 KB |
| agents/openai.yaml | config | 319 B |
| references/academic-diagram-style.md | markdown | 4.0 KB |
| references/figure-types.md | markdown | 1.7 KB |
| scripts/export-drawio-png.ps1 | script | 3.8 KB |
| scripts/new-drawio-figure.ps1 | script | 3.6 KB |
references/academic-diagram-style.md
View on GitHub# Academic Diagram Style
## Goal
Academic diagrams should support explanation, not compete with it.
The figure must remain legible when:
- viewed at normal zoom
- placed on an A4 page
- inserted into a thesis chapter with a standard caption
## Core Style Rules
- Prefer white or very light backgrounds.
- Use low-saturation accent colors.
- Use consistent line weight and corner radius.
- Keep spacing regular and grid-aligned.
- Reduce decorative effects such as heavy shadows or glossy gradients.
- Use one dominant reading direction for the entire figure where possible.
- Keep semantic color usage sparse and consistent.
## Typography
- Node text should be short.
- Prefer concise noun phrases over sentence-style prose.
- Avoid squeezing long explanations into one box.
- If text becomes small, reduce wording before expanding complexity.
- Prefer a clean sans-serif font family and keep it consistent.
- Use `26px` text throughout the diagram by default unless the user explicitly requests another size.
- Expand boxes and simplify wording instead of shrinking below the `26px` default.
- Make titles and major group labels clearly larger than ordinary node labels.
- Increase box size before shrinking text into an unreadable range.
## Layout
- Keep a clear primary reading direction.
- Separate major layers with whitespace, not visual clutter.
- Avoid excessive crossing connectors.
- Keep module widths and heights visually balanced.
- Keep adjacent nodes typically separated by about 24-40 px at starter-canvas scale.
- Keep major grouped sections typically separated by about 40-80 px.
- Use labeled containers or background bands when grouping related modules.
- Route connectors so they do not pass through text or box interiors unnecessarily.
- Use orthogonal connectors as the default for structured academic diagrams.
- Attach connectors to sensible side anchors instead of treating them as unconstrained point-to-point strokes.
- Adjust elbow points and connector bends manually when auto-routing looks awkward.
- When a connector needs a turn, define explicit bend points or waypoints instead of loose diagonal segments.
- Move nodes to improve line clarity instead of accepting tangled connector paths.
## Shape And Line Defaults
- Keep comparable nodes at comparable sizes unless size encodes meaning deliberately.
- Use consistent border widths for comparable objects.
- Use consistent arrowhead style for the same relationship type.
- Avoid mixing too many shape grammars in one figure; use shape variation only when it conveys structure.
- Keep corner radius consistent across similar boxes.
## Export Defaults
- Export PNG with a white or very light opaque background by default.
- Target publication-ready export size; roughly 2200 px or more on the longer side is a good default.
- Keep a small outer margin around the content.
- Ensure nothing is clipped at the export boundary.
- Prefer a figure that is slightly spacious over one that is densely packed.
## Readability Checklist
- Can the title and all main labels be read at normal page zoom?
- Are secondary labels still readable without zooming in heavily?
- Does each box contain one idea rather than a paragraph?
- Are connector directions obvious without verbal explanation?
- Does the figure still make sense in black-and-white print?
- Do connector bends and intersections remain easy to follow at normal size?
- Are arrowheads and line endpoints unobstructed?
- Is the exported PNG ready to insert into the paper without further cleanup?
- Are spacing, border widths, and arrow styles consistent across comparable elements?
- Is the figure readable without relying on color alone?
- Does the deliverable include the editable `.drawio` source file together with the exported image?
## Visual Differentiation
Different figure types should not look interchangeable.
- Architecture diagrams should emphasize modules and interactions.
- Roadmaps should emphasize stages and progression.
- Process figures should emphasize order and branching.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |