DrawIO Architect

Problem

Architecture diagrams often stall on two issues: unclear business relationships and messy DrawIO XML details such as inconsistent spacing, crossing connectors, and brittle styling. ascii-drawio targets engineers who need an editable architecture diagram before design review, not a screenshot-style graphic.

How It Works

The skill structures generation into controlled steps:
- Requirement confirmation: identify systems, modules, roles, and data flow before discussing layout or color.
- Palette and layout: present choices and preview nodes, groups, and connections with an ASCII wireframe.
- Diagram generation: after wireframe approval, handle mxgraph.aws4.* icons, coordinate planning, spacing checks, connector-crossing review, and .drawio XML output.

It requires wireframe confirmation before writing files and applies style constraints, such as avoiding residual html=1 and using 
 for line breaks, so the result remains an editable .drawio file.

Boundaries

It fits structured topology, service flow, and AWS component relationships. Highly visual, illustrative, or brand-locked diagrams may still need manual refinement in DrawIO.