agentleFS
texra-aitexra-ai/texra-scientific-skills/skills/tikz-figure-builder/SKILL.md

tikz-figure-builder

Skill4 starsChanged 7 months agoMITView on GitHub

Create or refine TikZ figures for technical papers and slides. Use when Codex needs to add a new diagram, improve an existing figure, align a visual with manuscript notation, or iteratively compile and visually read the rendered output until the figure is correct and readable.

The file

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 7 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈7

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill for architecture diagrams, workflows, commutative diagrams, tensor-network sketches, algorithm schematics, annotated plots, …

    line 10
  2. Distinctive:

    Read the surrounding manuscript or slide context before drawing.

    line 14
  3. Distinctive:

    Prefer reusable styles and compact structure over copy-pasted node formatting.

    line 16
  4. Distinctive:

    Keep captions and in-text references synchronized with the final figure.

    line 20
  5. Distinctive:

    Avoid duplicated style definitions across multiple figures when a shared style can live in the preamble or a common file.

    line 27
  6. Distinctive:

    Do not stop at source edits alone when a build is possible.

    line 28
  7. Distinctive:

    Ensure the figure integrates cleanly into the surrounding text and layout.

    line 29

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

TikZ Figure Builder

When to use this skill

Use this skill for architecture diagrams, workflows, commutative diagrams, tensor-network sketches, algorithm schematics, annotated plots, and figure cleanups where the final output should be TikZ or closely integrated with LaTeX.

Workflow

  1. Read the surrounding manuscript or slide context before drawing. Match the figure to the notation, vocabulary, and mathematical meaning already in use.
  2. Decide what the figure must communicate. Reduce the diagram to the essential objects, relationships, flow, or geometry.
  3. Prefer reusable styles and compact structure over copy-pasted node formatting.
  4. Compile every substantial TikZ change and visually read the rendered image or PDF, not just the source code. Treat this as an automatic loop: edit, build, read, fix, and rebuild until the figure is stable.
  5. Fix clipping, crowding, label collisions, uneven spacing, unreadable labels, and style drift immediately instead of deferring them.
  6. For mathematically meaningful diagrams, verify that topology, arrow direction, labels, and adjacency actually match the equations or constructions they represent.
  7. Keep captions and in-text references synchronized with the final figure.

Quality Bar

  • A pretty but mathematically wrong diagram is a failure.
  • Labels must be legible and consistent with manuscript notation.
  • Spacing should make structure obvious without decorative clutter.
  • Avoid duplicated style definitions across multiple figures when a shared style can live in the preamble or a common file.
  • Do not stop at source edits alone when a build is possible; the default is to compile, visually read the rendered result, and refine until it is clean.
  • Ensure the figure integrates cleanly into the surrounding text and layout.

For dense or math-sensitive figures, use references/figure-checklist.md to run a stricter pass over layout, consistency, and rendered correctness.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.