← ClaudeAtlas

visual-vibeslisted

Analyze any repository (or a proposed system) and create, update, and explain evidence-backed architecture diagrams and docs. Use for creating or updating C4, UML, ERD, DFD, sequence, state, deployment, CI/CD, and security diagrams; generating HLD/LLD/ADRs; answering questions about how a codebase is structured; and producing animated diagram READMEs. Triggers on requests like "diagram this repo", "how is X wired up", "update the architecture diagram", "map the data flow", or "explain the system design".
yash0208/visual-vibes · ★ 0 · Data & Documents · score 65
Install: claude install-skill yash0208/visual-vibes
# Visual Vibes Turn a codebase (or a set of requirements) into **evidence-backed** diagrams, architecture docs, and clear answers. The core idea: build one canonical model grounded in real files, then render diagrams as *views* of that model — never invent components, and never let two diagrams disagree. ## The one rule that matters **Evidence before visualization.** Every element, relationship, protocol, datastore, and boundary you draw must trace to a real file/line, or be explicitly marked `inferred`, `proposed`, or `unknown`. Uncertainty is shown (dashed lines + label), never hidden. ## Modes Parse `$ARGUMENTS`. First token = mode (default `full` when a repo is given, `explain` when a question is asked). | Mode | What it does | |------|--------------| | `full` | Full package: model → HLD + LLD + diagrams + review, under `docs/architecture/`. | | `diagram` | One or a few diagrams of a given type/scope. | | `update` | Re-derive the model, regenerate only diagrams affected by changes. | | `explain` | Answer a question about the repo, grounded in evidence, with an inline diagram if it helps. | | `hld` / `lld` | Just the high-level or low-level design doc + its diagrams. | | `review` | Compare code vs docs vs diagrams; report contradictions, gaps, risks. | | `drift` | Diff a base git revision vs current; report architecture changes. | | `proposal` | No code yet — treat requirements as evidence, mark elements `proposed`. | Flags: `--type <diagram-type>`, `--renderer auto