writing-style-markdown

To enforce consistent markdown writing conventions, apply rules that standardize bullet lists, Mermaid diagrams, and semantic line breaks around 80 characters to improve readability and maintainability across files.

The best way to format markdown diagrams for version control is using Mermaid syntax, which keeps sequence and flow diagrams source-controlled, text-based, and easily editable directly within documentation files.

Use semantic line breaks in markdown documentation to break lines at natural sentence boundaries around 80 to 100 characters, which significantly improves raw-source readability and produces cleaner diffs during collaborative editing.

Use bullet lists in markdown by default for flexibility and easier editing, and reserve numbered lists only for situations requiring explicit sequential ordering or direct step referencing.

Yes, you can apply markdown formatting rules to existing README files by converting numbered lists to bullets, adding Mermaid diagrams for visual flows, and rewrapping paragraphs to semantic line breaks.

Yes, exceptions to semantic line wrapping rules include markdown tables and skill frontmatter, which are skipped to preserve their structural integrity and rendering compatibility across tools.