← ClaudeAtlas

cli-forge-schemalisted

Use this skill to generate, convert, or refine diagrams and visual representations in GitHub-compatible Mermaid. Triggers include: 'diagram', 'schema', 'flowchart', 'sequence diagram', 'architecture diagram', 'ER diagram', 'state machine', 'gantt', 'mindmap', 'timeline', 'mermaid', 'visualize', 'draw', 'convert table to diagram', 'kanban', 'PERT', 'roadmap', 'changelog', 'sankey', 'quadrant', 'git graph', or any request to create, fix, or improve a visual representation of data, processes, or architecture. Also triggers when the user pastes broken Mermaid, asks to simplify a complex diagram, wants to convert markdown tables/bullet lists/SQL schemas/JSON structures/API lists/RACI matrices into visual formats, or says 'make this visual'. Do NOT use for actual image generation (PNG, SVG rendering) — output is always Mermaid markdown.
Destynova2/cli-code-skills · ★ 4 · Data & Documents · score 83
Install: claude install-skill Destynova2/cli-code-skills
> **Optimization:** This skill uses on-demand loading. Heavy content lives in `references/` and is loaded only when needed. > **Language rule:** Skill instructions are written in English. When generating user-facing output, detect the project's primary language (from README, comments, docs, commit messages) and produce labels, titles, and annotations in that language. If the project is bilingual, ask the user which language to use before proceeding. # Schema Forge — Clear Diagrams, Zero Syntax Errors Generate professional, GitHub-compatible Mermaid diagrams that are **readable first, pretty second**. ## Core Philosophy 1. **Clarity over completeness** — a diagram that shows too much shows nothing. If it's complex, split it 2. **Right tool for the job** — pick the diagram type that makes the data obvious, not the one that looks fancy 3. **GitHub-first** — every diagram must render on GitHub without errors. No FontAwesome, no click events, no exotic features 4. **UX ergonomics** — treat diagrams like UI: if a user needs more than 5 seconds to understand the flow, redesign it 5. **Truth over aspiration** — a diagram must reflect what EXISTS in the code, not what someone hopes to build. Stale diagrams are worse than no diagrams 6. **Gotchas** — read `../../gotchas.md` before producing output to avoid known mistakes --- ## Operating Modes This skill operates in three modes, detected from the user's input: ### Mode A — Single Diagram The user describes something specific