editorconfig

Provide your project structure and preferences such as indent style and size, and the skill generates a complete .editorconfig file. It analyzes your file types to apply appropriate glob-pattern rules and includes universal settings like charset and line endings.

A well-formed .editorconfig should set root = true, indent_style, indent_size, end_of_line, charset, trim_trailing_whitespace, and insert_final_newline. Per-file-type sections using glob patterns like [*.md] can override universal rules where needed.

Trailing whitespace is significant in Markdown because two trailing spaces create a hard line break. The generated configuration sets trim_trailing_whitespace = false under a [*.md] section to preserve this behavior.

Yes, EditorConfig is supported natively or via plugins by most editors including VS Code, IntelliJ, Vim, and Sublime Text. The root = true setting stops the search at the project directory so parent configurations do not interfere.

The skill follows your explicit preference even when it conflicts with a common best practice, and notes the conflict in the rule-by-rule explanation so you understand the trade-off.