Loading page
About this tool
Turn your team's conventions into a coding standards document plus a matching .editorconfig, per language.
This generator turns a handful of choices — language, indentation, line length, quotes and review rules — into a complete engineering style guide in Markdown plus a matching .editorconfig file. Defaults are seeded from each ecosystem's dominant published standard: Prettier for JavaScript and TypeScript, PEP 8 for Python, gofmt for Go, the Google Java Style Guide, RuboCop defaults for Ruby and Microsoft's .NET naming guidelines for C#. It is built for tech leads and new teams who want a documented standard without writing it from scratch.
Open Engineering Style Guide Generator on AltFTool — it loads instantly in your browser.
Provide your input — an image, text, or data.
Let the tool analyze or generate the result.
Review, refine, and reuse the output wherever you need it.
Defaults come from Prettier, PEP 8, gofmt, Google Java Style, RuboCop and .NET guidelines — not invented rules.
One set of choices produces both the human-readable Markdown guide and a machine-readable .editorconfig.
Toggle commit messages, branching, reviews, tests, error handling and documentation rules on or off.
At minimum: formatting rules (indentation, line length, quotes), naming conventions, a short list of language-specific rules, and the exact formatter and linter commands that enforce them. Strong guides also cover commit-message format, branch naming, code-review expectations and testing rules — the sections this generator lets you toggle on.
It varies by ecosystem: Prettier defaults to 80 characters for JavaScript and TypeScript, PEP 8 specifies 79 for Python (Black raises it to 88), the Google Java Style Guide uses 100, RuboCop defaults to 120 for Ruby, and gofmt imposes no hard limit at all for Go. The generator applies the right default for your language and lets you override it between 60 and 200.
An .editorconfig is a small INI-style file that editors and IDEs read automatically to apply indentation style, indent size, line endings and trailing-whitespace rules per file type. Generating it alongside the written guide means the most mechanical rules are enforced by tooling instead of by reviewers.
No — anything a formatter can enforce should be enforced by the formatter in CI, and reviewers should focus on behaviour, naming and design. The generated guide states this explicitly and includes the formatter and linter commands (for example `prettier --write .` or `ruff format .`) so the rule is automated rather than debated.