Flowchart

Skill KhaiTrang1995/agentic-awesome-kits/kits/software/drawio-kit/.claude/skills/flowchart

A universal collection of reusable Loop Engineering kits for AI coding agents—not just prompts. Each kit combines Skills, Rules, Templates, workflows, and validation loops to help agents autonomously plan, execute, verify, fix, and improve engineering tasks.

Install

npx -y skills add KhaiTrang1995/agentic-awesome-kits --skill flowchart

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

3 things to look at

22 days oldThe repository was created 22 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
7 stars7 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Generate flowchart .drawio from a process description — start/end, process, decision, standard mxGraph, opens directly in draw.io.

SKILL.md

2.5 KB, as published. Nobody here has run it

/flowchart — Generate Flowchart (draw.io)

When to use

Visualize a business process or control flow (business process, algorithm, approval flow) as a professional diagram editable in draw.io.

Input examples

/flowchart leave request approval: submit request → manager approve → HR approve → confirm
/flowchart container search flow: enter keyword → validate → query DB → results? → display / empty state
/flowchart --direction left-right CI/CD process: push code → build → test → deploy

Workflow

Phase 1 — Analyze steps

Identify steps by type:

Start/End: start/end points (ellipse)
Process: action (rounded rectangle)
Decision: Yes/No or multi-branch (rhombus)
Input/Output: data in/out (parallelogram, if any)

Phase 2 — Layout (L3 preview)

Print node list + planned positions as a table before generating XML:

# | Type | Content | Position (x,y)
1 | Start | Start | (360, 40)
2 | Process | Enter keyword | (360, 140)
3 | Decision | Keyword valid? | (360, 260)
...

User reviews layout → Phase 3.

Phase 3 — Generate XML

Use _templates/flowchart.drawio as the frame, apply:

Core shapes + colors per drawio-conventions.md sections 2–3
Grid 20px, standard spacing section 4
Orthogonal edges with explicit exitX/exitY/entryX/entryY, Yes/No labels on decision branches

Phase 4 — Approval L1 → Write

Mandatory rules

Always exactly 1 Start and at least 1 End (multiple Ends allowed for different outcomes).
Every Decision MUST label all outgoing branches (Yes/No, or specific case names).
NO more than 15 nodes in one diagram — if the process is longer, split into child flowcharts + references (docs/diagrams/{feature}/flowchart-{sub-slug}.drawio).
Consistent flow direction (--direction default top-down).

Output

docs/diagrams/{feature}/flowchart-{slug}.drawio

References

@.claude/rules/drawio-conventions.md
@.claude/rules/naming-conventions.md
@.claude/rules/approval-gate.md
@_templates/flowchart.drawio
Brain: DRAWIO-BRAIN.md