If you're tired of fighting TikZ layouts and want flowcharts that don't look like they escaped from a 1990s textbook, this gives you two opinionated style systems: a Material-like theme with semantic colors and distinct shapes for data versus compute, and an Anthropic-inspired theme with warm ivory backgrounds, dashed grouping lanes, and pastel cards. The real value is in the constraints. It forces you to plan layout before drawing edges, insists on orthogonal connections with perpendicular entry at node anchors, and even tells you to spawn a subagent to review whether your diagram actually meets requirements instead of trusting your own pass. Useful if you want consistent technical diagrams without reinventing spacing and colors every time.
npx -y skills add yzlnew/infra-skills --skill tikz-flowchart --agent claude-codeInstalls into .claude/skills of the current project.
This skill provides standardized templates/styles for establishing professional technical diagrams using LaTeX TikZ. It is designed for creating flowcharts, architecture diagrams, and process flows.
When asked to "create a flowchart" or "draw a diagram" in this project, first choose a single theme, then open only that theme's file as the starting point.
Before writing any \node or \draw commands, plan the layout first: decide the main flow direction, group nodes into rows/columns or lanes, and make sure related nodes are aligned so the connectors can stay orthogonal.
If you need to judge whether the generated diagram actually satisfies the user's requirements, do not rely only on your own generation pass. Spawn a subagent for an independent review and use that review to verify compliance or identify gaps.
| Theme | File |
|---|---|
| Default Material-Like | themes/material-like.md |
| Anthropic | themes/anthropic.md |
After selecting a theme, read the corresponding file for the full style guide, color definitions, node styles, and LaTeX template.
right=of Node, below=of Node, or explicit coordinates to keep the layout stable. Adjust spacing via node distance or fixed x/y gaps so nodes have enough room for labels and bends..east, .west, .north, and .south. The segment that touches a node should be perpendicular to that side: horizontal into .east/.west, vertical into .north/.south.-- lines for nodes that already share a row or column, and use -| / |- only when a bend is actually needed. Avoid diagonal lines and avoid lines that hit a node corner or graze an edge at an angle.fit library and a background-layer group style to draw lane or phase containers. For the Anthropic theme, keep containers transparent and dashed.\\ for line breaks and \scriptsize or a dedicated label macro for secondary details.sickn33/antigravity-awesome-skills
kubesphere/kubesphere
supercent-io/skills-template