markdown-editor

To format Markdown files, apply best-practice rules that normalize heading levels sequentially, add blank lines around headings and code blocks, and default to 80 characters per line while preserving existing style.

The best way to enforce line-length limits in Markdown is applying a linting process that defaults to 80 characters per line but preserves the established line-length convention when one is clearly present in the file.

Markdown formatting does not work with Obsidian vault files; any file inside a directory containing a .obsidian/ folder is skipped to respect Obsidian-specific structures and prevent unwanted modifications.

To preserve existing content style when editing Markdown, apply GitHub Flavored Markdown rules unless specified otherwise, maintaining the original structure and avoiding raw HTML unless Markdown cannot express the requirement.

You should always add blank lines around lists and code blocks in Markdown to improve readability and ensure proper rendering across different parsers and documentation platforms.

You should avoid raw HTML tags in Markdown documentation drafts unless Markdown cannot express the specific requirement, ensuring the content remains portable and follows standard GitHub Flavored Markdown syntax.