Jekyll Mermaid Publishing

Critical separation

This skill does not visually refactor Mermaid.

If the user asks to:

• improve Mermaid appearance;
• normalize Mermaid;
• apply Mermaid visual standards;
• make diagrams consistent;

first apply:

mermaid-visual-standard

Then use this skill only for Jekyll packaging.

Purpose

Author locally with a mermaid code fence containing a complete Mermaid diagram.

Publish to Jekyll by changing only the opening fence language to mermaid!. Do not place placeholder Mermaid fences inside Jekyll-processed documentation.

Only the opening fence changes.

Front matter

If Mermaid blocks exist, require:

mermaid: true

Conversion contract

At publication time:

1. find plain ` ```mermaid ` opening fences;
2. convert them to ` ```mermaid! `;
3. preserve Mermaid body exactly;
4. preserve closing fence exactly;
5. preserve wrappers;
6. preserve colors;
7. preserve emoji;
8. preserve graph topology;
9. preserve natural height;
10. preserve node labels and classes.

References

In a Jekyll post References section:

• use explicit Markdown links;
• make URLs clickable;
• keep source title and author readable.

Example:

- Viktor S. Grebennikov, *My World*, Chapter 5:
  [English translation PDF](https://example.org/source.pdf)

Publication validation

Check:

• mermaid: true exists;
• no plain mermaid fence remains in publication output;
• Mermaid body was not modified;
• wrappers remain intact;
• reference URLs are clickable.

Do not

• redesign diagrams;
• add or remove colors;
• add or remove emoji;
• change direction;
• normalize height;
• change node shapes;
• change edge semantics.