tikz-flowchart
Creates professional TikZ flowcharts with standardized themes, including Google Material-like and Anthropic-inspired options.
What this skill does
# TikZ Flowchart Skill 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. ## Usage 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. - Use the **default Material-like theme** for conventional engineering diagrams with stronger semantic color coding and distinct data/storage/compute shapes. - Use the **Anthropic theme** when the user wants warm ivory backgrounds, quiet dashed grouping containers, pastel cards, thin connectors, and a calm product-diagram look. ## Theme Selection - If the request mentions Anthropic, warm/product-diagram styling, pastel cards, or dashed ownership lanes, use the **Anthropic theme**. - Otherwise default to the **Material-like theme**. ## Theme Files | Theme | File | |-------|------| | Default Material-Like | [`themes/material-like.md`](themes/material-like.md) | | Anthropic | [`themes/anthropic.md`](themes/anthropic.md) | After selecting a theme, read the corresponding file for the full style guide, color definitions, node styles, and LaTeX template. ## Best Practices 1. **Layout First**: Determine the node layout before drawing edges. Decide the dominant reading direction, assign nodes to rows/columns or swimlanes, and align related nodes so most edges can be drawn with zero or one bend. If the routing looks awkward, fix the layout first instead of forcing the edge. 2. **Relative Positioning**: Use `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. 3. **Perpendicular Edge Entry**: Connect to explicit anchors such as `.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`. 4. **Orthogonal Edges**: Prefer straight `--` 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. 5. **Grouping**: Use the `fit` library and a background-layer group style to draw lane or phase containers. For the Anthropic theme, keep containers transparent and dashed. 6. **Conciseness**: Keep node text short. Use `\\` for line breaks and `\scriptsize` or a dedicated label macro for secondary details. 7. **Anthropic Node Shapes**: Prefer rounded rectangles as the default node shape in the Anthropic theme. Use diamonds only for true decisions and avoid heavy cylinders or shadowed compute boxes. 8. **Anthropic Typography**: Keep the full diagram sans-serif, with tinted primary and secondary lines inside each node instead of pure black text. 9. **Independent Review**: When evaluating whether the generated flowchart meets the user's constraints, spawn a subagent to review the output against the requirements. Do not treat self-evaluation during generation as sufficient verification.
Related in AI Agents
skill-development
IncludedComprehensive meta-skill for creating, managing, validating, auditing, and distributing Claude Code skills and slash commands (unified in v2.1.3+). Provides skill templates, creation workflows, validation patterns, audit checklists, naming conventions, YAML frontmatter guidance, progressive disclosure examples, and best practices lookup. Use when creating new skills, validating existing skills, auditing skill quality, understanding skill architecture, needing skill templates, learning about YAML frontmatter requirements, progressive disclosure patterns, tool restrictions (allowed-tools), skill composition, skill naming conventions, troubleshooting skill activation issues, creating custom slash commands, configuring command frontmatter, using command arguments ($ARGUMENTS, $1, $2), bash execution in commands, file references in commands, command namespacing, plugin commands, MCP slash commands, Skill tool configuration, or deciding between skills vs slash commands. Delegates to docs-management skill for official documentation.
reprompter
IncludedTransform messy prompts into well-structured, effective prompts — single or multi-agent. Use when: "reprompt", "reprompt this", "clean up this prompt", "structure my prompt", rough text needing XML tags and best practices, "reprompter teams", "repromptception", "run with quality", "smart run", "smart agents", multi-agent tasks, audits, parallel work, anything going to agent teams. Don't use when: simple Q&A, pure chat, immediate execution-only tasks. See "Don't Use When" section for details. Outputs: Structured XML/Markdown prompt, quality score (before/after), optional team brief + per-agent sub-prompts, agent team output files. Success criteria: Single mode quality score ≥ 7/10; Repromptception per-agent prompt quality score 8+/10; all required sections present, actionable and specific.
adaptive-compaction
IncludedAdaptive add-on policy and recovery layer that decides WHEN to compact, prune, snapshot, or fork -- replacing fixed-percent auto-compaction across Claude Code, Codex, and MCP-capable hosts. Trigger on auto-compact timing or damage: "when should I compact", "is it safe to compact now or start a fresh session", "auto-compact fires too early/mid-task", "switching to an unrelated task but the window still has space", "context rot", "answers get worse the longer the session runs", "the agent forgot the plan or my decisions after it summarized", "add a layer on top that manages context without changing the agent", raising autoCompactWindow to give the policy room, or installing/tuning a cross-tool compaction policy or PreCompact hook -- even when "compaction" is never said but the problem is context-window pressure or post-summarization memory loss. Do NOT use to summarize a conversation, build RAG, write a summarization prompt (decides WHEN not HOW), or answer max-context-length trivia.
agent-skill-creator
IncludedCreate cross-platform agent skills from workflow descriptions. Activates when users ask to create an agent, automate a repetitive workflow, create a custom skill, or need advanced agent creation. Triggers on phrases like create agent for, automate workflow, create skill for, every day I have to, daily I need to, turn process into agent, need to automate, create a cross-platform skill, validate this skill, export this skill, migrate this skill. Supports single skills, multi-agent suites, transcript processing, template-based creation, interactive configuration, cross-platform export, and spec validation.
llm-wiki
IncludedUse when building or maintaining a persistent personal knowledge base (second brain) in Obsidian where an LLM incrementally ingests sources, updates entity/concept pages, maintains cross-references, and keeps a synthesis current. Triggers include "second brain", "Obsidian wiki", "personal knowledge management", "ingest this paper/article/book", "build a research wiki", "compound knowledge", "Memex", or whenever the user wants knowledge to accumulate across sessions instead of being re-derived by RAG on every query.
skill-master
IncludedAgent Skills authoring, evaluation, and optimization. Create, edit, validate, benchmark, and improve skills following the agentskills.io specification. Use when designing SKILL.md files, structuring skill folders (references, scripts, assets), ingesting external documentation into skills, running trigger evals, benchmarking skill quality, optimizing descriptions, or performing blind A/B comparisons. Keywords: agentskills.io, SKILL.md, skill authoring, eval, benchmark, trigger optimization.