agentleFS
pcoulbournepcoulbourne/everything-claude-code/.cursor/rules/kotlin-coding-style.md

everything-claude-code / rules

Cursor rule1 starsChanged 7 months agoMITView on GitHub

Kotlin coding style extending common rules

17 other projects use a version of this.

Adopted by

Steady: 0 new projects took it in the last 4 weeks, none the 4 weeks before.thin data

Week of Sep 13: 0 new projectsWeek of Sep 20: 0 new projectsWeek of Sep 27: 0 new projectsWeek of Oct 4: 0 new projectsWeek of Oct 11: 0 new projectsWeek of Oct 18: 0 new projectsWeek of Oct 25: 0 new projectsWeek of Nov 1: 0 new projects
Sep 2026Oct 2026Nov 2026
New projects taking a version of this file each week, over the 8 weeks our latest run read: only 0 in all, so this is a hint, not a trend.

Most recently taken up by

The file

We split this kotlin-coding-style.md into the rules it gives an agent

6 rules. About 0 are common, 2 are distinctive, and 4 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use trailing commas in multiline declarations

    line 13
  2. Very specific:

    Prefer val over var

    line 20
  3. Very specific:

    Use immutable collection types (List, Map, Set)

    line 21
  4. Very specific:

    Use data class with copy() for immutable updates

    line 22
  5. Very specific:

    Avoid !! -- use ?., ?:, require, or checkNotNull

    line 26
  6. Distinctive:

    Prefer expression bodies for single-expression functions:

    line 31

≈ “Common” is an estimate: at least 1 in 5 of the 6,668 Cursor rule files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
kotlin-coding-style.md

Kotlin Coding Style

This file extends the common coding style rule with Kotlin-specific content.

Formatting

  • Auto-formatting via ktfmt or ktlint (configured in kotlin-hooks.md)
  • Use trailing commas in multiline declarations

Immutability

The global immutability requirement is enforced in the common coding style rule. For Kotlin specifically:

  • Prefer val over var
  • Use immutable collection types (List, Map, Set)
  • Use data class with copy() for immutable updates

Null Safety

  • Avoid !! -- use ?., ?:, require, or checkNotNull
  • Handle platform types explicitly at Java interop boundaries

Expression Bodies

Prefer expression bodies for single-expression functions:

fun isAdult(age: Int): Boolean = age >= 18

Reference

See skill: kotlin-patterns for comprehensive Kotlin idioms and patterns.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.