← ClaudeAtlas

archify-diagram-pslisted

Interview-driven diagram builder. When the user asks to generate an architecture, infrastructure, sequence, or flow/data-flow diagram, this skill runs a thorough structured interview to capture every system detail — WAF, policies, load balancers, VMs vs physical machines, DMZ/app/web tiers, microservices with names/ports/tech-stack, databases, message queues, service-to-service interactions, internal/external LB routing, API dependencies, external systems, IP addressing and traffic routing — then produces a complete, validated diagram via the archify skill so nothing is left out. Use whenever the user wants a complete, detail-rich diagram of a real system rather than a rough sketch, or types /archify-diagram-ps.
solankipravin374/archify-diagram-ps · ★ 3 · Web & Frontend · score 74
Install: claude install-skill solankipravin374/archify-diagram-ps
# archify-diagram-ps An **interview-first** diagram builder. This skill does **not** draw diagrams itself. It behaves like a senior architect: it refuses to draw a box until it knows what is inside it, what talks to it, on which port, through which gateway, and why. It **extracts every detail through structured questioning**, builds a complete model of the system, confirms it with the user, and only then hands a fully-specified JSON to the **`archify`** skill for rendering, validation, and delivery. > **Dependency:** requires the `archify` skill to be installed (it does the actual rendering + `--quality showcase` validation + delivery). If `archify` is missing, say so and stop. ## Core principle **Never guess — always ask.** If a detail is unknown, it is shown in the diagram as `unknown`, never fabricated. **Completeness is the product:** every detail captured in the interview must appear in the rendered output so a viewer can click any node and find its real specs, ports, protocols, and dependencies. ## Procedure ### Step 0 — Detect diagram type Infer or ask: **architecture, sequence, or flow/data-flow?** Confirm in one line, then load the matching questionnaire below. If the user supplied a repo/doc up front, pre-fill answers from it and only ask about the gaps. ### Step 1 — Interview in batched rounds - Ask **4–7 questions at a time, grouped by theme** — never a single wall of questions, never strictly one-at-a-time. - After each batch, **reflect back** a compact bu