agentleFS
ch4570ch4570/vulpora/skills/diagram-styler/SKILL.md

diagram-styler

Skill1 starsChanged 56 days agoApache-2.0View on GitHub

Render an existing Mermaid `.mmd` semantic source into a themed, responsive, accessible SVG while preserving the source and recording renderer provenance in a manifest. Use for light or dark Mermaid styling, document-width SVG output, presentation output, and pre-rendering diagrams for HTML or PDF documents. Do not use to change diagram meaning or to download renderers at runtime.

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Read references/rendering-contract.md.

    line 13
  2. Very specific:

    Run the renderer preflight.

    line 14
  3. Very specific:

    Keep the generated manifest beside the SVG.

    line 18
  4. Very specific:

    If rendering cannot run, return the preserved .mmd, the preflight result, and the missing dependency.

    line 46

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 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

Diagram Styler

Apply a visual layer to Mermaid source without changing its semantic model.

Workflow

  1. Confirm that the input .mmd is the preserved source of truth. If meaning must change, return to the mermaid-diagrams skill.
  2. Read references/rendering-contract.md. Select light or dark and a document, presentation, or dark-ui target.
  3. Run the renderer preflight. Never invoke npx, install packages, or use a network renderer.
  4. Render with scripts/render-mermaid.js, providing a meaningful title and one-sentence description.
  5. Inspect the SVG at its target width for clipped labels, overlapping edges, unreadable contrast, broken glyphs, and excessive density.
  6. Fix semantic layout problems in the .mmd; fix palette or sizing problems in the theme/target layer. Re-render and inspect again.
  7. Keep the generated manifest beside the SVG. When the destination is PDF, compose the SVG first and run the pdf-qa skill on every final PDF page.

Commands

node scripts/render-mermaid.js --preflight
node scripts/render-mermaid.js \
  --input path/to/diagram.mmd \
  --output path/to/diagram.svg \
  --theme light \
  --target document \
  --title "Order processing" \
  --description "Sequence showing checkout, payment authorization, and fulfillment."

The preflight returns JSON even when unavailable. A render fails closed when mmdc is absent. MMDC_BIN may point to a preinstalled executable; it must never point to a download wrapper.

Completion Gate

Complete only when:

  • the .mmd, .svg, and .svg.manifest.json all exist and the manifest hashes match;
  • the SVG has role="img", a file-scoped aria-labelledby, <title>, and <desc>;
  • source meaning is unchanged and theme instructions are absent from the .mmd;
  • the SVG is responsive within the selected target width;
  • visual inspection finds no clipping, overlap, broken glyph, contrast, or readability defect;
  • a PDF destination has also passed the pdf-qa skill after document composition.

If rendering cannot run, return the preserved .mmd, the preflight result, and the missing dependency. Do not claim a rendered artifact or visual inspection.

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.