
GUIDE
Team Style Guide Kit
Names, imports, files, and tests in one clear place.
CODE STYLE
Use one style rule, one formatter, and one review list. Ship cleaner Scala with fewer fixes.

FROM THE JOURNAL
Names, imports, files, and tests in one clear place.

GUIDE
Names, imports, files, and tests in one clear place.

STRICT

FORMAT

Keep package, class, and method names easy to read.

Stop style drift before a pull request lands.

Simple rules for public repos and new contributors.

SETUP
SETUP

CI
CI
TOPIC CHIPS
Clear rules for names, files, imports, and test code.

GUIDE
Clear rules for names, files, imports, and test code.

TIPS
Small checks that catch style drift before review.

GUIDE
Scalafmt setups for teams, monorepos, and libraries.

TRENDS
Build steps that stop bad style before merge.
style rules and checks
style rules and checks
to set up a team
to set up a team
for guide, lint, and CI
for guide, lint, and CI
Community
“One style guide cut our review comments in half. The team now sees the same rules every time.”
Priya Shah
Platform Lead, Northstar Labs
“The formatter preset gave us a clear start point, so new code looks the same on day one.”
Marco Liu
Open Source Maintainer, Signal Forge
“CI checks saved us from style drift after every release branch.”
Elena Novak
Engineering Manager, GridPilot
SPOTLIGHT TAIL
A clean base for names, imports, files, and tests.

FEATURE
A clean base for names, imports, files, and tests.

Use it in pull requests and review notes.

Simple settings for wrap rules, spacing, and imports.

WIDE
Stop style issues before they land in main.

Short rules for model names and data files.

Keep shared code names plain and clear.

A quick check before every merge.

Help new contributors follow the same style.
Journal




Questions
Quick answers before visitors choose a product, service, or next step.
It gives teams style guides, lint rules, formatter presets, and review checklists for Scala codebases.
Yes. You can use formatter presets, setup notes, and review checks that match common Scalafmt use cases.
Yes. The docs fit public repos, team codebases, and maintainers who want clear rules for pull requests.
Yes. Add checks to your build so style issues fail fast before code merges, then keep review notes short and clear.
Scala developers, team leads, and open-source maintainers who want one clear code style across every repo.
Yes. You get plain setup docs for editors, build tools, rule files, and code review steps, so the whole team can start fast.
Get short notes on Scala style, rule changes, formatter tips, and team setup docs, sent a few times a month.