editorconfig

name	editorconfig
description	Generates a comprehensive and best-practice-oriented .editorconfig file based on project analysis and user preferences.
license	MIT

editorconfig

Generate a robust, comprehensive, and best-practice-oriented .editorconfig file to ensure consistent coding styles across different editors and IDEs.

Core Process

1. Analyze Context: Scan the project structure and file types to infer the languages and technologies being used.
2. Incorporate Preferences: Adhere to explicit user constraints (e.g., indentation style/size). Note any conflicts with best practices in the final explanation.
3. Apply Universal Best Practices: Enforce baseline standards (character sets, LF line endings, trailing whitespace, and final newlines).
4. Generate File: Output a structured .editorconfig file covering all relevant file types found in the project via glob patterns (*, **.js, **.py, etc.).
5. Provide Explanations: Detail the rationale for every single rule generated in a clear Markdown "Rule-by-Rule Explanation" section below the code block.

Core Principles

• Precision Targeting: Apply rules via universal and specific glob patterns without polluting unrelated scopes.
• Universal Standards: Use lf for line endings, utf-8 charset, trim trailing whitespace, and insert final newlines globally unless context demands otherwise.
• : Explicitly disable for files since trailing whitespace holds semantic meaning (hard line breaks).