← ClaudeAtlas

arkitect-drawiolisted

Create or edit editable Draw.io (.drawio) solution-architecture diagrams in the Arkitect house style, using the bundled icon packs for AWS, Azure, Google Cloud, data platforms, AI frameworks, DevOps, GitHub, file types and agent concepts. Use whenever the request involves a Draw.io/diagrams.net diagram, an AWS or cloud architecture diagram, a monitoring or observability architecture, a data-ingestion or data-pipeline architecture, an agentic/LLM system architecture, a solution-options or as-is/to-be comparison diagram, a flow or decision diagram wanted as .drawio, or an edit to an existing .drawio file.
mouadja02/arkitect · ★ 9 · DevOps & Infrastructure · score 74
Install: claude install-skill mouadja02/arkitect
# Draw.io architecture diagrams Produces native, editable `.drawio` XML — never a flattened image, never Mermaid as the final artifact. Style rules are learned from an analysed corpus of real architecture pages, each rule carrying its evidence count; the icons are eighteen packs - about 4,800 marks - bundled with this skill and resolved by one search. Scripts live in `${CLAUDE_PLUGIN_ROOT}/skills/arkitect-drawio/scripts`. Read `references/style-guide.md` before laying anything out, and `references/pattern-catalog.md` to pick a starting pattern. ## Workflow 1. **Interview until you both mean the same thing.** One question at a time, each carrying your recommended answer, walking the design tree in dependency order. See [Interview first](#interview-first). Never ask about styling — that is this skill's job. Do not start drawing while a branch that would change the drawing is unresolved. 2. **Pick a pattern and state assumptions.** Choose the nearest entry in `references/pattern-catalog.md`. Write down every architectural assumption you made; they go in the final report and, where useful, in a note box on the canvas. 3. **Resolve icons — bundled packs first.** ```bash node scripts/find-icon.mjs "bedrock" # rank matches, metadata only node scripts/find-icon.mjs "cloud run" --context gcp # bias toward the stack in play ``` The search answers with `confident: true` or with the reason it is not, plus the alternatives, and