home / skills / ehtbanton / claudeskillsrepo / editorconfig-generator

editorconfig-generator skill

safe

This skill instantly generates a complete .editorconfig file with project-specific settings for consistent coding styles across editors.

npx playbooks add skill ehtbanton/claudeskillsrepo --skill editorconfig-generator

Review the files below or copy the command above to add this skill to your agents.

Files (2)

SKILL.md

743 B

---
name: editorconfig-generator
description: Generate .editorconfig files for consistent coding styles across different editors and IDEs. Triggers on "create editorconfig", "generate editor config", "editorconfig for", "editor settings".
---

# EditorConfig Generator

Generate .editorconfig files for consistent coding styles across editors.

## Output Requirements

**File Output:** `.editorconfig`
**Format:** EditorConfig INI syntax
**Standards:** EditorConfig specification

## When Invoked

Immediately generate a complete .editorconfig file with appropriate settings for the project.

## Example Invocations

**Prompt:** "Create editorconfig for web project"
**Output:** Complete `.editorconfig` with settings for JS, CSS, HTML, JSON.

Overview

This skill generates complete .editorconfig files to enforce consistent coding styles across editors and IDEs. It produces EditorConfig-compliant INI syntax tailored to the project type and languages detected or requested. Use simple triggers like "create editorconfig" or "editorconfig for <project>" to get a ready-to-use file.

How this skill works

When invoked, the skill analyzes the project type or the language list you provide and assembles a .editorconfig file with global defaults and language-specific sections. It follows the EditorConfig specification and outputs valid INI syntax ready to save at the repository root. You can request presets (web, node, python, etc.) or custom rules (indent_style, end_of_line, charset, trim_trailing_whitespace, insert_final_newline).

When to use it

New project setup to establish consistent editor behavior
Adding consistent formatting to an existing multi-language repository
Onboarding teams to enforce shared whitespace and encoding rules
Before CI formatting checks to reduce style-related noise
When migrating between editors or standardizing across IDEs

Best practices

Place the generated .editorconfig at the repository root for project-wide effect
Include both global defaults and per-language sections for clarity
Keep rules minimal and focused on editor behavior, not code style enforced by linters
Use explicit charset and end_of_line settings to avoid cross-platform issues
Review and customize sections for generated build or generated files to avoid accidental formatting

Example use cases

Create editorconfig for web project: outputs rules for HTML, CSS, JS, JSON with 2-space indentation and utf-8 charset
Generate editor config for TypeScript monorepo: provides root=true, overrides for *.ts and *.tsx, and node module ignores
Editorconfig for Python project: sets indent_style=space, indent_size=4, and trim_trailing_whitespace=true
Create editorconfig for mixed repo: sets common defaults and language-specific blocks for Markdown, YAML, and shell scripts
Quickly produce a config to add to CI to reduce formatting diffs across contributors

FAQ

Can I customize the generated sections?

Yes. Provide the list of languages or specific rules you want included and the skill will incorporate them into the .editorconfig output.

Does the output follow the EditorConfig spec?

Yes. The skill produces EditorConfig-compliant INI syntax and standard keys like indent_style, indent_size, charset, end_of_line, trim_trailing_whitespace, and insert_final_newline.