Drawio Shapes

Workflow

1. Identify the user intent: software architecture, cloud, UML, BPMN, UI wireframe, network, floorplan, chart, or generic flowchart.
2. Map the intent to one or more draw.io categories or libraries.
3. Check whether the request is about native libraries, public custom libraries, or both.
4. Suggest the best matching libraries first.
5. Suggest likely shapes or diagram families within those libraries.
6. If a request mentions C4, prioritize the native C4 library.
7. If the user asks for “all available shapes”, explain that draw.io does not expose a single complete public catalog and that the closest reliable sources are the repository sidebars plus the taxonomy file.

Native-source policy

Use these source priorities:

1. Primary: native repository sources such as Sidebar-*.js and related stencil references.
2. Secondary: resources/dia.txt for category and library labels.
3. Tertiary: drawio-libs for public custom libraries.

Response style

• Start with the best matching library or category.
• Then list the most likely shapes or families to use.
• Mention where the user would find it in draw.io when known, such as “More Shapes > Software” or “More Shapes > Network”.
• For architecture requests, prefer practical recommendations over exhaustive lists.
• For ambiguous requests, give 2-4 likely libraries instead of guessing one.

Known native categories

Use the reference file: references/drawio-shapes-catalog.md

Examples

Example: C4

User request:

• “Quais shapes usar para um diagrama C4 de containers?”

Expected behavior:

• Recommend the native C4 library first.
• Mention related fallbacks from Software / UML when needed.
• Suggest a minimal set such as person, software system, container, database, boundary, and relationship labels.

Example: AWS architecture

User request:

• “Quero desenhar uma arquitetura AWS com filas, banco e API gateway.”

Expected behavior:

• Recommend AWS or AWS 3D first.
• Optionally mention generic network/software fallback shapes if the exact service icon is unavailable.

Example: generic process flow

User request:

• “Preciso modelar um fluxo de aprovação.”

Expected behavior:

• Recommend Flowcharts first.
• Suggest process, decision, terminator, document, connector, and swimlane options when relevant.

Limits

• Do not claim that dia.txt contains every individual shape.
• Do not assume a public API exists for the full More Shapes inventory.
• If the user asks for a verified full inventory, state that it must be reconstructed from the native repository sources.