kotlin

Enforce Kotlin conventions across source files and Gradle Kotlin DSL scripts.

Updated Mar 31, 2026

Search Tags:#conventions #null-safety #kotlin #coroutines #ktlint #detekt #gradle-kotlin-dsl

Ready to run

npx skills add https://github.com/dotBeeps/pantry --skill kotlin-dotbeeps

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: kotlin
Source: https://github.com/dotBeeps/pantry/tree/main/morsels/skills/kotlin
Command: npx skills add https://github.com/dotBeeps/pantry --skill kotlin-dotbeeps

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Kotlin conventions beyond standard linters, guiding consistent style and safer patterns across Kotlin projects.

Core Features & Use Cases

Enforced idioms that reduce mutability and promote clarity in Kotlin code.
Guidance for null safety, scope functions, and Kotlin's type system to prevent common errors.
Use Case: Teams adopting these conventions see fewer stylistic disputes and more maintainable Gradle Kotlin DSL.

Quick Start

Apply these Kotlin conventions to your Kotlin sources and Gradle Kotlin DSL files to improve readability and maintainability.

Frequently Asked Questions about kotlin

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

What are the best Kotlin conventions for improving code quality and consistency?▼

Kotlin conventions for code quality enforce idioms that reduce mutability, ensure null safety, and guide scope functions. Applying these to source files prevents common errors and promotes clarity across multi-module projects.

How do I enforce Kotlin idioms and null safety in a multi-module project?▼

To enforce Kotlin idioms and null safety in a multi-module project, apply standardized conventions to your Kotlin source files. This guides the type system and scope functions to prevent common errors across all modules.

Does this convention set work with Gradle Kotlin DSL scripts?▼

Yes, these Kotlin conventions work with Gradle Kotlin DSL scripts. Applying them maintains readability and ensures safer patterns within your build configuration, resulting in more maintainable Gradle setups.

How do I standardize Kotlin coroutines and error handling across my team?▼

To standardize Kotlin coroutines and error handling across your team, apply a shared set of Kotlin conventions. This satisfies project requirements for consistent patterns and reduces stylistic disputes during code reviews.

What is the difference between standard linters and Kotlin conventions?▼

Standard linters check basic syntax, while Kotlin conventions go further by guiding safer patterns, enforcing null safety, and reducing mutability. This deeper approach ensures consistent style and more maintainable code.

When do I need to apply Kotlin conventions beyond standard linters?▼

You need Kotlin conventions beyond standard linters when your team requires enforced idioms for collections and coroutines. This prevents common errors and resolves stylistic disputes in complex multi-module projects.