drawio

Name: drawio
Author: sordi-ai

17stars3forks

How to install drawio?

sordi-ai/skill-everything/drawio

$npx -y skills add sordi-ai/skill-everything --skill drawio

Installs into the current project.

Summary

Apply when creating or reviewing architecture diagrams, Mermaid diagrams, or draw.io files.

Files · 1

View on GitHub

SKILL.md

1	# Sub-Skill: Diagrams (draw.io / Mermaid)
2
3	Purpose: Ensure diagrams are version-controlled as source, rendered consistently, and kept in sync with the system they describe.
4
5	---
6
7	## Rules
8
9	### Source Control
10
11	1. Commit source, not just exports. Always commit diagram source files (`.drawio`, `.mmd`, `.puml`) alongside or instead of rendered image exports. Reference: ERR-2026-027
12	2. No binary-only diagrams. Never commit only a PNG or SVG export without the editable source; reviewers cannot diff or modify a raster image.
13	3. One source file per diagram. Use a single canonical source file per diagram; avoid duplicating the same diagram in multiple formats.
14
15	### Format Selection
16
17	4. Prefer diagram-as-code. Prefer Mermaid or PlantUML over draw.io XML when the diagram fits a supported diagram type; text diffs are reviewable.
18	5. Match diagram type to content. Use `sequenceDiagram` for request flows, `flowchart` for decision logic, `C4Context`/`C4Container` for architecture, `erDiagram` for data models.
19	6. Set layout direction explicitly. Always declare layout direction (`LR`, `TD`) in Mermaid flowcharts; never rely on the default, which varies by renderer.
20
21	### Rendering Pipeline
22
23	7. Document the render command. Always include the render command or CI step in the repo README or Makefile so any contributor can regenerate exports.
24	8. Regenerate exports in CI. Ensure CI regenerates diagram exports from source and fails if the committed export differs from the generated one.
25	9. Pin renderer version. Always pin the Mermaid CLI or draw.io CLI version in CI to prevent silent rendering changes across upgrades.
26
27	### Quality & Consistency
28
29	10. Use consistent node naming. Always use the same label for the same system component across all diagrams in the repo; divergent names cause confusion.
30	11. Add alt text to exported images. Always add descriptive alt text to diagram images embedded in documentation for accessibility.
31	12. Review diagrams in PRs. Before merging, verify that any diagram change accurately reflects the system change described in the PR.
32
33	---
34
35	## See also
36
37	- `skills/svg-check/SKILL.md`
38	- `skills/error-log/SKILL.md`

People who liked this also viewed

6 picks

Type

web-design-guidelinesReview UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".SkillsJul 2026483k29k
lark-slides飞书幻灯片：创建和编辑幻灯片。创建演示文稿、读取幻灯片内容、管理幻灯片页面（创建、删除、读取、局部替换）。当用户需要创建或编辑幻灯片、读取或修改单个页面时使用。当用户给出 doubao.com 的 /slides/ URL/token 时，也应直接使用本 skill，不要因为域名不是飞书而回退到 WebFetch；路由依据是 URL 路径模式和 token，而不是域名。不负责：云文档内容编辑（走 SkillsJul 2026332k16k
design-taste-frontendTaste-Skill - gives your AI good taste. stops the AI from generating boring, generic slop SkillsJul 2026280k66k
ui-ux-pro-maxUI/UX design intelligence for web and mobile. Searchable local database with 84 styles, 192 color palettes, 74 font pairings, 192 product types, 98 UX guidelines, 104 icon entries, 16 GSAP motion presSkillsJul 2026280k109k
caveman-helpQuick-reference card for all caveman modes, skills, and commands. One-shot display, not a persistent mode. Trigger: /caveman-help, "caveman help", "what caveman commands", "how do I use caveman".SkillsJul 2026249k92k
codebase-designShared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-nSkillsJul 2026225k182k

drawio

17stars3forks

View on GitHub

How to install drawio?

sordi-ai/skill-everything/drawio

$npx -y skills add sordi-ai/skill-everything --skill drawio

Installs into the current project.

Summary

Apply when creating or reviewing architecture diagrams, Mermaid diagrams, or draw.io files.

Files · 1

View on GitHub

SKILL.md

1	# Sub-Skill: Diagrams (draw.io / Mermaid)
2
3	Purpose: Ensure diagrams are version-controlled as source, rendered consistently, and kept in sync with the system they describe.
4
5	---
6
7	## Rules
8
9	### Source Control
10
11	1. Commit source, not just exports. Always commit diagram source files (`.drawio`, `.mmd`, `.puml`) alongside or instead of rendered image exports. Reference: ERR-2026-027
12	2. No binary-only diagrams. Never commit only a PNG or SVG export without the editable source; reviewers cannot diff or modify a raster image.
13	3. One source file per diagram. Use a single canonical source file per diagram; avoid duplicating the same diagram in multiple formats.
14
15	### Format Selection
16
17	4. Prefer diagram-as-code. Prefer Mermaid or PlantUML over draw.io XML when the diagram fits a supported diagram type; text diffs are reviewable.
18	5. Match diagram type to content. Use `sequenceDiagram` for request flows, `flowchart` for decision logic, `C4Context`/`C4Container` for architecture, `erDiagram` for data models.
19	6. Set layout direction explicitly. Always declare layout direction (`LR`, `TD`) in Mermaid flowcharts; never rely on the default, which varies by renderer.
20
21	### Rendering Pipeline
22
23	7. Document the render command. Always include the render command or CI step in the repo README or Makefile so any contributor can regenerate exports.
24	8. Regenerate exports in CI. Ensure CI regenerates diagram exports from source and fails if the committed export differs from the generated one.
25	9. Pin renderer version. Always pin the Mermaid CLI or draw.io CLI version in CI to prevent silent rendering changes across upgrades.
26
27	### Quality & Consistency
28
29	10. Use consistent node naming. Always use the same label for the same system component across all diagrams in the repo; divergent names cause confusion.
30	11. Add alt text to exported images. Always add descriptive alt text to diagram images embedded in documentation for accessibility.
31	12. Review diagrams in PRs. Before merging, verify that any diagram change accurately reflects the system change described in the PR.
32
33	---
34
35	## See also
36
37	- `skills/svg-check/SKILL.md`
38	- `skills/error-log/SKILL.md`

People who liked this also viewed

6 picks

Type